brightergreen
asked on
Cached internal addresses not delivering after exchange migration
When migrating clients to new exchange servers (with a new internal domain) we often have the problem that users get NDRs when responding or sending new (via NK2 / Outlook 2010 cache) messages to users. Here is an example of the bounceback (personal data changed).
IMCEAEX-_O=THE+RED+20ORGAN
#550 5.1.1 RESOLVER.ADR.ExRecipNotFou
To fix this, we've gone in and deleted individual entries from PSTs or entire PSTs, but at this point we're working with an organization that frequently needs to respond to old emails. I feel there must be a fix for this we can perform on the server for the whole organization.
Clients range from outlook 2003 - 2010
Server was exchange 2003 and now is SBS 2011
Here is the header from that mail:
Received: from TRSBS1.tr.local ([fe80::34fb:c8ef:91c3:a07
TRSBS1.tr.local ([fe80::34ab:c2ef:94c3:g07
14.01.0218.012; Fri, 29 Jul 2011 20:48:11 -0700
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding:
From: jon <jon@thered.com>
To: "'bob@Thered.com'"
<IMCEAEX-_O=THE+20RED+20OR
Subject: FW: red
Thread-Topic: red
Thread-Index: AcxOSo9kxFPrLujoTo+/YMgMbj
Date: Fri, 29 Jul 2011 20:48:10 -0700
Message-ID: <472B6462B6A36746BDBBFA1DB
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator: <472B6462B6A36746BDBBFA1DB
MIME-Version: 1.0
X-Originating-IP: [10.10.4.136]
IMCEAEX-_O=THE+RED+20ORGAN
#550 5.1.1 RESOLVER.ADR.ExRecipNotFou
To fix this, we've gone in and deleted individual entries from PSTs or entire PSTs, but at this point we're working with an organization that frequently needs to respond to old emails. I feel there must be a fix for this we can perform on the server for the whole organization.
Clients range from outlook 2003 - 2010
Server was exchange 2003 and now is SBS 2011
Here is the header from that mail:
Received: from TRSBS1.tr.local ([fe80::34fb:c8ef:91c3:a07
TRSBS1.tr.local ([fe80::34ab:c2ef:94c3:g07
14.01.0218.012; Fri, 29 Jul 2011 20:48:11 -0700
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding:
From: jon <jon@thered.com>
To: "'bob@Thered.com'"
<IMCEAEX-_O=THE+20RED+20OR
Subject: FW: red
Thread-Topic: red
Thread-Index: AcxOSo9kxFPrLujoTo+/YMgMbj
Date: Fri, 29 Jul 2011 20:48:10 -0700
Message-ID: <472B6462B6A36746BDBBFA1DB
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator: <472B6462B6A36746BDBBFA1DB
MIME-Version: 1.0
X-Originating-IP: [10.10.4.136]
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Got it.
The X500 has to be the old LegacyExchangeDN in this format (my final syntax as missing a front slash):
/o=The Red Organization/ou=First Administrative Group/cn=Recipients/cn=bob
which appears to correspond with the mailbox name, not an SMTP address.
The X500 has to be the old LegacyExchangeDN in this format (my final syntax as missing a front slash):
/o=The Red Organization/ou=First Administrative Group/cn=Recipients/cn=bob
which appears to correspond with the mailbox name, not an SMTP address.
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for brightergreen's comment http:/Q_27249508.html#36410226
for the following reason:
Ended up being a syntax error that I was able to resolve myself.
Accepted answer: 0 points for brightergreen's comment http:/Q_27249508.html#36410226
for the following reason:
Ended up being a syntax error that I was able to resolve myself.
So I didn't help you at all with the solution by advising you about the x500 address?
ASKER
However, the theory seems sound - we got the x500 addresses in there but they are still not working. I've tried many versions of the syntax for the x500 address including:
_O=THE+20RED+20ORGANIZATIO
O=THE+20RED+20ORGANIZATION
“_O=THE RED ORGANIZATION_OU=FIRST ADMINISTRATIVE GROUP_CN=RECIPIENTS_CN=bob
“O=THE RED ORGANIZATION_OU=FIRST ADMINISTRATIVE GROUP_CN=RECIPIENTS_CN=bob
/O=THE+20RED+20ORGANIZATIO
O=THE+20RED+20ORGANIZATION
I fired up the old exchange server and had a look at the LegacyExchangeDN attribute and this is what it was for that user, which differs from the original bounceback (and also did not work):
o=The Red Organization/ou=First Administrative Group/cn=Recipients/cn=bob
What is the correct syntax for the x500 address? Is there another component I'm missing?