Hi,
I have a bit of a puzzler. I have a client whose MX records have recently (early last week, or late the week before) changed to a spam filtering and forwarding service. No problem; they have an A record that holds their real mail recipient address.
The have the following SPF record:
v=spf1 +a +mx +include:smtp.secureserver.net -all
They have a grand total of 3 A records (counting the "@" record), and 3 MX records.
When they try to send to certain clients, they're getting the following bounce message (snipping the confidential stuff):
When I go to the linked website, I get this:
Katie
I have a bit of a puzzler. I have a client whose MX records have recently (early last week, or late the week before) changed to a spam filtering and forwarding service. No problem; they have an A record that holds their real mail recipient address.
The have the following SPF record:
v=spf1 +a +mx +include:smtp.secureserver.net -all
They have a grand total of 3 A records (counting the "@" record), and 3 MX records.
When they try to send to certain clients, they're getting the following bounce message (snipping the confidential stuff):
Your message did not reach some or all of the intended recipients.
Subject: RE: <snip>
Sent: 9/9/2014 7:58 AM
The following recipient(s) cannot be reached:
<snip> on 9/9/2014 7:58 AM
You do not have permission to send to this recipient. For assistance, contact your system administrator.
<<snip A record name of their SMTP server> #5.7.1 smtp;550 5.7.1 Client host rejected: Please see email address>&ip=<snip IP address of their SMTP server>&receiver=>
When I go to the linked website, I get this:
rejected a message that claimed an envelope sender address of <snip>.
received a message from <snip> (<snip - confirmed IP address is correct>) that claimed an envelope sender address of <snip>.
The domain spf100.secureserver.net has published an SPF policy, however, an error occurred while the receiving mail server tried to evaluate the policy:
Maximum DNS-interactive terms limit (10) exceeded.
What should I do?
The domain spf100.secureserver.net will have to fix the problem. You can contact the spf100.secureserver.net postmaster and tell them about the error message you received.
Katie