parsaCr7x
September 2nd, 2016, 22:30
Hello my friend
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
Return-path: <>
Envelope-to: sender@example.com
Delivery-date: Thu, 25 Oct 2012 16:42:54 -0400
Received: from mailnull by ecbiz103.inmotionhosting.com with local (Exim 4.77)
id 1TRUGT-0005Qd-RT
for sender@example.com; Thu, 25 Oct 2012 16:42:54 -0400
X-Failed-Recipients: recipient@RemoteDomain.com
Auto-Submitted: auto-replied
From: Mail Delivery System <Mailer-Daemon@ecbiz103.inmotionhosting.com>
To: sender@example.com
Subject: Mail delivery failed: returning message to sender
Message-Id: <E1TRUGT-0005Qd-RT@ecbiz103.inmotionhosting.com>
Date: Thu, 25 Oct 2012 16:42:53 -0400
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:
recipient@RemoteDomain.com
No Such User Here
------ This is a copy of the message, including all the headers. ------
Return-path: <sender@example.com>
Received: from sender@example.com by ecbiz103.inmotionhosting.com with local (Exim 4.77)
(envelope-from <sender@example.com>)
id 1TRUGT-0005QT-Q5
for recipient@RemoteDomain.com; Thu, 25 Oct 2012 16:42:53 -0400
To: recipient@RemoteDomain.com
Subject: [example.com] Please moderate: "About us"
X-PHP-Script: example.com/wp-comments-post.php for 123.123.123.123
Date: Thu, 25 Oct 2012 20:42:53 +0000
From: WordPress <wordpress@example.com>
Message-ID: <82f2c6cb759fb7e7c03356a25c799790@example.com>
X-Priority: 3
X-Mailer: PHPMailer 5.1 (phpmailer.sourceforge.net)
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="UTF-8"
A new comment on the post "About us" is waiting for your approval
http://example.com/
Author : Payday loans (IP: 123.123.123.123)
E-mail : payday@spam.com
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? (http://www.inmotionhosting.com/support/email/email-troubleshooting/email-bounce-bounceback-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 theaddress 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 (http://www.inmotionhosting.com/support/edu/wordpress/320-wordpress-comment-spam) that could help you clear this issue up.
---
that is my webmail here:
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:
max.dadoua@wanadoo.fr
host smtp-in.orange.fr [193.252.22.65]
SMTP error from remote mail server after initial connection:
550 mwinf5c04 ME Adresse IP source bloquee pour incident de spam. Client host blocked for spamming issues. OFR006_102 Ref http://csi.cloudmark.com/reset-request/?ip=136.243.108.62 [102]
Reporting-MTA: dns; server2.easy-dns-name.in
Action: failed
Final-Recipient: rfc822;max.dadoua@wanadoo.fr
Status: 5.0.0
Remote-MTA: dns; smtp-in.orange.fr
Diagnostic-Code: smtp; 550 mwinf5c04 ME Adresse IP source bloquee pour incident de spam. Client host blocked for spamming issues. OFR006_102 Ref http://csi.cloudmark.com/reset-request/?ip=136.243.108.62 [102]
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
Return-path: <>
Envelope-to: sender@example.com
Delivery-date: Thu, 25 Oct 2012 16:42:54 -0400
Received: from mailnull by ecbiz103.inmotionhosting.com with local (Exim 4.77)
id 1TRUGT-0005Qd-RT
for sender@example.com; Thu, 25 Oct 2012 16:42:54 -0400
X-Failed-Recipients: recipient@RemoteDomain.com
Auto-Submitted: auto-replied
From: Mail Delivery System <Mailer-Daemon@ecbiz103.inmotionhosting.com>
To: sender@example.com
Subject: Mail delivery failed: returning message to sender
Message-Id: <E1TRUGT-0005Qd-RT@ecbiz103.inmotionhosting.com>
Date: Thu, 25 Oct 2012 16:42:53 -0400
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:
recipient@RemoteDomain.com
No Such User Here
------ This is a copy of the message, including all the headers. ------
Return-path: <sender@example.com>
Received: from sender@example.com by ecbiz103.inmotionhosting.com with local (Exim 4.77)
(envelope-from <sender@example.com>)
id 1TRUGT-0005QT-Q5
for recipient@RemoteDomain.com; Thu, 25 Oct 2012 16:42:53 -0400
To: recipient@RemoteDomain.com
Subject: [example.com] Please moderate: "About us"
X-PHP-Script: example.com/wp-comments-post.php for 123.123.123.123
Date: Thu, 25 Oct 2012 20:42:53 +0000
From: WordPress <wordpress@example.com>
Message-ID: <82f2c6cb759fb7e7c03356a25c799790@example.com>
X-Priority: 3
X-Mailer: PHPMailer 5.1 (phpmailer.sourceforge.net)
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="UTF-8"
A new comment on the post "About us" is waiting for your approval
http://example.com/
Author : Payday loans (IP: 123.123.123.123)
E-mail : payday@spam.com
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? (http://www.inmotionhosting.com/support/email/email-troubleshooting/email-bounce-bounceback-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 theaddress 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 (http://www.inmotionhosting.com/support/edu/wordpress/320-wordpress-comment-spam) that could help you clear this issue up.
---
that is my webmail here:
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:
max.dadoua@wanadoo.fr
host smtp-in.orange.fr [193.252.22.65]
SMTP error from remote mail server after initial connection:
550 mwinf5c04 ME Adresse IP source bloquee pour incident de spam. Client host blocked for spamming issues. OFR006_102 Ref http://csi.cloudmark.com/reset-request/?ip=136.243.108.62 [102]
Reporting-MTA: dns; server2.easy-dns-name.in
Action: failed
Final-Recipient: rfc822;max.dadoua@wanadoo.fr
Status: 5.0.0
Remote-MTA: dns; smtp-in.orange.fr
Diagnostic-Code: smtp; 550 mwinf5c04 ME Adresse IP source bloquee pour incident de spam. Client host blocked for spamming issues. OFR006_102 Ref http://csi.cloudmark.com/reset-request/?ip=136.243.108.62 [102]