0

I had an email account: [email protected].

In exchange I had a distribution group [email protected]. This distribution group had a few users.

My DNS MX records pointed to my exchange 2010 server.

So sending an email to [email protected] was going to distribution group [email protected] and there it was distributed to a list of users and contacts.

Recently I moved my domainhosting from product.com where I had the possibility to use mailbox forwarders, hosted by them. I changed my DNS MX records to their server and everything was fine. emailing to [email protected] now directly goes to my list of users and not anymore via [email protected].

Email still works fine, I'm happy with the move as it simplifies things for me on my own exchange server.

I deleted user [email protected] from exchange and AD because this was only created to forward.

Now recently I only had webaccess via OWA and I sent an email to [email protected] Immediately I received an email from Exchange that the email could not be delivered.

IMCEAEX-_O=MYCOMPANY+20ORGANIZATION_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=producta81@mycompany.com

550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found

So the situation/problem: - Sending to [email protected] from external account works fine (even from my outlook at the company). - Sending to [email protected] from OWA gives 550 5.1.1 not found.

Why does it happen and how can I solve it?

Improve this question

1 Answer 1

Reset to default
1

We see this issue sometimes in outlook when mailboxes have been migrated. You may try to remove the suggestion when typing the recipient adress and ensure to type the address once completely. seems that there is additional information about the ad object behind the suggested recipient.

Improve this answer
5
  • This seems to work indeed, any idea how I can make it work when the email address is suggested? More details?
    – juFo
    Feb 19, 2016 at 13:58
  • i don't know if there's an automatism for this issue. we just know the manual fix by removing the entry once by hand.
    – Daniel Nachtrub
    Feb 19, 2016 at 14:59
  • 1
    Internal suggestions don't use the SMTP address, they are using an X.500 address. Therefore adding an X.500 address to the new object will allow auto completes from the old object to be delivered correctly.
    – Sembee
    Feb 20, 2016 at 14:43
  • @Sembee interesting, but 'adding to the new object', how do I do this? (also: no idea yet how that X.500 address works or how to add/configure it :-) )
    – juFo
    Feb 22, 2016 at 9:39
  • This is written for SBS, but applies to any Exchange servers. blogs.technet.microsoft.com/sbs/2009/05/21/…
    – Sembee
    Feb 22, 2016 at 13:00

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .