Tom, | > Turning on SA auto whitelists is presently not useful | > with amavisd-new. There is a fundamental problem in that | > SpamAssassin is geared to work fine with one-recipient- | > -at-a-time messages, and amavisd-new tries to process | > multi-recipient messages in one go if at all possible | | I thought that something like postfix wouldn't break the email up | into multiple deliveries until after it had passed through the | advanced filter portion of the process.
Right. It doesn't. | Given that process flow, the email would still be processed once. | | Even if amavisd-new processes multi-recipient messages in one pass | (I assume that md5-hash has something to do with this) then | wouldn't the disposition w.r.t. spam be retained as well and | therefore the AWL would only be adjusted the one time that the | email passed through amavisd? - AWL is supposed to be per-recipient. Each recipient has its own automatically updated whitelist. - amavisd-new has no way of telling SA what the envelope recipients are (SA can only guess that from the header, and this can only work when SA is called at the final stage from the local delivery agent (e.g. procmail), when there is already only a single recipient) | If you went through the AWL for the amavis user once for each | reciptient you would really screw up the AWL ratings, but the same | would be true for the Bayesian filter statistics... Although Bayesian works best when it is trained for a particular user, it is still _very_ useful with a single site-wide database. Given a larger set of ham/spam messages to train, the lack of specialization can be compensated to some degree. AWL on the other hand (as I understand it) is only useful as a per-recipient information. (but I may be wrong here) | Is there any way to enable SA auto whitelist? Or is it S.O.L. You can turn it on, but it will always see only one a.w. list, namely the one belonging to used amavis (or vscan) - as things stand now. Some special AWL handling would need to be devised, and it is not high on my priority list. Btw: | (I assume that md5-hash has something to do with this) then Well, not directly, it solves the opposite problem. The cache of body digests is used to save time on calling SpamAssassin and virus checkers when the same message content comes-in as separate messages, close one after the other, such as with some poor-man's mailing lists or in spam bursts. Mark ------------------------------------------------------- This SF.NET email is sponsored by: The Best Geek Holiday Gifts! Time is running out! Thinkgeek.com has the coolest gifts for your favorite geek. Let your fingers do the typing. Visit Now. T H I N K G E E K . C O M http://www.thinkgeek.com/sf/ _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
