Sign up for Office 365
Learn more about Office 365
Running into a problem with a new setup on MS Exchange online.
Basically when a person hits REPLY, REPLY ALL or FORWARD if any of the email addresses in the To and/or cc fields go to another person internally the email gets bounced with the following error:
Delivery has failed to these recipients or groups:
'Karla Xxxxx' The e-mail address you entered couldn't be found. Please check the recipient's e-mail address and try to resend the message. If the problem continues, please contact your helpdesk.
'Angeli Nnnnnn' The e-mail address you entered couldn't be found. Please check the recipient's e-mail address and try to resend the message. If the problem continues, please contact your helpdesk.
Diagnostic information for administrators:
Generating server: ibscommodities.onmicrosoft.com
IMCEAEX-_O=CHOST_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=KARLA+2EXXXXX@namprd06.prod.outlook.com #550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##
IMCEAEX-_O=Chost_ou=Exchange+20Administrative+20Group+20+28FYDIBOHF23SPDLT+29_cn=Recipients_cn=annnnnn@namprd06.prod.outlook.com #550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##
Original message headers:
Received: from CH1PRD0610MB368.namprd06.prod.outlook.com ([169.254.7.50]) by CH1PRD0610HT002.namprd06.prod.outlook.com ([10.255.151.37]) with mapi id 14.16.0143.004; Mon, 30 Apr 2012 18:43:20 +0000 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: binary From: Karla Xxxxx <kxxxxx@ibscommodities.com> To: 'Karla Xxxxx' <IMCEAEX-_O=CHOST_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=KARLA+2EXXXXX@namprd06.prod.outlook.com>, Breeze of www.garlic86.com <Breeze@garlic86.com>, 'Angeli Nnnnnn' <annnnnn@ibscommodities.com> CC: xiangsheng <xiangsheng@peanutcn.com> Subject: RE: RE: copy documents of garlic 21202201 Thread-Topic: RE: copy documents of garlic 21202201 Thread-Index: Ac0knIG42g4SWQAqSBi/hbXEhgeAegCOJ+vQAAr1r3A= Date: Mon, 30 Apr 2012 18:43:20 +0000 Message-ID: <EA244E99539A4945A9DFD81652D4DDAB29FE5A@CH1PRD0610MB368.namprd06.prod.outlook.com> References: <54CDF23D117B3D4DA16151FCD0C35D2F6A3373457D@AUSP01VMBX06.collaborationhost.net>, <201203230924119378270@garlic86.com>, <4346E21832217949A011B6174C8903EB713AA32BD9@AUSP01VMBX06.collaborationhost.net>, <201203240031033434809@garlic86.com>, <4346E21832217949A011B6174C8903EB713D2E2FC4@AUSP01VMBX06.collaborationhost.net>, <201204091810297963914@garlic86.com>, <4346E21832217949A011B6174C8903EB72C71E15C3@AUSP01VMBX06.collaborationhost.net>, <201204240913180935591@peanutcn.com>, <201204250811252037381@garlic86.com>, <4346E21832217949A011B6174C8903EB72C762AFEA@AUSP01VMBX06.collaborationhost.net> <201204271737298752336@garlic86.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: <EA244E99539A4945A9DFD81652D4DDAB29FE5A@CH1PRD0610MB368.namprd06.prod.outlook.com> MIME-Version: 1.0 X-Originating-IP: [68.114.86.157]
Note that one of the persons that was rejected was sending the email to herself.
They are using Office 2010. The internal emails do not appear in the Suggested Contacts folder (and thus are not in history).
This is not really acceptable.
lalto
We are having the same problem. The users who are having trouble receiving email have an email address at the same domain, but with a different email provider. It's like Office is assuming that because they're using an @ourdomain.com email address their account must be within Office (which it isn't).
Is there a way to override this default functionality?
Hi Lalto & KateUnseen,
I would like to confirm are these emails migrated to Office 365 by importing PST files? If so, you will lose the ability to reply to old email and modify old calendar items. The reason this occurs is because the message is stored with x500 address from the old domain. To fix it, you need to add the old LegacyDN attribute to the online user's proxy addresses with Remote PowerShell. Please refer to the following article to do this:
http://help.outlook.com/en-us/140/cc967281.aspx
Thanks, Reken Liu
Hi Lalto,
I have just found this thread, which includes the detailed steps of adding LegacyDN to the proxy addresses. Please see http://community.office365.com/en-us/f/160/p/14802/68833.aspx#68833
No, they're new emails we're trying to send. It may be a different problem, so I will open up a new topic.
Hi KateUnseen,
Thanks for your update. Please feel free to open a new threads in the forum, and provide more detailed information about the issue in your side. By doing this, you should be able to get more dedicated assistance on the issue.
Is there any updates about the issue?
Hi Reken,
I just applied the settings for the proxy addresses. When the users come in tomorrow they will test it and I will let you know the results.
Thanks,
Hi lalto,
Thanks for the responding, and I look forward to your next update.
Best Regards, Reken Liu
Do you have any updates about the issue?
Hi Liu,
Sorry for the delay, but the problem is still occurring.
Larry
Hi Larry,
Have you test it in Outlook Web App(OWA), or your desktop Outlook? I suggest you test it again in OWA, because the cached information in desktop Outlook may have not been updated.
Meanwhile, please use the following cmdlet to verify if you have added the old LegacyDN address to the proxy address for the mailboxes correctly:
Get-Mailbox alias | FL EmailAddresses
How are things going? Have you test the issue in OWA?