> The SpamAssassin ALL_SPAM_TO mechanism only works if the given email > address appears in the TO: or CC: lines of the email itself. It does
Yes, it does. > not examine the delivery envelope. Thus BCC'ed emails, those delivered > by mailing lists, or those with fake TO: lines will not have the > negative score modifier applied. What do you mean with "fake TO:" ? > How are you feeding your message to SA? Might it be possible to simply not > invoke SA at all for specific recipients? EG. If calling SA from procmail, > check > the username before calling SA. Unfortunately this is not possible, because we have to add/remove accounts from time to time and anything should be as simple as possible (by using the known GUI). I did some investigation, perhaps it helps you to give me more advise, because it's becoming more stranger: I sent an e-mail from a third party account (webmail service) to one "get all spam" e-mail address. The important header parts are: X-Spam-Status: No, hits=-101.195 tagged_above=-999 required=5 tests=BAYES_00, BLANK_LINES_70_80, USER_IN_ALL_SPAM_TO X-Spam-Level: Seems to work well. Then I sent an e-mail from within our network (they have two servers, my account is on the first, the above "get all spam" account on the other): X-Spam-Status: No, hits=-9.8 tagged_above=-999 required=5 tests=ALL_TRUSTED, BAYES_00, USER_IN_WHITELIST X-Spam-Level: X-Spam-Status: No, hits=-108 tagged_above=-999 required=5 tests=BAYES_00, USER_IN_ALL_SPAM_TO, USER_IN_WHITELIST X-Spam-Level: Do you note about the two spam checks performed there ? Is this intended ? Something to fix ? Could this be affiliated with the problem ? Anyway, the sender are located outside; I just wondered about my own testing results... so it shouldn't be an issue, but who knows. Tobias.
