Re: disinformation newsletter suddenly getting flagged as spam by spam assassin. whitelisting it doesn't help.
"Mike Easter" <[email protected]>
| Newsgroups | gmane.mail.spam.spamcop.email |
|---|---|
| Organization | SpamCop |
| Message-ID | <[email protected]> |
I was misunderstanding the problem when we were talking before. I tho't spamcop was tagging as spam and putting into held mail in spite of being whitelisted.... Rev. Guido > spamcop, > is letting the mailing list through (probably because i have > whitelisted it on webmail), .... you are saying that SC isn't putting in held mail, but, in spite of being whitelisted, it is still being 'examined' by SA > but it's getting flagged as spam by spam > assassin, That examination by SA is making a SA score, in the tracker you provided, the score would be a SA spam score > and when it arrives on my machine, instead of getting > routed to the disinformation mailbox, it gets routed to the spam > mailbox. Something in your system is reading the SA result that SC assigned and flagging as spam > i'm sure that it's not my mailserver that is flagging it as > spam, because on my mailserver i have a procmail rule that makes an > end run around spam assassin when it encounters a sender address at > disinfo dot com. Your system 'avoids' the SA scoring when something is whitelisted; but in this case SC has already provided a SA scoresheet even tho it was whitelisted, which results in your system flagging as spam, even tho' SC didn't [because of the whitelist] > the only other place that i know of that's filtering > my mail through spam assassin is spamcop. > > here's a tracking URL if that will help: www.spamcop.net/sc?id=z730077084zf01b5c5b0e8415125bb1bcee1184e3a7z That tracker shows that SC passed the item X-SpamCop-Whitelisted: [email protected] but then proceeded to rate it with SA 'anyway' X-Spam-Status: Yes, score=7.5 When your system gets/sees an item with a positive SA score, it is calling it spam. I don't have the 'answer' to your problem, but at least I understand it correctly now, whereas I didn't before. -- Mike Easter kibitzer, not SC admin