On 7 Apr 2018, at 8:08 (-0400), Robert Boyl wrote:
Hi, everyone
Pls...
Is this still an active spamassassin test?
No. It is a 'sandbox' rule that got auto-promoted at some point and was
auto-demoted March 12. If you run sa-update daily and restart any
persistent processes using the rules afterwards, you will keep up with
those automatic changes.
header __FSL_HAS_LIST_UNSUB exists:List-Unsubscribe
meta FSL_BULK_SIG ((DCC_CHECK || RAZOR2_CHECK ||
PYZOR_CHECK)
&& !__FSL_HAS_LIST_UNSUB)
describe FSL_BULK_SIG Bulk signature with no Unsubscribe
Had some odd false positive due to its high score of 1,35...
It was a forgot password message... and it scored "Bulk signature with
no
Unsubscribe".
Which is probably not wrong. Password reset messages are usually quite
similar to each other, just like a large fraction of spam, and there's
little point in them having unsub links.
Seems strange as it depends on DCC, Razor, Pyzor, systems that I also
see
score wrongly.
Those are all primarily distributed bulk detectors, rather than spam
detectors. Currently they each score about 1, so even if they all hit
simultaneously on non-spam bulk mail (which they rarely do) there needs
to be something else spammy about a message to push it into the 'spam'
classification with the standard threshold of 5. If you're using a lower
threshold (as I do) you should have carefully-managed local rules and
score adjustments, and have a valid reason to believe that your mail
flow fits that divergence.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Currently Seeking Steady Work: https://linkedin.com/in/billcole
