Office 365 to Exchange 2003 (staged migration) NDR 5.2.1 error sending mail

Hi All,

We are performing a staged migration from Exchange 2003 to Office365 and are experiencing the following error when users in the office365 environment send mail to users in the on premise exchange.

Remote Server returned '< #5.2.1>'
Original message headers:
Received: from xxxx.xxxx.messagelabs.com ([xxx.xxx.xxx.xxx]) by <FQDN  on premise exchange> with Microsoft SMTPSVC(6.0.3790.4675);

Any ideas?

Thanks
lutherpendragonAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Vasil Michev (MVP)Commented:
What's the generating server? And why is messagelabs involved?

In Exchange 2013, DSN 5.2.1 indicates issues with the recipient mailbox:

5.2.1      
Mailbox cannot be accessed       
The mailbox cannot be accessed. The mailbox may be offline, disabled, or the message has been quarantined by a rule.      
Check to see if the recipient database is online, the recipient mailbox is disabled, or the message has been quarantined.

In other mail systems the cause might be different.
0
Mai Ali (MVP)Senior Infrastructure ConsultantCommented:
It's not compatible, you need to have exchange server 2010 sp3 to can migrate to office 365
0
lutherpendragonAuthor Commented:
I've found the solution. That NDR can also be linked to one or more errors with ID 9667 generated in the Application event log on the Exchange server.

The underlying error ( ID 9667 ) mentions that the limit of Named Properties has been reached for the database.

The WORKAROUND (not log term fix) is documented here for exchange 2003:
http://msexchangeguru.com/2009/09/04/event-id-9667/

Involves editing the non MAPI registry entry, As stated this is a workaround and not a long term solution.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
lutherpendragonAuthor Commented:
No other solutions were accurate. I fixed the problem myself
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Office 365

From novice to tech pro — start learning today.