Take the 2-minute tour ×

This question already has an answer here:

Our website is sending out email verifications to members who sign up with our service.

Yahoo is throwing our messages in the spam box and displaying this message in the headers:

Received-SPF: none (domain of -.com does not designate permitted sender hosts)

I'm pretty sure this is the reason why.

I added a text record to our DNS:

v=spf1 mx:smtp.secureserver.net +all

Maybe I didn't set it up right? The yahoo message remains.

Our email has html and text versions and has received a score of .07 on spamassassin, so I highly doubt that anything in the email content itself is throwing a flag.

share|improve this question

marked as duplicate by TheCleaner, Katherine Villyard, Rex, mdpc, Ward Feb 22 at 5:05


2 Answers 2

up vote 3 down vote accepted

synergyweight.com. 3600 IN TXT "v=spf1 mx:smtp.secureserver.net +all"

There are several issues with your SPF record.

The mx field matches the MX record of the given domain. smtp.secureserver.net does not have an MX record. You probably intended on using a:smtp.secureserver.net or mx:synergyweight.com.

The +all mechanism matches and passes anything, which undermines the purpose of having an SPF record in the first place. -all (fail) or ~all (softfail) would be better choices.

share|improve this answer
thank you, I had the smtp wrong. It was a:smtpout.secureserver.net –  prospector Feb 19 at 23:53
@Prospector After reading your other comments that provide more details on your specific scenario you probably want to use a rule like this: "v=spf1 a:synergyweight.com include:secureserver.net -all" –  Mark Sturgill Feb 19 at 23:54
@Prospector In any case GoDaddy should be able to provide you with the correct fields to include in your SPF record. –  Michael Hampton Feb 20 at 0:18

Your SPF record contains +all, which means that everyone on the Internet is permitted to send mail for your domain.

Since this is obviously ridiculous, it's treated as though you don't have an SPF record.

Perhaps you meant to use -all instead, meaning that no one except those you designated elsewhere in the SPF record can send mail for your domain.

share|improve this answer
thank you for pointing that out, I changed it and am testing at the moment –  prospector Feb 19 at 23:39
No, it doesn't. –  Michael Hampton Feb 19 at 23:44
I know it doesn't, but here is my concern. If I allow that IP address, how will I know that godaddy will not send out the next email from a different ip address? –  prospector Feb 19 at 23:49
@Prospector You don't, so you probably want a rule like this: "v=spf1 a:synergyweight.com include:secureserver.net -all" –  Mark Sturgill Feb 19 at 23:49
