Exchange
--
Questions
--
Followers
Top Experts
Returned Mail
We have a client that tried to send one of our employees an email and got the following returned mail message:
From: Mail Delivery Subsystem <MAILER-DAEMON@mx202.mails
Date: Tue, Mar 2, 2010 at 6:45 AM
Subject: Returned mail: see transcript for details
To: Client@ClientDomain.com
The original message was received at Mon, 1 Mar 2010 17:33:18 +0300
from mail-iw0-f187.google.com [209.85.223.187]
----- The following addresses had permanent fatal errors -----
<EmployeeA@Company.com>
(reason: 354 go ahead)
<EmployeeB@Company.com>
(reason: 354 go ahead)
----- Transcript of session follows -----
554 5.5.0 Remote protocol error
Final-Recipient: RFC822; EmployeeA@Company.com
Action: failed
Status: 5.5.1
Remote-MTA: DNS; server.company.com
Diagnostic-Code: SMTP; 354 go ahead
Last-Attempt-Date: Tue, 2 Mar 2010 02:45:11 +0300
Final-Recipient: RFC822; EmployeeB@Company.com
Action: failed
Status: 5.5.1
Remote-MTA: DNS; server.company.com
Diagnostic-Code: SMTP; 354 go ahead
Last-Attempt-Date: Tue, 2 Mar 2010 02:45:11 +0300
---------- Forwarded message ----------
Anyone know what could be causing this? The same client was able to send a message to the same employee at a later date. I have seen posts online saying that a "354 go ahead" means that the message was received, but that SMTP is waiting for more data or a terminating "." the problem with that is that the message was never received by the employee. If anyone can shed some light into this issue it would be appreciated. Thanks.
From: Mail Delivery Subsystem <MAILER-DAEMON@mx202.mails
Date: Tue, Mar 2, 2010 at 6:45 AM
Subject: Returned mail: see transcript for details
To: Client@ClientDomain.com
The original message was received at Mon, 1 Mar 2010 17:33:18 +0300
from mail-iw0-f187.google.com [209.85.223.187]
----- The following addresses had permanent fatal errors -----
<EmployeeA@Company.com>
(reason: 354 go ahead)
<EmployeeB@Company.com>
(reason: 354 go ahead)
----- Transcript of session follows -----
554 5.5.0 Remote protocol error
Final-Recipient: RFC822; EmployeeA@Company.com
Action: failed
Status: 5.5.1
Remote-MTA: DNS; server.company.com
Diagnostic-Code: SMTP; 354 go ahead
Last-Attempt-Date: Tue, 2 Mar 2010 02:45:11 +0300
Final-Recipient: RFC822; EmployeeB@Company.com
Action: failed
Status: 5.5.1
Remote-MTA: DNS; server.company.com
Diagnostic-Code: SMTP; 354 go ahead
Last-Attempt-Date: Tue, 2 Mar 2010 02:45:11 +0300
---------- Forwarded message ----------
Anyone know what could be causing this? The same client was able to send a message to the same employee at a later date. I have seen posts online saying that a "354 go ahead" means that the message was received, but that SMTP is waiting for more data or a terminating "." the problem with that is that the message was never received by the employee. If anyone can shed some light into this issue it would be appreciated. Thanks.
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
What version of exchange are you on?
Exchange 2007 version 08.02.0217.002
goto http://www.mxtoolbox.com/ and run all the DS and SMTP test they offer, report back on any tests that fail if you need further help.
Check this source of SMTP errors:
http://www.answersthatwork.com/Download_Area/ATW_Library/Networking/Network__3-SMTP_Server_Status_Codes_and_SMTP_Error_Codes.pdf
5.5.1 = User not local or invalid address – Relay denied.
SMTP Error 551 : If neither the sending mail address nor
the recipient’s address are locally hosted by the server,
then the ISP’s servers may refuse to relay the message
on.
You can verify relay / no relay settings o nthe SMPT properties page in your Exchange system manager - but changing the server is the least proper course, butter to get the user to use SMTP authentication than open up your server to spammers.
Check this source of SMTP errors:
http://www.answersthatwork.com/Download_Area/ATW_Library/Networking/Network__3-SMTP_Server_Status_Codes_and_SMTP_Error_Codes.pdf
5.5.1 = User not local or invalid address – Relay denied.
SMTP Error 551 : If neither the sending mail address nor
the recipient’s address are locally hosted by the server,
then the ISP’s servers may refuse to relay the message
on.
You can verify relay / no relay settings o nthe SMPT properties page in your Exchange system manager - but changing the server is the least proper course, butter to get the user to use SMTP authentication than open up your server to spammers.
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Thanks for the quick responses.
All the SMTP tests for our company's domain were successful. The only problem was the mailshelter.com SMTP test as rDNS failed. I'll check out the SMTP errors link you posted.
All the SMTP tests for our company's domain were successful. The only problem was the mailshelter.com SMTP test as rDNS failed. I'll check out the SMTP errors link you posted.
Do you use RBL? If so, check if this client is blacklisted (use the IP in the NDR)
http://www.anti-abuse.org/multi-rbl-check
http://www.anti-abuse.org/multi-rbl-check
Again this is being reported as a failed attempt to SMTP relay on a server that is (quite properly usually) configured to prevent same.
Should the client be using an email address served off the same server thats rejecting the answer is simple, configure the client to use SMTP authentication (likely most all your other users are already configured for this) and you are done.
========================
BUT SO NOT fail to fix your RDNS. Every day, more and more sites are validing using RDNS, and if you are failing, they are not accepting your email. Fix this one right away!!!!
Should the client be using an email address served off the same server thats rejecting the answer is simple, configure the client to use SMTP authentication (likely most all your other users are already configured for this) and you are done.
========================
BUT SO NOT fail to fix your RDNS. Every day, more and more sites are validing using RDNS, and if you are failing, they are not accepting your email. Fix this one right away!!!!
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
peakpeak: Thanks for the help, unfortunately nothing came back blacklisted.
dnilson: Thanks for all the help. rDNS is all setup for our domain, and we passed all tests according to the link you sent previously. The third party domain that failed (mailshelter.com) we have no control over. This is the only reported instance of returned mail, and the same client has been able to send emails to our domain since. If the server originating the message is from mailshelter.com then we can't enable SMTP relay on it anyway, although like you mention we probably wouldn't want to anyway.
dnilson: Thanks for all the help. rDNS is all setup for our domain, and we passed all tests according to the link you sent previously. The third party domain that failed (mailshelter.com) we have no control over. This is the only reported instance of returned mail, and the same client has been able to send emails to our domain since. If the server originating the message is from mailshelter.com then we can't enable SMTP relay on it anyway, although like you mention we probably wouldn't want to anyway.
I'm confused, who is recieeving the bounceback 5.5.1 error, someone in your domain (i thought) or someone at a third party domain(sounds like from last post).
Becuase it appears to have been generated by the SMTP (sending) server that the user who is SENDing the email is using to transmit the emai, it doesnt look like anything the RECIPient emails server said.
The client software, Outllok, Outlook Express, Thunderbird, etc is what has to be configured authenticate SMTP for the SENDing users mail client.
Becuase it appears to have been generated by the SMTP (sending) server that the user who is SENDing the email is using to transmit the emai, it doesnt look like anything the RECIPient emails server said.
The client software, Outllok, Outlook Express, Thunderbird, etc is what has to be configured authenticate SMTP for the SENDing users mail client.
The person receiving the bounceback error is one of our Clients, who sent the original email from a gmail address. Maybe gmail isn't setup for SMTP authentication?
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
ASKER CERTIFIED SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Sounds good man. Thanks for all the help. We were wondering what the deal was, especially since no one else was having any issues receiving mail. Thanks guys.
Exchange
--
Questions
--
Followers
Top Experts
Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.