sys1031.txt 185 MB sys1106.txt 135 MB

The first line is the Imail log file size before IMGate, and the 2nd line from one week later is after IMGate.

The approx 30% reduction in Imail logging is the reduced SMTP acivity, due to 15% to 20% of the incoming mail being rejected by IMGate (MAPS, DNS validations, unknown users, whatever, not even seen by Imail) plus Imail not having to accept SMTP sessions to bounce unknown users, and not having to retry repeatedly failed remote deliveries (the Imail outbound queue is now empty since Imail sends all outbound to always-available IMgate vs. 100's of previously queued msgs due failed deliveries). The IMGate deferred queue (can't deliver) is between 500 and 1000 msgs on average (2 day queue lifetime), a huge burden off the Imail \spool directory.

So perhaps rather than upgrade your Imail machine, first think about lengthening its life a few more months or longer by adding IMGate, while increasing your customers' satifaction with a tremendous reduction in spam. Plus giving yourself a front-line of defense against mail bombs and relaying without touching Imail.

And if you run lots of Imail list volume, then note that this IMGate machine runs as many as 220 SMTP delivery processes on demand (vs 30 standard in Imail) and 30 to 50 SMTPD server processes, but you can add just about as many processes as you want within memory limits. This will tranform the speed at which you can turn around list msgs.

Len