> Following some exchange last week in this newsgroup, and as requested here
>is a description of my problem :
> SMTP connector (Internet) SMTP connector (Internet)
> X400 connector ------- InterSites ----- X400 connector
> I have created a custom recipient in Site A :
> x400 address for Exchange internal management
Let's get the terminology right so we can understand what you're
trying to say. The "reply address" is usually the "primary SMTP proxy
address" and it's usually found in the property "E-Mail Address" of
the Custom Recipient. It's this address that determines the
destination of messages sent to the Custom Recipient.
The address that you refer to as the "reply address" is usually a
secondary SMTP proxy address and appears in the "E-Mail Addresses"
property (note the plural).
Now, it doesn't HAVE to be that way, but that's the way it's set up by
default when you create the CR.
In the case you're discussing I'd expect to see the
would also be the primary SMTP proxy address in the "E-Mail Addresses"
property (the one with the upper-case SMTP prefix).
Quote:>When I'm connected on Site A, if I send a mail to my custom recipient, the
>mail goes directly thru my SMTP connector to the correct address.
Good. This is just the way it should work.
>mail comes in (I've got traces), then cross my X400 intersites connector to
>use the SMTP connector on the other site although that route has a weight of
>2 whereas the local SMTP as 1.
>Anybody else notice something like this ??, any idea ??
Well, one thing comes to mind -- and I'm not sure how applicable it is
to your situation. If the MTA is viewing this message as I think it
might be, then it will not send the message out of the site over the
same connector over which it entered the site. It does this in order
to avoid a message loop.
If you restrict the scope of the address space on the IMS's to "This
site" does the message leave by way of SiteA's IMS? It should!
The other possibility is that the MTA has a problem selecting the
local connector and is mistakenly selecting a more expensive route. I
remember reading a KB article on a problem like that but I can't seem
to locate it! If you suspect this then call MS PSS.
MCSE, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm