>yesterday, i tried to use the Imail SMTP server v6.06 >in order to send 150 000 + mails
it's the queue processing that kills the throughput. best configuration: put the imail/spool in its own partition, containing no other directories. The spool partition should be on a separate disk and controller. If ATA, on its own ATA master channel with no slave deveice. The disk should be 160 mbyte/sec SCSI, and the controller should be caching, 64 or 124 mbtyes of cache. Use Scott/Declude's queue kicker utility to generate many SMTP sending processes, which means you'll need plenty of memory. For DNS (MX and A record lookups), use a dedicated DNS. You could, perhaps, avoid the weaknesses of IMail queue processing of very high list volumes by a) having Imail send all outbound mail to an IMGate machine where the queue processing is much better b) using a read list processor like Ecartis or Mailman or ezmlm running on *nix (but still respecting all the above techniques for disk setup). If all the above works just right, you should get 30k to 40k msgs/hour, meaning 150k msgs will take 4 or 5 hours, maybe 12 or 24. :)) If the list contains a high percentage of bad addresses (5 or 10%), then the sending rate can be much lower than the above. Also, it's pretty easy to saturate a T1 line with large lists delivery. When a T1, or other line, becomes saturated, or every above 60% utilization, the throughput can degrade horribly. Len http://MenAndMice.com/DNS-training http://BIND8NT.MEIway.com : ISC BIND for NT4 & W2K http://IMGate.MEIway.com : Build free, hi-perf, anti-abuse mail gateways Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Please visit the Knowledge Base for answers to frequently asked questions: http://www.ipswitch.com/support/IMail/
