SpamAssassin classifies MailScanner reports like SPAM
john at tradoc.fr
Wed Mar 23 14:40:50 UTC 2016
I beg to differ. If MailScanner reports are not RFC-compliant with
regard to non-ASCII characters (which is what these SpamAssassin rules
are effectively testing), then that's a bug in MailScanner.
That said, I agree entirely with your recommendation to turn off
scanning for MailScanner-generated messages.
Le 23/03/2016 à 15:04, Alex Neuman a écrit :
> No. It's a feature. Turn off scanning from the host itself or the
> report address + localhost if you want to be thorough.
> On Mar 23, 2016 8:30 AM, "Valentin Laskov" <it at festa.bg
> <mailto:it at festa.bg>> wrote:
> This is a bug report (likely).
> SpamAssassin classifies MailScanner report messages like SPAM:
> 0.0 PP_MIME_FAKE_ASCII_TEXT BODY: MIME text/plain claims to be
> ASCII but
> 1.1 SUBJ_ILLEGAL_CHARS Subject: has too many raw illegal
> 2.0 DSN_NO_MIMEVERSION Return-Path <> and no MIME-Version: header
> 0.1 SUBJECT_NEEDS_ENCODING Subject is encoded but does not
> specify the
> Subject and body are UTF-8.
> Valentin Laskov
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> <mailto:mailscanner at lists.mailscanner.info>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MailScanner