-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Matt Kettler wrote: | At 11:52 AM 5/5/2004, Sergey Smirnov wrote: | |> I'm using spamassassin 3.0 cvs. |> If incoming message contain few users but only one of them in |> ALL_SPAM_TO all others user also receive message with spam. | | | Yep. That's normal, and is an inherent limitation of spamassassin's | whitelists. | | Fundamentally, whitelists are better done at a higher layer than SA, and | there's nothing SA can do to improve the situation because it's an | inherent limitation of being a mail filter. To improve the problem would | involve changing what SpamAssassin is, and how mail tools call it. It | would also prevent SA from being used in probmail completely. | | SA never sees message envelopes. It does NOT know who will receive a | given message. All it knows is what addresses are in the message headers. | | If you're at the MTA layer, you're even more out of luck, as there's NO | way to improve the situation. At the MTA layer, there's only one | message, despite multiple people. | | If you're at the MDA layer (ie: procmail) you can improve things | slightly. Here there's one delivery per recipeint, and you can do things | like have procmail never call SA in the first place for the user in | question. Or you can use spamc -u and set up true per-user config options. Unfortunately I'm using SA with sendmail + spamass-milter. I can't use common procmail filter because I have to forward messages to M$ Exchange and store copy of message locally. It's easy for me use sendmail aliases than ~/.procmailrc files for each users. Only one person don't want use SA. Of cause he is M$ sysadmin. - -- Sergey Smirnov hkp://wwwkeys.pgp.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFAme4TTW1qobfmhlsRAiVUAJ9/sKOwQDujv49M8mQRMYHw+FxLngCfbhb9 Ask6fQAI3Wp7h4WsKvKbaek= =jGg5 -----END PGP SIGNATURE-----
