Messages delivered locally to the same domain on a Windows Server behind the NAT are being marked as SPAM by SpamAssassin:

Follow

Comments

4 comments

  • Avatar
    Mohamed Adil

    We are facing the same behavior in linux. Kindly provide us the similar steps.

  • Avatar
    Alexandr Redikultsev

    Hi @Mohamed Adil,

    The same configuration file on linux is /etc/spamassassin/local.cf, so you can try adding the directives there.

  • Avatar
    Mohamed Adil

    Thank you for the response. The message header shows a spam score of 9.4. with the below message.

    X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on docker-pluto  
    X-Spam-Flag: YES  
    X-Spam-Level: *********  
    X-Spam-Status: Yes, score=9.4 required=4.0 tests=FSL_HELO_NON_FQDN_1,  
                    HTML_MESSAGE,HTML_MIME_NO_HTML_TAG,MIME_HTML_ONLY,MISSING_DATE,MISSING_MID,  
                    RDNS_NONE,TO_EQ_FM_DIRECT_MX,TO_EQ_FM_HTML_DIRECT,TVD_RCVD_SINGLE  
                    autolearn=no autolearn_force=no version=3.4.0  
    MIME-Version: 1.0  
    Content-Type: multipart/mixed; boundary="----------=_5C611BE0.AF83F33E"  

    So, could we make additional entries to exclude from the total spam score?  Or do you have any recommendations?

  • Avatar
    Ivan Postnikov

    Hi @Mohamed Adil,

    As an alternative solution, I would like to suggest using "trusted_networks" directive.

    The detailed description may be found in official documentation.

     

    Examples:

        trusted_networks 192.168/16 127/8           # all in 192.168.*.* and 127.*.*.*
        trusted_networks 212.17.35.15               # just that host
        trusted_networks 127.                       # all in 127.*.*.*

     

Please sign in to leave a comment.

Have more questions? Submit a request