List peformance is another place where IMGate "fixes" Imail
>I have experimented with this... Depending on the amount of RAM you have,
>your networking infrastructure, and CPU speed, you will probably find
>diminishing returns after about 48 processes... I've had it as high as 192,
>but that was disastrous in some cases...
I�ve set up IMGate and Listar servers with 400 SMTP processes max,
and have regularly seen many machines run with 200 to 400 processes
sending mail. Have seen 40 k list msgs/hour on outbound, when the list was
"clean", and about 25 k msgs/hour where the list of 180 K members was
pretty darn junky (lost of processes wasted on bad connections, slow
servers, host unreachable, etc, etc).
The idea is to have Imail dump all its outbound on IMGate and let IMGate�s
much more efficient MTA do the deliveries to Internet. Imail�s queue is
never backed up, Imail is not bogged down, and deliveries are much faster
and smoother.
One should estimate 10 secs per message on average from IMGate to Internet
per SMTP process, so 6 mgs/minute x 200 processes = 1200 / minute x 60 =
72K/hour. I expect for most setups 40 to 50 K is achievable, with P500
single CPU and 512 megs RAM.
Assuming DNS and bandwidth ar ok, if your pb is Imail delivery, the IMGAte
is your solution.
Len
http://MenAndMice.com/DNS-training
http://BIND8NT.MEIway.com : ISC BIND 8.2.3 "NT3" 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/
