Thomas Bolioli wrote:
Hi Thomas
1) Does SA auto upgrade to newer versions (of the spam defs more importantly) or could it be set up to do so through an automated CPAN install?
No, and you might not like that. Auto-update sounds too commercial to me, and takes off from you the privilege of knowing what goes on during an update (which includes what and why something went wrong).
Look, when I moved from SA 2.55 to 2.61 I had to rebuild the Bayes database, which required to stop spamd daemon. 2.7 might work only on Perl 5.8+, ... you don't want auto-update to update Perl as well, don't you?! :-)
2) Can individual users easily have their own training files (I know it is possible, looking more for feasibility) when they do not have an
Look, here we are routing about 2GB of Internet incoming mail every day (40000+ mails per day), towards about 5-6000 mailboxes spread over a dozen of domains. None of the individuals ever asked for rules customization. I think it's a matter of how you "sell" the antispam solution (guarantee 90% hit ratio, so they'll tolerate what passes through, then produce statistics).
3) What other issues will I run into in a multi user environment where the SA server is simply forwarding on mail between MTAs and not the final delivery agent?
Bounces! One of the domains here receives only spam (90% of the whole traffic). These do bounce back to inexistant addresses, usually.
High-Availability is another issue.
Rather than marking subjects you might consider quarantining spam on the transit MTA. This reduces bounces too!
Paolo
