Re: disinformation newsletter suddenly getting flagged as spam by spam assassin. whitelisting it doesn't help.

Rev. Guido
> Mike Easter

>> 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

I think that is a bad configuration of the SC mail.  SA must use some
resources to do all that it does.  Using SA on mail 'for no [good]
purpose' which has been whitelisted is a waste of resources.  You might
think that it is possibly useful for something to be both whitelisted
and scored, but I think the normal configuration should be for
whitelisting to take place /first/ - before any other screening
tools/rules, and if it is whitelisted nothing else happens.


>> 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.
>
> yes, you're exactly right... and _my_ machine has a procmail rule that
> accepts any sender at disinfo.com without even looking at spam
> assassin, so the fact that it's getting flagged by SA _at_ SC is the
> problem...

But, what is your machine doing even looking at the SA result if it has
been whitelisted?  Just like I think SC shouldn't be SA scoring the item
because it was SC whitelisted, I also think that your system shouldn't
be reading 'somebody else's' SA scoring if it is whitelisted on your
end.

> which brings me back to the question i had initially, which is, is
> there any way to set up a procmail rule _at_ SC, that would fix
> this... my guess is no, because i'd have to have a shell account at
> spamcop.net, but it never hurts to ask...

I think that if people, ie mail clients, were attentioning that it
doesn't make any sense to be doing any more tests on mail after it is
recognized as whitelisted, that someone might answer that.  But not
likely in/from this ng.

-- 
Mike Easter
kibitzer, not SC admin