locked
Microsoft Exchange 2007 - Unable to send Emails to mail contacts in GAL RRS feed

  • Question

  • Hi there, 

    We are getting the following error message when we try sending an email to a Mail Contact which is part of our GAL, the error is as below: 

    Diagnostic information for administrators:

    Generating server: server.domain.com

    IMCEAEX-_O=NT5_ou=92B35CE8EAC2A148B34A50DD8E4276D4_cn=51288C5476FA5B4AAC30FD4391985772@nbki.com #550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

    Original message headers:

    Received: from server.doamin.com ([192.168.10.246]) by server.domain.com  ([192.168.10.246]) with mapi; Thu, 4 Jul 2013 09:46:42 +0100 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: binary From: Nawaz Ali Pir <Nawaz.Pir@domain.com> To: Imran Minhas             <IMCEAEX-_O=NT5_ou=92B35CE8EAC2A148B34A50DD8E4276D4_cn=51288C5476FA5B4AAC30FD4391985772@domain.com> Date: Thu, 4 Jul 2013 09:46:42 +0100 Subject: Test from outlook Thread-Topic: Test from outlook Thread-Index: Ac54kwAAAZN2zrExT6qpeBOvOSO12A== Message-ID: <4F9F637CC2A5344A9AD174056D37B187679475E145@server.domain.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: <4F9F637CC2A5344A9AD174056D37B187679475E145@server.domain.com> MIME-Version: 1.0

    I have gone through various forums and all of them mention to change the legacyExchangeDN attribute and then clean the autocomplete field, finally update the offline address book.

    Unfortunately this has not worked for me.

    I went a step further and created a new profile on outlook and still i am getting the bouncebacks. Any help will be appreciated.

    Regards, 

    Nawaz 


    Thursday, July 4, 2013 11:21 AM

Answers

  • Hi, 

    It works fine when trying to send via the OWA. 

    I have also used the get-mailcontact cmdlet to confirm and the contact is there. 

    This system has been in place for a very long time, we had used the update-globaladdresslist command before this problem arose. 

    Anything else you may recommend that i may try? 

    thanks 

    That "NT5" in the legacyExchangeDN usually means that the AD object has no legacyExchangeDN

    http://blogs.msdn.com/b/dgoldman/archive/2005/11/18/oab-pdn-changes-and-exchange-site-consolidations.aspx

    If the Contact appears in the EMC, try disabling it and then enable it. That should get the error fixed. Wait for AD replication and then regenerate the OAB and have the clients download the OAB. If you're using web-based OAB distribution be aware that the CAS servers don't update immediately -- IIRC they only sync every 4 or 6 hours.


    --- Rich Matheisen MCSE&I, Exchange MVP

    Sunday, July 7, 2013 3:18 PM

All replies

  • Hello,

    I recommend you check if the issue occur when you use owa.

    If owa has the same issue, please use the get-mailcontact cmdlet to check if there is the contact.

    And please make sure whether there is a migration.


    Cara Chen
    TechNet Community Support

    Friday, July 5, 2013 8:53 AM
    Moderator
  • Hi, 

    It works fine when trying to send via the OWA. 

    I have also used the get-mailcontact cmdlet to confirm and the contact is there. 

    This system has been in place for a very long time, we had used the update-globaladdresslist command before this problem arose. 

    Anything else you may recommend that i may try? 

    thanks 

    Friday, July 5, 2013 9:07 AM
  • If OWA works fine that the problem is not with the GAL contact, it seems your OAB has not been successfully generated, did you check if you are successfully getting 9107 in apps log for OAB generated successfully and the CAS also has updated OAB files. Create a new mailbox trying to sending email from there..


    Don't Let go..

    Friday, July 5, 2013 9:31 AM
  • Hi, 

    It works fine when trying to send via the OWA. 

    I have also used the get-mailcontact cmdlet to confirm and the contact is there. 

    This system has been in place for a very long time, we had used the update-globaladdresslist command before this problem arose. 

    Anything else you may recommend that i may try? 

    thanks 

    That "NT5" in the legacyExchangeDN usually means that the AD object has no legacyExchangeDN

    http://blogs.msdn.com/b/dgoldman/archive/2005/11/18/oab-pdn-changes-and-exchange-site-consolidations.aspx

    If the Contact appears in the EMC, try disabling it and then enable it. That should get the error fixed. Wait for AD replication and then regenerate the OAB and have the clients download the OAB. If you're using web-based OAB distribution be aware that the CAS servers don't update immediately -- IIRC they only sync every 4 or 6 hours.


    --- Rich Matheisen MCSE&I, Exchange MVP

    Sunday, July 7, 2013 3:18 PM