If you get this error it means the message failed permanently, at the receivers server normally it will generate a bounce bounce back to the sender....and will not be re-delivered or re-tried.
example:
554 Denied - Denied for Spam Content
Solution:
If you believe that the message is legitimate and should be delivered, contact the recipient and let them know what you are seeing and request that they Whitelist / Allow your sending address.
Why this happens?
Although any spam filtering, Firewall or Mail Server can reply with a similar type of error this normally happens when the recipients server is using some type of spam filtering service.
Here are some of the common Spam Filtering service that are know to send back a 554 Denied
MXLogic AKA McAfee
Example Error
host domain.com.inbound15.mxlogic.net[208.65.144.12] said: 554 Denied (Mode:normal) (in reply to end of DATA command)
Resolution/Workaround
For McAfee SaaS Customers, please do one or more of the following:
1. Place the sending domain on the User or Domain-Level allow list in the Control Console. For instructions on how to do this, please refer to Adding to Domain-level Sender Allow List
see full description here: https://support.mcafeesaas.com/MCAFEE/_cs/AnswerDetail.aspx?sSessionID&aid=155
Godaddy
554 This IP has been temporarily blocked for attempting to send too many messages containing content judged to be spam by the Internet community. IB110
for the full details click here: https://support.godaddy.com/help/article/3568/dealing-with-email-bouncebacks
TIP: In some cases if you get 554 Denied "RELAY is NOT ALLOWED" then the issue is actually on the sending end normally means that when you try to send the message the sending server didn't trust your message and bounced it back, this normally happens if your IP or Domain is not recognized by the sending server as valid.
A blog about all the technical stuff.. come along for the ride and you might learn a thing or two.
Showing posts with label sent. Show all posts
Showing posts with label sent. Show all posts
Tuesday, December 9, 2014
Wednesday, November 19, 2014
SPF Record error when sending mail 551 5.0.0 Rejected
If you get the following error when sending a message, as a bounce back NDR notification
Remote Server returned '<mx.mail.google.com #5.0.0 smtp; 551 5.0.0 Rejected, look at http://www.openspf.org/why.html?sender=al@topel.com&ip=69.84.129.239&receiver=mailin1-trm.thomsonreuters.com>'
This means that the recipient server is doing an SPF record check and it doesn't match.
What needs to match?
The IP of the server you are using needs to be added to the SPF record also known as a TXT record in your DNS you can perform an SPF look-up by going to:
http://mxtoolbox.com/SuperTool.aspx?action=spf%3a&run=networktools
Explained:
Remote Server returned '<mx.mail.google.com #5.0.0 smtp; 551 5.0.0 Rejected, look at http://www.openspf.org/why.html?sender=al@topel.com&ip=69.84.129.239&receiver=mailin1-trm.thomsonreuters.com>'
This means that the recipient server is doing an SPF record check and it doesn't match.
What needs to match?
The IP of the server you are using needs to be added to the SPF record also known as a TXT record in your DNS you can perform an SPF look-up by going to:
http://mxtoolbox.com/SuperTool.aspx?action=spf%3a&run=networktools
Explained:
Sender Policy FrameworkWhy | |
|
Labels:
551 5.0.0 Rejected,
bounceback,
DNS,
email,
fix,
issue,
messages,
moved,
NDR,
new client,
notification,
record,
send,
sent,
SMTP,
SPF
Subscribe to:
Posts (Atom)