|
Thanks for the response Al, I will have to sit down and
mull it over. :o)
I am learning far more about Exchange than I ever intended
to. I am not exactly thrilled except my going rate keeps going up for any other
company that wants to hire me. ;o)
joe From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mulnick, Al Sent: Thursday, February 24, 2005 1:49 PM To: [email protected] Subject: RE: [ActiveDir] OT:(again)exchange address I suspect there's a lot more to it. Outlook is one
thing (another group in Microsoft) and Exchange routing is another.
Exchange routing doesn't need to use LEDN because it won't be submitted to the
routing subsystem that way. The client handles some of the resolution for
you when internally located and the locally stored contacts would be one
example. It *could* be an SMTP based contact vs. LEDN, but if you pulled it from
the GAL Outlook inserts the LEDN.
LEDN is also backwards compatible and is X.500-like meaning
that it works out well for migration scenarios if you input an X.500 addr as a
secondary proxy addr so you can reply to existing messages. Routing at the
server still needs to query the directory to resolve an address regardless of
the 'client' that submits it or the form it takes when submitted to the
store. Some routes go through the store and now in Exchange 200x many more
do not by default [1].
In SMTP, anything outside the local store is considered a
'client' in the client-server sense, including a foreign MTA.
Outlook can take shortcuts in some situations and in others
has to play by the rules imposed by legacy Exchange systems in a given
mode.
If you really really really don't have anything better to
do ;) you may want to jack up the logging on the routing subsystem (categorizer
etc) to see what it gets from the 'client' and what it puts out for
routing. Been too long since I last did that, but that would help you to
see the iterations that an address has to go through (lovingly referred to as
munging in my mind).
Al
[1] hence the change from X.400 like MTA to SMTP MTA and a
lot of performance boost; now that the store doesn't have to be involved, it's
much much faster at higher rates than it used to be.
It would be nice to hear from Microsoft dev exactly what
they expect to see in the form of address submission to the server. SMTP, LEDN,
X.500, ?? What exactly do they accept and why? I haven't seen the docs
saying exactly what they would accept, but suspect most of it is still governed
by the legacy i.e. Exchange 5.5 parameters for coexistence
sake.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of joe Sent: Thursday, February 24, 2005 12:58 PM To: [email protected] Subject: RE: [ActiveDir] OT:(again)exchange address I wonder about this though. In particular I wonder how much
Outlook impacts this. I know Outlook does a lot with legacyExchangeDN.
If you crank up logging on a DC, I know you will see
outlook try to resolve email addresses but it seems to only ask for
displayNames. However if you go a little further up the list of calls and the
address being sent to is represented in the local directory say as a contact,
you will see a legacyExchangeDN lookup from Exchange for that object, not an
smtp address lookup.
I would expect that if the address can be resolved by
Outlook, either to contact or mail/mailbox enabled user it submits the message
with a LEDN instead of with an email address. The fun part is I have never
caught a query from outlook that seems to return ledn to it. I see the NSPI
lookups that give the displayName, I would expect it returns the ledn at that
point as well.
So at this point, I think if the email comes in from
outlook in smtp format it probably already knows that it is a foreign
address.
joe
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, February 24, 2005 12:17 PM To: [email protected] Subject: RE: [ActiveDir] OT:(again)exchange address In addition to what Al said, DSaccess and DSProxy are
the 2 components responsible for locating, resolving and providing referrals for
internal users located AD. SMTP Categorizer uses DSAccess to resolve a mailbox
addy to a user (and for other things). Exchange knows to send an email to an
external server by looking at the domain name part of the email address and
determining whether it is responsible for THAT domain or not. If it is not
responsible for the domain, Exchange (nay, all SMTP servers) categorizes the
email as outbound. If it determines that it is responsible for the domain, it
then utilizes its components to resolve the mailbox and route the email for
delivery based on the resolution. It’s more involved than that, but you get the
gist. When you get to the Exchange Library site, be sure to
look for the “Exchange Technical Reference” doc. Deji -----Original Message----- Exchange doesn't care about internal/external in that
way. Exchange is SMTP based and follows the concept of authoritative for a
domain or not. That's configured via Recipient Policies GUI typically.
GUIDS to find users? I've never heard that and
can't comment past saying that a user-object has a guid and an SMTP address as
attributes. They are connected and could be used, but why? Homemdb (and
several other attributes that must exist in order to qualify for mail receipt)
would be more useful I would guess. As for addresses, Exchange has to do lookups for the
SMTP addresses and then deliver the message. Since it's SMTP based and
uses a centralized directory service, as mail comes in from external systems
(external to Exchange) it MUST lookup the address either in cache or in the
directory itself to be able to bring the transaction to resolution.
That's where the 1:4 MHZ server to GC recommendation comes from; you'll knock
over a GC in a high-volume environment if you're not
careful. As for docs that explain internal routing, you can find
those at http://www.microsoft.com/exchange/library and I would
suggest the troubleshooting routing
docs. Does that help? Al -----Original Message----- From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Kern, Tom Sent: Thursday, February 24, 2005 11:38
AM Subject: RE: [ActiveDir] OT:(again)exchange
address doesn't exchange use guids to find users? it can't
associate a guid with a smtp address? or rather, how exactly does exchange tell if an address
is in AD or out on the internet and how does it find the owner of said
address(if in AD) under the hood? are there any docs you could point me
to? thanks joe wrote: > Yep. I have seen it go a couple of ways at various
times. > > User1 gets the email but User2
doesn't. > User2 gets the email but User1
doesn't. > Sometimes one way, sometimes the
other. > Neither get it and an NDR is
sent. > > Basically only one person gets the message or no
one gets the message. > This is why I end up working on scripts to find
duplicates. > :o) > > > joe > > > -----Original
Message----- > From:
[EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On
Behalf Of Coleman, > Hunter Sent: Tuesday, February 01, 2005 11:27
AM > To:
[email protected] > Subject: RE: [ActiveDir] OT:(again)exchange
address > > Typically it will result in neither person getting
the email, and the > sender will get and NDR. Addresses (primary and any
secondaries) need > to be unique within the forest to prevent the
delivery failure. >
http://support.microsoft.com/default.aspx?scid=kb;en-us;258058 > > -----Original
Message----- > From:
[EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On
Behalf Of Kern, Tom > Sent: Tuesday, February 01, 2005 8:52
AM > To: ActiveDir (E-mail) > Subject: [ActiveDir] OT:(again)exchange
address > > Hi, if i have 2 users with the same name in 2
different domains in a > win2k forest and both users have the other users'
primary smtp address > as a secondary like so-
[EMAIL PROTECTED] > [EMAIL PROTECTED]
secondary > >
[EMAIL PROTECTED] >
[EMAIL PROTECTED] > > > will both users get each others mail? will exchange
try to deliever to > both mailboxes based on the smtp address? when
exchange gets a email > doesn't it just use that smtp address value to find
the attribute and > user associated with it and then deliever the mail?
or is a lot more > involved? > > thanks > List info :
http://www.activedir.org/List.aspx > List FAQ :
http://www.activedir.org/ListFAQ.aspx > List archive: >
http://www.mail-archive.com/activedir%40mail.activedir.org/ > List info :
http://www.activedir.org/List.aspx > List FAQ :
http://www.activedir.org/ListFAQ.aspx > List archive: >
http://www.mail-archive.com/activedir%40mail.activedir.org/ > > List info :
http://www.activedir.org/List.aspx > List FAQ :
http://www.activedir.org/ListFAQ.aspx > List archive: >
http://www.mail-archive.com/activedir%40mail.activedir.org/ List info :
http://www.activedir.org/List.aspx List FAQ :
http://www.activedir.org/ListFAQ.aspx List archive:
http://www.mail-archive.com/activedir%40mail.activedir.org/ List info :
http://www.activedir.org/List.aspx List FAQ :
http://www.activedir.org/ListFAQ.aspx List archive:
http://www.mail-archive.com/activedir%40mail.activedir.org/ |
