We run cPanel servers and scan every outbound message with SA in order
to reduce the amount of garbage that comes through website contact forms.
However, in a default cPanel configuration, HAS_X_OUTGOING_SPAM_STAT
scores a whopping 2.3. I'm not sure what the distribution default is but
that's enough to move a lot of messages to spam, simply because the
sender was scanning messages. Sure spammers are going to be putting that
header in, but as far as I can tell, that's an argument for always
scoring the rule at a hard zero. I can see how it might be useful in a
meta with some other indicators, but as it stands, it's penalizing both
the guys trying to stop spam at the source and the spammers and that
seems counterproductive.
--
For SpamAsassin Users List
