You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2017/12/04 20:18:19 UTC

[Bug 7512] Change the default score of SPF_NONE to 0.001

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7512

Bill Cole <sa...@billmail.scconsult.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sa-bugz-20080315@billmail.s
                   |                            |cconsult.com

--- Comment #1 from Bill Cole <sa...@billmail.scconsult.com> ---
-1

Of the 7742 messages in my current log which reached SA (lots do not...) and
were not local (i.e. not ALL_TRUSTED) 1020 had no SPF rule match, i.e. they
would match SPF_NONE but for it not having a score. 1003 of those had negative
scores, largely but not entirely due to various forms of provisional
whitelisting of the sender or recipient. 13 were rejected, all correctly based
on what was logged about them. There were no messages within 0.5 on either side
of my rejection threshold.

This may be skewed by my subscription to a few mailing lists run by fairly
mail-savvy entities:

bigsky:~ root# host -t txt mailop.org
mailop.org has no TXT record
bigsky:~ root# host -t txt postfix.org
postfix.org has no TXT record
bigsky:~ root# host -t txt lists.cymru.com
lists.cymru.com has no TXT record
bigsky:~ root# host -t txt lists.freron.com
lists.freron.com has no TXT record


Absent the RuleQA process revealing SPF_NONE to be actually useful in
differentiating between spam and ham on more diverse mailstreams, I don't see a
case for scoring it on theological grounds.

-- 
You are receiving this mail because:
You are the assignee for the bug.