Hey, list! I've been running ASSP (http://assp.sourceforge.net) as a proxy for Imail for a couple of months now. The transition went quite smooth, mainly due to lurking here and learning from you, so I thought I'd share my experience.
ASSP runs on a standalone Win2k box - a 2.8ghz Xeon with 512mb ram - acting as a transparent proxy. It's currently handling 20-30.000 emails a day, spread over ~400 domains. RAM is plentiful (except while rebuilding the spamDB), and cpu-usage averages about 25%. All good, in other words. As others have noted, initial training was a pain, but it was worth it. Even though our userbase is diverse, we have almost no reports of miscategorized mail. Some features of ASSP require these lists: - A "local domains" list which is checked before relaying - A "local addresses" list which is checked to, well, validate local addresses before accepting - A "secondary hostnames" list, to invalidate HELO's In my case, these lists consist of all domains the Imail server will handle, formatted in various ways. Since we add and remove domains from Imail daily, I've scheduled a script to pull domains and do regular updates of these lists on the ASSP server. Feel free to grab the script at http://carr.no/assp-domains.zip Configure ASSP to use listfiles (by putting "file:yourfilename.txt" in the relevant fields). Then, schedule the Imail server to go: "assp-domains.vbs 1 > \\yourasspserver\assp\yourfilename.txt". Read the script comments for details. Any input or thoughts on better ways to handle ASSP in a major/diverse environment would be welcome :-) Best regards, Eric Carr 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/
