SPF Notification question

Greetings.  I am pretty sure I have our SPF (TXT) record set up properly in DNS, but every so often we get an undeliverable message with an SPF link similar to:

Please see http://www.openspf.org/Why?xxxxxxxxxxxx

The resulting suggestion from Openspf.org is:

----------------------
MX1 rejected a message from a mail server claiming to be mail.our_domain.org.

MX1 received a message from mail.our_domain.org (xx.x.xxx.xx) from a mail server claiming to be mail.our_domain.org.

The domain mail.our_domain.org has not published an SPF policy. It is possible that the receiving mail server refuses all mail from domains that do not have an SPF policy.
----------------------

My guess is that the recipient's mail server or hosted filtering is doing a reverse DNS for:  mail.our_domain.org  or their SPF check is mistaking our "domain" as:  mail.our_domain.org  .... instead of correctly identifying our domain as:   our_domain.org

Suggestions ?  Anything we should change or is this a misconfiguration on the recipient's side ?

Thanks much.
-Stephen
lapavoniAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

mikebernhardtCommented:
Well, was the IP address or name "mail.our_domain.org" valid? Was the message it rejected valid? The last sentence could just be a weirdness in the message, but the first 2 look like they COULD be correct. The whole point of SPF is for the remote mail server to check if the sending server is legit.
0
lapavoniAuthor Commented:
Yes the IP address and server name are correct.  However, if they're looking for a domain named "mail.our_domain.org", they won't find it.  "mail.our_domain.org" isn't a domain - it's an mx record under "our_domain.org"
0
gheistCommented:
Would be helpful if you tell your domain so others can confirm your SPF record is present and correct.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

lapavoniAuthor Commented:
Domain is:  fairtradeusa.org
0
mikebernhardtCommented:
It appears that your configuration is correct, so if it's only happening with one destination then I would assume it's a problem on their end. I do notice that
1. the IP address 173.231.134.176 doesn't resolve, but it's in the SPF record. If it isn't valid it should be removed.
2. 74.3.121.58 resolves to both mail.fairtradeusa.org and mail.transfairusa.org, but they are both in the SPF record so it should be OK.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
gheistCommented:
it looks pretty OK
fairtradeusa.org.       3600    IN      TXT     "v=spf1 ip4:74.3.121.58/32 ip4:173.231.134.176/32 a:mail.transfairusa.org a:mail.fairtradeusa.org include:spf.protection.outlook.com -all"

i think /32 are obsolete
a: ? could taht be just mx/24 ?
Why would your rwcipiwnts need to do 5 DNS lookups to accept your mail? use IPs for hostnames.
0
lapavoniAuthor Commented:
OK, thank you both for the suggestions.  I removed the /32 and the 173.231.134.176.  This IP is our static IP for our webserver.  Seems irrelevant as our mail server is completely separate.  I looked at our SMTP logs and all EHLO/HELO are for: mail.fairtradeusa.org   We had a previous CERT in the past that only had:  mail.transfairusa.org , so I think that was a remnant, but we still use that as an accepted domain for our Exchange server.

I am thinking the few SPF undeliverables are just unhappy or misconfigured servers on the other end.  I checked past undeliverables and noticed a few "grey listed" messages.  Interesting concept - grey listing.  Didn't look like the best way to protect against SPAM to me ... but maybe it used to be very effective - I don't know.
0
gheistCommented:
Make it soft fail  ~all and maybe remote site loads your SPF record sooner or later.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Servers

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.