Hello,

 

There are a number of variables here, # of users in the List, # of smtp handlers etc, network links etc.

 

Subscribers  in a List are processed sequentially perhaps the List can be broken down into smaller Lists – say 5 Lists alphabetically, and then fired off one after the other, a bit of co-ordination but easier to manage/monitor,

 

 

 

Nope, we’re on a classic license and using it ourselves. Here’s what’s running:

 

10782 ?        00:01:08 lsv

10783 ?        00:00:00 lsv

10784 ?        00:00:00 lsv

10785 ?        00:00:00 lsv

 

10782 is the main process while 83, 84, and 85 are the SMTP handlers as defined in SMTP_FORWARD_n. With our Fall term about to start we have a high volume of mail to lists including university wide ones, so having it handed off to the three handlers is a lifesaver.

 

 

Isn’t SMTP_Forward_N HPO only?  I might be wrong, but I thought it wasn’t available to Classic.

 

 

Depending on how many connections your SMTP server will accept from another machine, use SMTP_FORWARD_n to set up several background processes that will handle the actual sending. For instance if your SMTP_FORWARD is set to smtp.example.com then you could spawn three workers by setting SMTP_FORWARD_n to smtp.example.com*3. This allows several connections to handle each batch of addresses and the additional benefit of letting the main listserv process be available instead of locked up trying to send all the mail by itself.

 

 

 

To unsubscribe from the LSTSRV-L list, click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1