• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved SPF is rejecting Spamexperts delivery servers

Dennis de Jong

New Pleskian
Dear Plesk,

An costumer of our corporation uses an externtal Spamexperts server and not the extension for Plesk. Sometimes its working just fine but the costumer says sometimes the email is rejected by the SPF on our server. The costumer do not know this but I can see this in our log file when I connect with SSH.

Code:
Jul  5 16:35:36 ds01 postfix/cleanup[11541]: 76C6CE82125: milter-reject: END-OF-MESSAGE from mx54.antispamcloud.com[2a00:1630:2:80a::1]: 5.7.23 SPF validation failed. Please see http://www.openspf.org/Why?id=sender%40domain.nl&ip=2a00%3a1630%3a2%3a80a%3a%3a1&receiver=server@domain.nl : Reason: mechanism; from=<sender@domain.nl> to=<receiver@domain.nl> proto=ESMTP helo=<mx54.antispamcloud.com>

The problem is that the SPF check is reacting on the sender@domain.nl SPF record, he expect the *.antispamcloud.com in the sender@domain.nl SPF record. This is not possible because every sender@domain.nl that sends mail to this receiver@domain.nl will need the *.antispamcloud.com SPF record in their DNS settings.

I also added Spamexperts delivery.antispamcloud.com on the whitelist of Postfix (see: How To Whitelist Hosts/IP Addresses In Postfix).

This also doesn't work, I don't see any option in Plesk to add domains or wildcard domains to the whitelist so that the SPF wil bypass this domains.

Is there anything I can do because the costumer can't receive some email now because the SPF is rejecting Spamexperts on our server.

Please let me know what I can do about this problem so I can bypass SPF check for Spamexperts delivery servers.

Cheers,
Dennis de Jong
 
Last edited:
Dear Plesk,

I found a solution to this, adding include:delivery.antispamcloud.com to the SPF local rules in the Mail Server Settings seems to work.

KFORn2R.png


I will close this issue and turn it to resolved.

Thanks,
Dennis de Jong
 
Back
Top