NDRs When replying to X400 addresses with DDA extensions
-
Tuesday, February 19, 2013 3:16 PM
I am currently preparing for a migration from Exchange 2003 to Exchange 2010. The Exchange 2003 environment participates as part of a wider X400 messaging environment. The Exchange 2003 server has a X400 connector to the X400 community network via a 3rd party MTA. I have deployed a single Exchange 2010 server in the Exchange org and have migrated a few test mailboxes to Exchange 2010. Intra org mailflow works as expected, as does external mailflow to most X400 addresses, however 2010 mailboxes are getting NDR's when trying to reply to external users who have X400 addresses with embeded IMF addresses, as shown below:
c= XX; a = ;p=unit+org;o=org;s-surname;g=forename;i=XX;ou1=exchange;DDA:rfc-822=name(a)org;DDA:acp-plad=org
We can send OK to these addresses when we pick from the GAL or a local contact list but we cannot reply to the address. It gets rejected by the next hop Exchange server as an invalid address. If I compare the replys in message tracker (which fail) with newly generated messages (which work) , I can see one difference in the address string. Working emails seem to correctly interpret the (a) in the DDA:rfc-822 portion of the X400 address as an @ which is UTF encoded as +40, however the failing replys are showing up in message tracker as +28a+29a which is the UTF code for (a).
If we have any X400 gurus left out there in the wild, with long memories I'd appreciate any pointers you can offer. The client environment is Outlook 2003.
Regards
Dave
All Replies
-
Wednesday, February 20, 2013 6:28 AMModerator
Hi Dave，
c= XX; a = ;p=unit+org;o=org;s-surname;g=forename;i=XX;ou1=exchange;DDA:rfc-822=name(a)org;DDA:acp-plad=org
Are they all the NDR information ?
If no, please post the complete NDR information .
Wendy Liu
TechNet Community Support
-
Wednesday, February 20, 2013 3:34 PM
Hi Wendy, NDR pasted below: Note this has been heavily sanitised as security within the customer environment is critical. Setup is
Outlook2003 ---> [Routing Group2{E2K10sERV1}]-----> [Routing Group1{E2K3SERV2}]--> [Routing Group1{E2K3SERV3}]---->X400 MTA. As you can see replies are getting rejected by first E2K3 server in path.
-------------------------------------------------------------------------------------------------------
Delivery has failed to these recipients or groups
IMCEAX400-C=XX+3BA=+20+3BP=org+2Bsuborg+3BO=suborg+3BS=Surname+3BG=Forename+3BI=XX+3BOU1=exchange+3BDDA+3Arfc-822=xxsurname+28a+29suborg+3BDDA+3Aacp-plad=suborg+3B@local.dns
<mailto:IMCEAX400-C%3DXX%2B3BA%3D%2B20%2B3BP%3Dorg%2B2Bsuborg%2B3BO%3Dsuborg%2B3BS%3Surname%2B3BG%3DForename%2B3BI%3Dxx%2B3BOU1%3Dexchange%2B3BDDA%2B3Arfc-822%3DXXSurname%2B28a%2B29suborg%2B3BDDA%2B3Aacp-plad%3Dsuborg%2B3B@local.dns>
The format of the email is address isn't correct. A correct address looks like this: someone@example.com. Please check the recipients e-mail address and try to resend the message.Diagnostic information for administrators:
Generating Server: E2K3Serv02.local.dns
Original message headers:
Received: from E2K10Serv01.local.dns ([192.168.0.38]) by
E2KServ02.local.dns with Microsoft SMTPSVC(6.0.3790.1830); Tue, 12 Feb 2013 17:46:36 +0000
Received: from E2k10Serv01.local.dns ([fe80::99e9:fc34:5b99:lee2]) by
E2k10Serv01.local.dns ([fe80::99e9:fc34:5b99:lee2%15]) with mapi id
14.02.0247.003; Tue, 12 Feb 2013 17:46:36 +000
Content-Type: multipart/mixed;
boundary="_000_8cb63DD10DB19A47B5BDF01E76BA4E9BD80DE2K10SERV01localdns_"
From: <Bloggs@local.dns>
To:
<IMCEAX400-C=XX+3BA=+20+3BP=org+2Bsuborg+3BO=suborg+3BS=Surname+3BG=Forename+3BI=XX+3BOU1=exchange+3BDDA+3Arfc-822=xxsurname+28a+29suborg+3BDDA+3Aacp-plad=suborg+3B@local.dns>
cc: < user2@local.dns>
Subject: RE: Test
Thread-Topic: Test
Thread-Index: AQHOCUjmlaQt/1qQTEeUQTGLZiO3jw==
Disposition-Notification-To : <Bloggs@local.dns>
Date: Tue, 12 Feb 2013 17:46:35 +0000
Message-ID: <XXXXXXXXXXXXXXXXXXXXX@E2K10Serv01.local.dns>
IN-Reply-To:<E2K3serv02xxxxxxxxxxx@E2K3SERV02.local.dns>
Accept-Language: en-GB, en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
<XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX@E2K10SERV01.local.dns>
x-originating-ip: [192.168.1.232]
MIME-Version: 1.0
Return-Path: bloggs@local.dns
X-OriginalArrivalTime: 12 Feb 2013 17:46:36.0682 (UTC)
FILETIME=[XXXXXXXXXXXXXX] -
Wednesday, February 27, 2013 10:11 AMModerator
Hi ,
To achieve connect an Exchange 2010 environment to an e-mail system that uses X.400.
You need to do the following steps.
1.Configure one or more X.400 Authoritative Domain namespaces by using the New-X400AuthoritativeDomain cmdlet;
2.Create a Foreign Connector to send e-mails to a local messaging server
that does not use SMTP.
The detail information for your reference.
X.400 Addresses and Exchange 2010:
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Wendy Liu
TechNet Community Support -
Wednesday, February 27, 2013 12:07 PM
Hi Wendy
I have installed Exchange 2010 into an existing Exchange 2003 organisation which is already authoritative for an X400 namespace and already has X400 connectors defined. We have no problem sending and recieving email between Exchange 2010 and standard X400 addressees. We can even send OK to the problem recipients when we can pick the address from the address list. The problem is specifically when replying to emails sent from external X400 addresses which contain DDA:RFC-822=name@domain fields. When incoming emails are packaged in IMCEA for onward delivery within the Exchange org, ( External sender > X400 GW > E2K3 Bridgehead > E2K10 ) the sender address seems to be getting misformated by the Exchange 2003 bridgehead in the path. After some messing around trying to reformat the sender address so I can reply to one of these emails, I found that I need to make the following changes to the address in order that it will send correctly:
Replace (a) & modify case in DDA component so it is changed as follows:
DDA:rfc-822=name(a)domain.local ----------> DDA:RFC-822=name@domain.local
and reorder the DDA fields so that the RFC-822 field is that last component of the X400 address.
In message tracking, it looks like the reply-to address is getting messed up during encapsulation for onward delivery within IMCEA, only X400 addresses with DDA extensions are affected.
Thanks for responding
David
.png)
