All Products 
Username / Customer#
Password
Log In
 Hi,  |  Log Out
  • Site Search
  • Domain Search
  • WHOIS Domain Check
24/7 Support: (480) 505-8877
Hablamos Español
9 AM to 9 PM IST
7 days a week
Go Daddy Support

Search help articles, forums, and discussion groups

Incoming mail bounced for SPF fail

Viewing post 1 to 5 (5 total posts)
Profile picture of esc952

esc952 said 1 year ago:

I have a friend, whose email server is SPF compliant, but when he sends me email GoDaddy is bouncing it back as:

72.167.238.201 failed on DATA command.
Remote host said: 550 5.7.1 SPF unauthorized mail is prohibited.

Can anyone help us resolve this issue?

Profile picture of bryceh

GoDaddy Expert bryceh said 1 year ago:

@esc952

This error generally means that the domain on the sending email address has an SPF record and the sending email server is not authorized to send email from the domain due to the SPF record in place.

To resolve this issue, have your friend modify their current SPF record to include the server they are trying to send from or remove the SPF record from the domain.

Hope this helps!

-Bryce

Profile picture of esc952

esc952 said 1 year ago:

We do not believe this is the case. Mine is the only email address from which he gets email bounced back.

I’ve asked him to verify his SPF record and ISP’s domain. However, I’m pretty confident the problem is a something involving GoDaddy accepting his ISP’s SPF-compliant email.

FYI, here is a copy of a sample email that failed:

Hi. This is the qmail-send program at taz6.fiberhosting.com.
I’m afraid I wasn’t able to deliver your message to the following addresses.
This is a permanent error; I’ve given up. Sorry it didn’t work out.

<my email address removed>:
72.167.238.201 failed on DATA command.
Remote host said: 550 5.7.1 SPF unauthorized mail is prohibited.

— Below this line is a copy of the message.

Return-Path: <sender’s email address removed>
Received: (qmail 3186 invoked from network); 25 Apr 2012 12:58:06 -0400
Received: from in-71-50-203-104.dhcp.embarqhsd.net (HELO office) (71.50.203.104)
by virtual.fiberhosting.com with SMTP; 25 Apr 2012 12:58:06 -0400
Message-ID: <003101cd2304$960c9220$0302a8c0@office>
From: “Steve ABC” <sender’s email address removed>
To: “Ed XYZ” <my email address removed>
Subject: TEST
Date: Wed, 25 Apr 2012 12:58:06 -0400
Organization: Company name removed
MIME-Version: 1.0
Content-Type: text/plain;
charset=”Windows-1252″
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.2001
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.2001

TEST

Profile picture of ChrisG

GoDaddy Expert chrisg said 1 year ago:

@esc952,

As @bryceh pointed out, the error indicated in the bounce is a straight forward message indicating issues with the SPF record of the domain attempting to send to our servers.

If you have not done so already, I would recommend reaching out to our Live Support to provide a complete copy of the bounced email being received as a separate file attachment. You should be able to email this direct to support@godaddy.com.

Christopher G.

Profile picture of The_Merg

the_merg said 1 month ago:

I realize this is an old thread, but I was having the same issue as well. One company that deal with would have e-mails to me bounced back due to this error. I was the only person that they had this issue with. GoDaddy support put it off that the issue was with the sender. If the issue was with the sender, they would have had a lot more bouncebacks than just me. I have my domains hosted by GoDaddy and e-mail hosted by GoDaddy. The company could not send to any of my e-mail addresses. I created a Gmail account and they could send to me without issue.

Something is definitely not working right with GoDaddy. I find it hard to believe that the SPF record at the sender is not set up right yet only my e-mail addresses don’t work.

- Merg

Add a reply:

You will auto join this group when you reply to this topic.

When posting about a technical issue, please be sure to include as many details as possible, such as your domain name, related URLs and other pertinent information. This consideration will allow us to better understand the situation and quickly assist you.