Mail delivery failed: returning message to sender
Mail delivery failed: returning message to sender errors are generally encountered when an intended recipient does not exist on the remote server.
You will normally receive a bounceback message with this error in the subject, and the body of the message should contain the original message that was attempting to be sent.
Example bounce-back message
Delivery-date: Thu, 25 Oct 2012 16:42:54 -0400
Received: from mailnull by ecbiz103.inmotionhosting.com with local (Exim 4.77)
for sender@YourDomain.com; Thu, 25 Oct 2012 16:42:54 -0400
From: Mail Delivery System <Mailer-Daemon@ecbiz103.inmotionhosting.com>
Subject: Mail delivery failed: returning message to sender
Date: Thu, 25 Oct 2012 16:42:53 -0400
recipients. This is a permanent error. The following address(es) failed:
No Such User Here
Received: from sender@YourDomain.com by ecbiz103.inmotionhosting.com with local (Exim 4.77)
for recipient@RemoteDomain.com; Thu, 25 Oct 2012 16:42:53 -0400
Subject: [YourDomain.com] Please moderate: "About us"
X-PHP-Script: YourDomain.com/wp-comments-post.php for 220.127.116.11
Date: Thu, 25 Oct 2012 20:42:53 +0000
From: WordPress <wordpress@YourDomain.com>
X-Mailer: PHPMailer 5.1 (phpmailer.sourceforge.net)
Content-Type: text/plain; charset="UTF-8"
E-mail : firstname.lastname@example.org
URL : http://www.paydayspam.com
Comment: Payday loans are available for any occasion!
Resolving Mail delivery failed: returning message to sender bounce-backs
Typically these type of bounceback errors are hard bounces meaning that trying to send the message again won't be successful. You can read our previous article on why does email bounce, bounceback, or error? for a more in-depth explanation of a hard bounce.
In the particular bounce-back example above, the cause of the issue is that this user has WordPress setup to allow comments on posts. A spammer attempted to leave a comment on one of their posts, and the WordPress administrator of this site has setup their e-mail account as recipient@RemoteDomain.com. So that is the address used to send comment moderation requests to. However that e-mail address doesn't exist on the RemoteDomain.com mail server, so it's always going to fail and cause a bounce-back error.
If you happen to also be having issues with WordPress comment spam causing bounce-back errors for your account, we have an advanced article on WordPress comment spam clean up that could help you clear this issue up.
2014-09-13 5:46 am
Thank you for the suggestions. I had tried "add that particular address to the blocked list", but it didn't work. I've resolved the problem now. It was a scorpion virus. I had to pay Norton $99 to uninstall/reinstall Norton antivirus and change my password.
Again, thank you for your suggestion.
2015-03-24 7:21 am
Can you give advice in solving my problem regarding:
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:
SMTP error from remote mail server after end of data:
host aspmx.l.google.com [2a00:1450:4013:c01::1b]:
550-5.7.1 [2a01:5b40:0:252::55 12] Our system has detected that this
550-5.7.1 message is likely unsolicited mail. To reduce the amount of spam sent
550-5.7.1 to Gmail, this message has been blocked. Please visit
550 5.7.1 more information. w1si16472613wix.3 - gsmtp
------ This is a copy of the message, including all the headers. ------
2015-03-24 8:54 am
Thank you for your question. The content of this email message is being flagges bu Google as spam.
The link you provided, included more in-depth information from Google.
I recommend avoiding common words that trigger spam filters.
Also, SPF records and Domain Keys can verify your emails are being sent un-tampered from a valid server.