Trey, > I am not opposed to multiple amavisd-new servers, but I'm not sure how > that would be implemented with our setup. The messages are all > delivered to one server, so how do you propose that we distribute the > email among multiple servers? We cannot just do it on a per-domain > basis, because some of our larger domains will overwhelm a single > server doing both spam and virus scanning. Keep in mind that we have > MANY end users that have their incoming and outgoing server set to > this main server and it is not feasible to change those settings.
You haven't told us how you are interfacing qmail to amavisd-new. If this is a dual-MTA setup, and communication goes over inet socket and speaks SMTP, then placing amavisd on a different box is not a problem, which is what other people here are suggesting. If you use a Unix socket between qmail and amavisd, then you are probably out of luck. Either switch to inet-based socket (which would probably imply a dual-MTA setup, but maybe not, I'm not very familiar with the qmqpqq interface). Another option would be what you had in mind, i.e. modify amavisd to talk to spamd. This wouldn't be a particularly efficient solution, as each mail would have to be passed over some socket one more time. Mark ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
