Blacklisting for spam protection does not work

Follow

Comments

3 comments

  • Avatar
    Dan Wright (Edited )

    A couple of things:

    1) There should be a way to direct Postfix to use an alternate resolver instead of having to make a change system-wide like this from resolv.conf or named.conf.

    2) Regardless, I changed to OpenDNS as suggested and get the proper dig +short response, but still failing the nelson-sbl-test @ crynwr.com test as outlined here https://support.plesk.com/hc/en-us/articles/213416729-How-to-check-whether-spam-protection-based-on-spamhaus-org-blacklists-is-working

  • Avatar
    Dan Wright

    I believe I found resolution. In my main.cf file, one of my entries smtpd_client_restrictions had the directive "permit" in front of the rbls for some reason. Placing that directive at the end of the line appears to have re-activated my bl's!

  • Avatar
    Denis Bykov

    @Dan

    These are limitations on the side of DNS provider. Postfix is using nameservers configured on the system.

    Thank you for sharing the information regarding the issue. Indeed, the Postfix decides whether to block the message on not based on the first applicable directive, therefore directive order matters.

Please sign in to leave a comment.

Have more questions? Submit a request