Fred Bennett wrote:> > I have SA 2.61 running spamd on a Mandrake server with Postfix. It > sends mail to our Exchange 2000 server on the LAN. All is ok, except > for one user that wants to opt-out. This user wants to get all > messages unmodified by SA (I think header mods would be acceptable as > long as subject and body are unmodified).
Allowing one user to opt-out like this depends a great deal on how you're calling SA. In my case, for instance, if I were using report_safe 0 globally on one server here, I could easily set it to 1 or 2 for a specific user because I'm calling SA from procmail on delivery, not in the middle of the SMTP chain. I can score rules differently, whitelist/blacklist, and set the spam threshold differently for each user. Fortunately for my administrative time, defaults work pretty well for most users- but I *can* (and have) made specific changes for a few users with somewhat unusal mail. On the other machine I run SA on, it's a little different. The first machine only hosts accounts for one domain; the second is our domain hosting server and has ~40 domains right now. I call SA from MIMEDefang, which is called during sendmail's SMTP conversation with the remote host. This machine splits mail streams on a per-domain basis, allowing some individuality for each domain without imposing the load that full per-user preferences would. I'm not sure whether Postfix will allow you to do this sort of per-recipient or group-of-recipients processing; if not it sounds like you might have to redesign your inbound relay server. :/ > This seemed simple enough (all_spam_to), but when I use that or > whitelist_to, it affects a whole bunch of other users. They are all > listed in the To, Cc, and/or Bcc fields as co-recipients. I see that > this is a documented problem on the SA "to-do" list, Which likely wouldn't help in your case, as at the SMTP level there may only be *one* message that SA is working with. :( Unless you can get Postfix to (re)generate a copy of the message for each recipient *before* the SA processing, fixing this SA bug won't help you. > but in the meantime I would like to know if there's another method > that would work. One such method that I've seen suggested is to > set required_hits to a high number for this user, If you do actually have per-user prefs like this, you should also be able to use whitelist_to without trouble. This assumes that you're calling SA in such a way that it runs once for each recipient. Good luck. -kgd -- "Sendmail administration is not black magic. There are legitimate technical reasons why it requires the sacrificing of a live chicken." - Unknown ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
