I am testing IMail to support our newsletter. I am having an issue with it disconnecting from my list management program after it only sends about 200 messages.
I've seen this with IMail refusing all connections from IMGate when the traffic gets heavy (connection refused). Imail catches up and start accepting SMTP connections in a little while.
You will have to limit the rate at which your SMTP client delivers to Imail. tactics such as
1. Send one msg per SMTP session, perhaps with a pause between sessions
2. your SMTP client should open only one session, not several simultaneously.
3. on the Imail side, you can set this SMTP value:
Delay between recipients. Sets a delay (in milliseconds) between the delivery of messages to recipients. The default setting for this option is 0.
Try 1000, then 2000, until Imail is rate-limiting itself enough so that your SMTP client doesn't receive "connection refused".
The problem is that Imail is overwhelming the disk write (queueing) capacity, so optimize your Imail queue and filesystem, including moving the imail queue to separate, dedicated controller and disk. disk throughput, both writing an reading, is always the limit when trying to scale up a mail server to high volumes.
If the above doesn't work out, then use another SMTP gateway, eg, IMGate/postfix, which has both static and dynamic rate input params to play with.
Len
_____________________________________________________________________ http://MenAndMice.com/DNS-training: Seattle; Chicago; San Jose; Wash DC IMGate.MEIway.com: anti-spam gateway, effective on 1000's of sites, free
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
