Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

5.3.5 Looping Error with Exch2003/Exch2010

Status
Not open for further replies.

mlchris2

Technical User
Mar 18, 2005
512
US
Im doing some final testing of a transition from exch2003 to exch2010 When I reply back to email sent from a exch2010 mb, I receive a "5.3.5 NDR" error. I was trying to fix an error where I was unable to send email from a exch2010 mb, but fixed that by deleting the SMTP connector on the exch2003 server and recreating it. exch201 is using the SMTP connector on exch2003 server. I am able to send/receive email internally, send mail external but not receive email externally.

It's my understanding this is a SMTP looping error. I cant figure out what the issue is.

Can someone provide some insight?


Mark C.
 
correction... I just re-tested delivery and I am able to send email from a exch2010 mb both internal/external, but not able to receive both internal and external.

I received this msg back on a internal reply;

_____

Your message did not reach some or all of the intended recipients.

Subject: RE: internal test
Sent: 10/25/2010 8:55 AM

The following recipient(s) cannot be reached:

exchtest on 10/25/2010 8:55 AM
A configuration error in the e-mail system caused the message to bounce between two servers or to be forwarded between two recipients. Contact your administrator.
<mail.domain.com #5.3.5>
_____

from gmail, I get;

_____

This is an automatically generated Delivery Status Notification.

Delivery to the following recipients failed.

exchtest@domain.com




Final-Recipient: rfc822;exchtest@domain.com
Action: failed
Status: 5.3.5
X-Display-Name: exchtest

____

Mark C.
 
You should have a routing group connector for 2010 and for 2003, which the correct source and target servers defined. That will handle email flowing between the two. A properly configured send connector will handle sending mail OUT, and a properly configured receive connector will handle receiving mail IN.

Code:
[url=http://technet.microsoft.com/en-us/library/aa996924.aspx]Get-RoutingGroupConnector[/url] | fl
will show the RGCs

Code:
[url=http://technet.microsoft.com/en-us/library/aa998618.aspx]Get-ReceiveConnector[/url] | fl
will show all receive connectors. There are two by default, and any extras you created, like to receive from the Internet.

Code:
[url=http://technet.microsoft.com/en-us/library/bb124553.aspx]Get-SendConnector[/url] | fl
will show send connectors if they exist, including those defined to send to the Internet.

You should not have send connectors on one side configured to send to the other.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
 
I do have a routing group connector from 2010 to 2003, which was created during the 2010 GUI install. I believe my routing group connector is configured correctly. As I was previously able to send mail between both servers.

Previous to me deleting and re-creating the SMTP connector on 2003, I was able to send/recieve internal email as well as recieve external email on a 2010 mailbox. I lacked the ability to send email from a 2010 mailbox.

I do have 2 receive connectors, Client and Default. You mentioned... "any extras you created, like to receive from the Internet.".Do I need to create a receive connector???for both Internal and External or are the Client/Default connectors there sufficient? Im going to test by creating a internal and external receive connector

The only send connector I have is the one is see's from the exch2003 server.

I have ran the MailFlow troubleshooter and the results were;

"Mail Submission failed: Error Message: The SMTP host was not specified."


I thought about just doing this:




Mark C.
 
You have to create a receive connector to receive from the Internet, and a send connector to send to the Internet. Do not try to change default connectors.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
 
I figured it out, I had to remove the "all unassigned" from each virtual smtp server in all routing groups and point it to the corresponding private IP of each server. tested and mail is flowing great now.

I can under stand once I fully move to exchange 2010 and put it public facing, I will have to create a send and receive connector, but it appears the default connectors are sufficient. Im not at that point yet... hopefully in week.

Mark C.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top