Check for duplicate smtp addresses. I have seen this in our mixed environment. I have to occassionally search for duplicates and modify the offending mailbox/pf. Also check that you have the correct email address for the pf. I have caught more than one typo causing this error.
Nate > ---------- > From: Fyodorov, Andrey > Reply To: [EMAIL PROTECTED] > Sent: Thursday, June 19, 2003 8:47 AM > To: [EMAIL PROTECTED] > Subject: routing issue in a mixed environment > > Hi all. Just an interesting observation I'd like to share (I have already > found a way to fix the problem) > > We have a mixed 5.5/2000 environment and are in the process of migrating. > > All the public folders have been migrated and now reside on a 2000 public > folder server > > Some users are still on 5.5 > > The IMC connectors are still on 5.5 servers (I didn't do it :) it was like > this before I started here and there is a change management process to put > a > 2000 SMTP connector in place soon). The 5.5 IMC connectors are in a > separate > 5.5 site from the site that contains the mix of 5.5 and 2000 servers, and > there is a site connector between sites. > > There is a public folder that is set up to forward a copy of all mail to a > custom recipient (set up in the Exchange General/Delivery properties of > the > PF, NOT a rule) > > Here is what I was observing: > > When a 5.5 user sends mail to this public folder he gets back an NDR. It > looks like the NDR comes from one of the 2000 servers. Sometimes the NDR > says "5.7.1 Unable to relay to [external SMTP address]", sometimes it just > says "Unable to deliver the message due to a recipient problem". > > Since the public folder only has a replica on a 2000 server, the message > is > first routed from the user's 5.5 home server to the 5.5 bridgehead server, > then via the site connector to the mixed site where it eventually enters > the > 2000 world. There it gets split and a 2000 server tries to forward a copy > to > the external SMTP address. In order to do that, Exchange 2000 needs to > submit the message to the MTA and shove it back to the Exchange 5.5 world > (because the IMCs are only on Exchange 5.5). > That's where Exchange 2000 freaks out and sometimes thinks that this is a > relay situation or "recipient problem". > > P.S. the fix was to make a replica of that public folder on one of the > Exchange 5.5 servers. > > > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Web Interface: > http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&la > ng=english > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > > _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
