We have migrated one of our clients off Microsoft BPOS and to their own SBS 2008 server. During the migration we exported each users Outlook 2010 data to PST files and have imported it into a new profile connected to the SBS 2008 machine. The problem is that when a user tried to reply to an email that was in their inbox prior to the migration they get an NDR because the autocomplete is trying to deliver the message to the microsoft online servers. I have tried clearing the NK2 but the users still get an NDR when trying reply to internal emails. I know there's a way to create an X500 address to trick the SBS server but I'm unclear what the proper formating would be. Can someone please help me configure the X500 address to trick exchange. ... a reply to John Doe came back as: Diagnostic information for administrators: Generating server: FTG01.ftg.local IMCEAEX-_O=MICROSOFTONLINE_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=4DDDBE93-00C3-4A5B-8A7A-627CD933221B@ftg.local #550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ## Original message headers: Received: from FTG01.ftg.local ([fe80::29aa:5ca9:6bc8:d48f]) by FTG01.ftg.local ([fe80::29aa:5ca9:6bc8:d48f%10]) with mapi; Wed, 26 Jan 2011 15:07:09 -0800 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: binary From: Michael Smith <msmith@internetdomain.com> To: 'Ardalan Ebnoddin-Hamidi' <IMCEAEX-_O=MICROSOFTONLINE_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=4DDDBE93-00C3-4A5B-8A7A-627CD933221B@ftg.local> Date: Wed, 26 Jan 2011 15:07:08 -0800 Subject: test Thread-Topic: test Thread-Index: Acu9rcAecd7TqHvAR/uBRV4PukubYQ== Message-ID: <793AC39995767D4AB5C5A03656F54B2C0784F111CB@FTG01.ftg.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: <793AC39995767D4AB5C5A03656F54B2C0784F111CB@FTG01.ftg.local> MIME-Version: 1.0

That is normal. You can add the address: /O=MICROSOFTONLINE/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=4DDDBE93-00C3-4A5B-8A7A-627CD933221B@ftg.local as a new "Other" address of type X509 to the user to whom it applies, i.e., the person to whom the reply is supposed to be sent. That will make Exchange recognize that internal Microsoft Online address as one of its own.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

On Wed, 26 Jan 2011 23:42:34 +0000, Ed Crowley [MVP] wrote: > > >That is normal. You can add the address: > >/O=MICROSOFTONLINE/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=4DDDBE93-00C3-4A5B-8A7A-627CD933221B@ftg.local > >as a new "Other" address of type X509 to the user to whom it applies, i.e., the person to whom the reply is supposed to be sent. That will make Exchange recognize that internal Microsoft Online address as one of its own. That should be "X500", not X509. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

I don't know where that 9 came from. Thanks, Rich.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

On Thu, 27 Jan 2011 03:52:25 +0000, Ed Crowley [MVP] wrote: >I don't know where that 9 came from. Thanks, Rich. It's right there, next to the zero on the keyboard. :-) If the topic was SSL certs you've have been right on! --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Thanks Guys! I was thinking that I would be able to do that but I wasn't too sure on the @ftg.local because that's my new local domain I figured I would need to make it something like @RED001 etc. Jason

Thank goodness it wasn't.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

This is still a problem. Has anyone actually tried this when moving off BPOS?

It isn't a BPOS error as much as an issue going between Exchange platforms. This blog posting from the SBS team explains what is happening. http://blogs.technet.com/b/sbs/archive/2009/05/21/cannot-reply-to-old-emails-or-modify-old-calendar-items-after-pst-mail-migration.aspx Simon.Simon Butler, Exchange MVP Blog | Exchange Resources

You may want to consider using MigrationWiz to perform your migration. We automatically translate legacy DNs (the stuff like /O=company/.../CN=user) into SMTP addresses during the migration process. As a result, migrated emails are repliable without having to import legacy DNs, modify proxy addresses, etc.

Funny you should mention that. I just came across MigrationWiz the other day. I will be looking into it. My only complaint is that it seems a little expensive for large companies. It would be cool if we could purchase your migration software and then run it on the AmazonCloud to leverage to power to actually do the migration. Do you guys offer any trials?