Your message did not reach some or all of the intended recipients. Subject: Test Email Sent: 12/16/2010 8:44 AM The following recipient(s) cannot be reached: (Exchange Recipient Address) on 12/16/2010 11:11 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. < (Exchange Server Name) #5.4.6 SMTP; 554 5.4.6 Too many hops> Can someone help me to resolve this issue because usually we get this error only for couple users in exchange. Thanks in Advance

What does message tracking show for that message?

Can you explain your exch architecture? Are you coexisting multiple versions, how many servers, how many sites? What does your connectors look like?Tim Harrington - Catapult Systems - http://HowDoUC.blogspot.com

On Sat, 18 Dec 2010 12:59:43 +0000, Snawadkar wrote: >Your message did not reach some or all of the intended recipients. > > > > Subject: Test Email > > Sent: 12/16/2010 8:44 AM > > > >The following recipient(s) cannot be reached: > > > > (Exchange Recipient Address) on 12/16/2010 11:11 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. > > < (Exchange Server Name) #5.4.6 SMTP; 554 5.4.6 Too many hops> > > > >Can someone help me to resolve this issue because usually we get this error only for couple users in exchange. What release of Exchange??? I've run into this problem a couple of times with messages that aren't looping. Once was with Ford Motor Company. They had so many internal servers handling their messages that by the time it got to us and went through another set of server that the hop count exceeded 30! You can raise that "hop count" limit on all versions of Exchange, but it's done differently in 2003 than 2007, e.g. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Please let us know your mail routing both inbound & outbound.... Check to see if you've gateway configured correctly to forward emails to right hosts etc.... Also see if smarthost on connectors is there & configured correctly.... Regards, Pushkal MishrA

Please let us know your mail routing both inbound & outbound.... Check to see if you've gateway configured correctly to forward emails to right hosts etc.... Also see if smarthost on connectors is there & configured correctly.... Regards, Pushkal MishrA

On Sat, 18 Dec 2010 12:59:43 +0000, Snawadkar wrote: >Your message did not reach some or all of the intended recipients. > > > > Subject: Test Email > > Sent: 12/16/2010 8:44 AM > > > >The following recipient(s) cannot be reached: > > > > (Exchange Recipient Address) on 12/16/2010 11:11 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. > > < (Exchange Server Name) #5.4.6 SMTP; 554 5.4.6 Too many hops> > > > >Can someone help me to resolve this issue because usually we get this error only for couple users in exchange. What release of Exchange??? I've run into this problem a couple of times with messages that aren't looping. Once was with Ford Motor Company. They had so many internal servers handling their messages that by the time it got to us and went through another set of server that the hop count exceeded 30! You can raise that "hop count" limit on all versions of Exchange, but it's done differently in 2003 than 2007, e.g. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP Im always amazed how many hops a message can take within a hosted provider who handles the inbound/outbound piece!

Please let us know your mail routing both inbound & outbound.... Check to see if you've gateway configured correctly to forward emails to right hosts etc.... Also see if smarthost on connectors is there & configured correctly.... Regards, Pushkal MishrA

Hi, Are the problematic users internal recipients? What's versio of Exchange server? Is the NDR generated server remote server or self Exchange server? If it's internal recipeints, you can use Message Tracking Log to find the possible cause. It it's Internet recipients and the remote server generates the NDR, that should be the destination server issue. Thanks AllenAllen Song