SpamAssassin classifies MailScanner reports like SPAM

[John Wilcock]

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.

-- 
John

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:
>
>     Hi,
>
>     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
>                                 isn't
>      1.1 SUBJ_ILLEGAL_CHARS     Subject: has too many raw illegal
>     characters
>      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
>                                 encoding
>
>
>     Subject and body are UTF-8.
>
>
>     Regards!
>     Valentin Laskov
>
>
>
>     -- 
>     MailScanner mailing list
>     mailscanner at lists.mailscanner.info
>     <mailto:mailscanner at lists.mailscanner.info>
>     http://lists.mailscanner.info/listinfo/mailscanner
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mailscanner.info/pipermail/mailscanner/attachments/20160323/9133f970/attachment.html>