ListPostProcessor Helper Application.

>    I want to thank you for reply so quickly on my
questions 
> on the LIstPostProcessor.   In your last email you
mentioned 
> that this helper only works on outgoing list messages. 
 I 
> have been trying to use this helper to aid me in
internal 
> list processing.   The problem I face is I have three 
> internal mail listings with contain 1000+ people on
them.    
> When I sent a mail message to any one of these lists
the 
> system takes a long time to process.    I even
increased the 
> LOCAL channels to aid in processing, but the negative
effect 
> is that the system because very slow.   Can the 
> ListPostProcessor be used to help me or is there
another way??

I hope you don't mind, but this information could be useful
to others,
so I'm posting it back to the list as well.

Yes, it can help. No there isn't another way (that I know
of).

The way current list processing works-- CGPro sends 1
message with all
the recipients on it. This isn't the problem. It's far less
overhead to
send one message for the entire distribution and CGPro does
this much
very quickly.

Then CGPro tries to deliver that message all at once. The
impact of
sending a large mailing is that other normal mail delivery
is delayed
while it delivers the list distribution. The magnitude of
the delay
depends on a lot of factors-- how many local recipients vs
external, how
fast your server is, how fast your internet connection,... 

ListPostProcessor should pull the 1 message the CGPro tries
to send and
break it into individual messages for each person. Assuming
you've used
the default settings, if it sees more than 50 recipients
(HoldRecipientLimit), it will stuff the new messages, in
your case 1000+
on hold (HoldFolder).

Then it checks every 60 seconds (HoldPollInterval) to see
whether there
are 20 more queue files than "queued messages"
(HoldQueueBacklog)
meaning that CGPro isn't keeping up with message processing,
and if not,
it submits the next 30 of the messages on hold
(HoldReleaseRate).

Overall, this is more overhead, not less, but the impact on
normal
message delivery is reduced so dramatically that the extra
overhead is
well worth it. If the messages aren't being delivered fast
enough, you
can adjust the settings-- perhaps the poll interval or
release rate to
get the messages dumped in faster, but just remember that
the faster the
messages dump in, the more they will delay normal e-mail.
Adjusting the
poll interval is safest since it still checks to make sure
CGPro is
keeping up with it's release rate.

IMO, this should all be built-in to CGPro, but it's not, so
we wrote our
own solution.

HTH,
Bret




############################################################
#
This message is sent to you because you are subscribed to
  the mailing list <CGatePromail.stalker.com>.
To unsubscribe, E-mail to: <CGatePro-offmail.stalker.com>
To switch to the DIGEST mode, E-mail to
<CGatePro-digestmail.stalker.com>
To switch to the INDEX mode, E-mail to
<CGatePro-indexmail.stalker.com>
Send administrative queries to  <CGatePro-requestmail.stalker.com>