Zach, > I'm implementing per-user scanning with SQL bayes and user prefs by > using spamc as a primary filter, then calling amavis as a secondary > filter. However, I'd like to amavis to still be able to quarantine > spam. So, I see 2 possibilities: > > 1.) An option to inject mail to amavis that immediately quarantines > the message
Hm. If you could persuade your spam filter to forward spam to a separate TCP port on amavisd-new (either directly, or indirectly through MTA), then you could fiddle with a policy bank on such a port, e.g. by setting kill_level to very low value (negative). It might need a tiny tweak to treat no-score as zero score (the 2.4.0 will behave this way by default). > 2.) Having an option for amavis to honor existing Spam headers and > quarantine appropriately. Does the spamc/spamd remove pre-existing X-Spam-* header fields? If not, you can't trust these headers. Modifying amavisd-new to believe such headers would be possible and not much work, although I don't think there is a patch floating around. > Is there any thing already existing to achieve either of these? I think not, you will have to modify few lines in amavisd. Mark ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
