[Exchange] Recipient not found error from local exchange - mailbox exists

[RabbieBurns]

We are having a problem whereby emails are bouncing back from a user who has a mailbox on our exchange server, even when I try to send locally.

 

This is the message that bounces back, however the user does have a mailbox on the exchange server, so I dont understand why this is showing a recipient not found:

 

IMCEAEX-_O=REDLANDS_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=Dgreg@domain.in.au
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

Original message headers:

Received: from MAILSERVER3.admin.domain.in.au
([fe80::e453:6189:550b:a869]) by MAILSERVER3.admin.domain.in.au
([fe80::e453:6189:550b:a869%24]) with mapi id 14.02.0283.003; Wed, 1 Aug 2012
18:10:04 +1000
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: Computing Services Helpdesk 
To: David Gregory 
Subject: RE: Yr 9 Assessment Notification - to be handed out this week
Thread-Topic: Yr 9 Assessment Notification - to be handed out this week
Thread-Index: AQHNb5tMpW9yyRUH10yv8iIgbDvebpdEmspQ
Disposition-Notification-To: IT Helpdesk

Return-Receipt-To: 
Date: Wed, 1 Aug 2012 18:10:03 +1000
Message-ID: 
References: 

In-Reply-To: 
Accept-Language: en-GB, en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
MIME-Version: 1.0
X-Originating-IP: [60.242.157.23]

 

I dont understand... what could I check?

[sukh]

Can you test via OWA for this user.

[qcomer]

We are having a problem whereby emails are bouncing back from a user who has a mailbox on our exchange server, even when I try to send locally.

 

This is the message that bounces back, however the user does have a mailbox on the exchange server, so I dont understand why this is showing a recipient not found:

 

IMCEAEX-_O=REDLANDS_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=Dgreg@domain.in.au
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

Original message headers:

Received: from MAILSERVER3.admin.domain.in.au
([fe80::e453:6189:550b:a869]) by MAILSERVER3.admin.domain.in.au
([fe80::e453:6189:550b:a869%24]) with mapi id 14.02.0283.003; Wed, 1 Aug 2012
18:10:04 +1000
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: Computing Services Helpdesk 
To: David Gregory 
Subject: RE: Yr 9 Assessment Notification - to be handed out this week
Thread-Topic: Yr 9 Assessment Notification - to be handed out this week
Thread-Index: AQHNb5tMpW9yyRUH10yv8iIgbDvebpdEmspQ
Disposition-Notification-To: IT Helpdesk

Return-Receipt-To: 
Date: Wed, 1 Aug 2012 18:10:03 +1000
Message-ID: 
References: 

In-Reply-To: 
Accept-Language: en-GB, en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
MIME-Version: 1.0
X-Originating-IP: [60.242.157.23]

 

I dont understand... what could I check?

 

Does this happen only for one user when sending to this person using an outlook auto remember? If so, have them delete the cached address and try again.

 

Or, did you recently do an email server migration? If so, Outlook uses x500 addresses when resolving an internal SMTP address rather than using the [email protected]. You can fix this very easily (I have done it after several migrations). Here is my tutorial on it: quinncomer.com » Outlook issue after SBS 2003 to Exchange 2010 Migration

[RabbieBurns]

Does this happen only for one user when sending to this person using an outlook auto remember? If so, have them delete the cached address and try again.

 

Or, did you recently do an email server migration? If so, Outlook uses x500 addresses when resolving an internal SMTP address rather than using the [email protected]. You can fix this very easily (I have done it after several migrations). Here is my tutorial on it: quinncomer.com » Outlook issue after SBS 2003 to Exchange 2010 Migration

 

It happens when everyone sends to them, but yes, we have very recently migrated to 2010, so I will check your blog.. thanks!

[qcomer]

It is from a bad cached x500 address for internal mailing of outlook when using outlook.

 

You can either deleted the cached email in their auto complete by highlighting the address and pressing delete or follow my guide to add the x500 address for all users as an alternative smtp address. Takes about 10 mins.

[RabbieBurns]

It is from a bad cached x500 address for internal mailing of outlook when using outlook.

 

You can either deleted the cached email in their auto complete by highlighting the address and pressing delete or follow my guide to add the x500 address for all users as an alternative smtp address. Takes about 10 mins.

 

It cant be a bad cached from outlook, as when I sent him an email to test, i had never previously contacted this user and there was no cache in my outlook of this user.

 

This is only happening to 1 user which is strange, but I will look at adding the x500 attribute for him. Thanks.

[sukh]

Did you compose a new message or reply to an old message from this useR?

[RabbieBurns]

Did you compose a new message or reply to an old message from this useR?

 

I composed a new email.

 

I have been unable to check whether the user can access their webmail or not at this time.

[sukh]

Then it's unlikey the x500 is the issue.

 

Can you repro the issue?

[RabbieBurns]

Every time i send an email to this user. It bounces back same error...

[sukh]

Even if you use OWA?

Is this the same for all users who send to this recipient?

[RabbieBurns]

It has been reported form multiple users.

 

I just sent from OWA, sending to just

 

This seemed to go through OK (i should have ticked delivery reciept, forgot)

 

I then sent another one, again just entering however this time OWA autofilled that to Full Name. This one, and subsequent ones have failed and bounced back.

[sukh]

Can you check and see what SMTP addresses are associated with this user?

Is [email protected] listed as one?

[RabbieBurns]

he only has one smtp address listed, and that is the correct one. Automatically update email address based on policy is also checked..

[sukh]

[email protected]

[email protected]

Both of these or just the one? If one is missing, as a test can you add the missing and test again.

[RabbieBurns]

sorry it is only dgregory i tried to truncate it when i posted so as not to post the full alias on here.

[sukh]

Can you actually go to the Domain partition in Adsiedit and check the proxyaddresses and mail attribute?

[RabbieBurns]

mail and proxy address in adsi edit are correct.

[sukh]

Can you run Get-Mailbox "Alias" | fl *add*

[RabbieBurns]

AddressBookPolicy             :
ForwardingAddress             :
ForwardingSmtpAddress         :
OfflineAddressBook            :
AddressListMembership         : {\All Users, \All Rooms, \Default Global Address List}
EmailAddresses                : {SMTP:[email protected]}
HiddenFromAddressListsEnabled : False
EmailAddressPolicyEnabled     : True
PrimarySmtpAddress            : [email protected]
WindowsEmailAddress           : [email protected]

[sukh]

Ok, send a test message via OWA and then check MT logs and report back on what they say.

If the above fails then move the mbx for this user to another DB and test again.

Can you check the user in the GAL and see if you see the addresses.

 

DONT forget to delete the cache when performing test.

[RabbieBurns]

are exchange transport logs on by default? Im a bit lost looking for them in this new R2/2010 installation..

[sukh]

By default they are logged, go to the properties under Server Configuration in the EMC and right click server>prop>log settings.

 

However, use the EMC>Toolbox>Tracking Log Explorer to perform a search. (Takes a few times to get it right, have a play around as you may not get any results back if you dont put in the "appropiate criteria" exch is looking for).

[RabbieBurns]

Ive only got 1 database so cannot move him to test.

 

This is the results of the logs, im not sure what they mean:

 

[sukh]

Are we saying that the recipient never gets's the message or they do and you get the NDR too?