none
Problem with Exchange sending to Live@EDU accounts RRS feed

  • Question

  • We have a automated account creation process which basically does the following:

    • Our student system generates details of new student
    • Passed details to ILM which creates the Live@EDU account
    • Live@EDU contacts Exchange to create a CONTACT for the student on our Exchange 2007 system.

    We have now noticed that when sending to a student (new creations since October this year) we get NDR.

    The message get's as far as the HUB server then seems to resolve the email address to something like this:

    IMCEAEX-_O=NT5_ou=FF76ED0B9E59B046A88E8C0368B27F29_cn=8E4AF092F266894899D1B2F158C57ABC@napier.ac.uk

    NDR message below:

     Generating server: crl-hub-1.napier-mail.napier.ac.uk

     IMCEAEX-_O=NT5_ou=FF76ED0B9E59B046A88E8C0368B27F29_cn=8E4AF092F266894899D1B2F158C57ABC@napier.ac.uk

    #550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

     Original message headers:

    Received: from E2K7MBX.napier-mail.napier.ac.uk ([146.176.250.56]) by

     crl-hub-1.napier-mail.napier.ac.uk ([146.176.222.89]) with mapi; Mon, 12 Dec
     2011 14:36:19 +0000
    Content-Type: application/ms-tnef; name="winmail.dat"
    Content-Transfer-Encoding: binary
    From: "Fallon, Sue" <S.Fallon@napier.ac.uk>
    To: "Ejimadu, Ikenna"
                <IMCEAEX-_O=NT5_ou=FF76ED0B9E59B046A88E8C0368B27F29_cn=8E4AF092F266894899D1B2F158C57ABC@napier.ac.uk>
    Date: Mon, 12 Dec 2011 14:36:18 +0000
    Subject: test
    Thread-Topic: test
    Thread-Index: Acy422ivrpz4PLq6T2KYdm7vXhXv1w==
    Message-ID: <78F1C759D89E1C44A6DD4C06B9A4B270C8394F00C8@E2K7MBX.napier-mail.napier.ac.uk>
    Accept-Language: en-US, en-GB
    Content-Language: en-US
    X-MS-Has-Attach: yes
    X-MS-TNEF-Correlator: <78F1C759D89E1C44A6DD4C06B9A4B270C8394F00C8@E2K7MBX.napier-mail.napier.ac.uk>
    MIME-Version: 1.0

    The only thing that has been changed recently on our system is that our old connection to Exchange 2003 has been shut down but the connector to our Exchange system for the Live@EDU domain is still there and works fine.

     

    Anyone with any idea why this has started??

     

    Thanks

    Sue

    Monday, December 12, 2011 3:37 PM

Answers

  • On Tue, 13 Dec 2011 09:37:25 +0000, admin_napier wrote:
     
    >Hi Rich, Thanks for your reply.
    >
    >IMCEAEX-_ou=FF76ED0B9E59B046A88E8C0368B27F29_cn=8E4AF092F26689 4899D1B2F158C57ABC@napier.ac.uk is not present in AD and when sending to it I still get an NDR.
    >
    >Compairing 2 accounts (1 that works and 1 that does not work), we have noticed the following:
    >
    >Account that works - 40070787 ? created the 2<sup>nd</sup> July 2011
    >
    > AddressListMembership : {Exchange Labs - All Students, Default Global Address List, All Students, Dept Admin}
    >
    >and
    >
    > LegacyExchangeDN : /O=Napier University/OU=Napier/cn=Recipients/cn=40070787
    >
    > Account that does NOT work - 10004199 ? created the 7<sup>th</sup> December 2011
    >
    > AddressListMembership : {Default Global Address List, All Students, Exchange Labs - All Students, Dept Admin}
    >
    >and
    >
    > LegacyExchangeDN :
    >
    >The removal of the old Exchange system also would have removed the recipient update service which might be the cause of the legacyexchangeDN not being populated.
     
    Absolutely correct. Your hoster (Live@EDU) can no longer just dump the
    objects into the AD and depend on the RUS to populate them with the
    necessary attributes and permissions.
     
    Have a look at the Enable-MailContact cmdlet in the EMS. If you want
    to fix just one or two you can use the EMC and select the existing
    contact to mail-enable.
     
    >Re- your points
    >
    >Is the domain "napier.ac.uk" in your "Accepted Domains" list? - Yes
     
    >Is your organization authoritative for the domain? - Yes
     
    So it's safe to assume that the Primary/External SMTP address on the
    Contact will be using something other than 'napier.ac.uk' in the
    domain portion? Office 365, for example, would use a domain like
    "hosted.napier.ac.edu" in the External E-Mail address and
    "napier.ac.edu" in the Primary SMTP Address to direct the messages to
    the hoster for delivery to the mailbox.
     
    >Can you find the Contact named "8E4AF092F266894899D1B2F158C57ABC" (that's probably the 'alias') in your AD? - NO
     
    I think it'd be a good idea to contact the hoster and explain this
    problem to them. Unless they require the presence of an Exchange 2003
    RUS they can tell you how to deal with this situation -- or then can
    fix it on their end.
     
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Proposed as answer by Sophia Xu Wednesday, December 14, 2011 2:26 AM
    • Marked as answer by admin_napier Wednesday, December 14, 2011 9:08 AM
    Tuesday, December 13, 2011 3:38 PM

All replies

  • On Mon, 12 Dec 2011 15:37:47 +0000, admin_napier wrote:
     
    >
    >
    >We have a automated account creation process which basically does the following: Our student system generates details of new student Passed details to ILM which creates the Live@EDU account Live@EDU contacts Exchange to create a CONTACT for the student on our Exchange 2007 system.
    >
    >We have now noticed that when sending to a student (new creations since October this year) we get NDR.
    >
    >The message get's as far as the HUB server then seems to resolve the email address to something like this:
    >
    >IMCEAEX-_O=NT5_ou=FF76ED0B9E59B046A88E8C0368B27F29_cn=8E4AF092F266894899D1B2F158C57ABC@napier.ac.uk
    >
    >NDR message below:
    >
    > Generating server: crl-hub-1.napier-mail.napier.ac.uk
    >
    > IMCEAEX-_O=NT5_ou=FF76ED0B9E59B046A88E8C0368B27F29_cn=8E4AF092F266894899D1B2F158C57ABC@napier.ac.uk
    >
    >#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##
    >
    > Original message headers:
    >
    >Received: from E2K7MBX.napier-mail.napier.ac.uk ([146.176.250.56]) by
    >
    > crl-hub-1.napier-mail.napier.ac.uk ([146.176.222.89]) with mapi; Mon, 12 Dec 2011 14:36:19 +0000 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: binary From: "Fallon, Sue" To: "Ejimadu, Ikenna" <IMCEAEX-_O=NT5_ou=FF76ED0B9E59B046A88E8C0368B27F29_cn=8E4AF092F266894899D1B2F158C57ABC@napier.ac.uk> Date: Mon, 12 Dec 2011 14:36:18 +0000 Subject: test Thread-Topic: test Thread-Index: Acy422ivrpz4PLq6T2KYdm7vXhXv1w== Message-ID: <78F1C759D89E1C44A6DD4C06B9A4B270C8394F00C8@E2K7MBX.napier-mail.napier.ac.uk> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: <78F1C759D89E1C44A6DD4C06B9A4B270C8394F00C8@E2K7MBX.napier-mail.napier.ac.uk> MIME-Version: 1.0
    >
    >The only thing that has been changed recently on our system is that our old connection to Exchange 2003 has been shut down but the connector to our Exchange system for the Live@EDU domain is still there and works fine.
    >
    >
    >
    >Anyone with any idea why this has started??
     
    Is the domain "napier.ac.uk" in your "Accepted Domains" list? Is your
    organization authoritative for the domain?
     
    Can you find the Contact named "8E4AF092F266894899D1B2F158C57ABC"
    (that's probably the 'alias') in your AD?
     
    Did you remove any Administrative Groups from your Exchange
    organization? The presence of the "NT5" in the encapsulated address
    means the message was probably addressed using the Offline Address
    Book and that there's a missing container where the associated objects
    used to reside in the AD.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Monday, December 12, 2011 8:04 PM
  • Hi Rich, Thanks for your reply.

    IMCEAEX-_ou=FF76ED0B9E59B046A88E8C0368B27F29_cn=8E4AF092F26689 4899D1B2F158C57ABC@napier.ac.uk is not present in AD and when sending to it I still get an NDR.

    Compairing 2 accounts (1 that works and 1 that does not work), we have noticed the following:

    Account that works - 40070787 – created the 2<sup>nd</sup> July 2011

        AddressListMembership  : {Exchange Labs - All Students, Default Global Address List, All Students, Dept Admin}

    and

      LegacyExchangeDN  : /O=Napier University/OU=Napier/cn=Recipients/cn=40070787

     Account that does NOT work - 10004199 – created the 7<sup>th</sup> December 2011

       AddressListMembership  : {Default Global Address List,   All Students, Exchange Labs - All Students, Dept Admin}

    and

      LegacyExchangeDN   :

    The removal of the old Exchange system also would have removed the recipient update service which might be the cause of the legacyexchangeDN not being populated.

    Re- your points

    Is the domain "napier.ac.uk" in your "Accepted Domains" list? - Yes

    Is your organization authoritative for the domain? - Yes

    Can you find the Contact named "8E4AF092F266894899D1B2F158C57ABC" (that's probably the 'alias') in your AD? - NO

     

    Regards

    Sue


    Sue Fallon
    Tuesday, December 13, 2011 9:37 AM
  • On Tue, 13 Dec 2011 09:37:25 +0000, admin_napier wrote:
     
    >Hi Rich, Thanks for your reply.
    >
    >IMCEAEX-_ou=FF76ED0B9E59B046A88E8C0368B27F29_cn=8E4AF092F26689 4899D1B2F158C57ABC@napier.ac.uk is not present in AD and when sending to it I still get an NDR.
    >
    >Compairing 2 accounts (1 that works and 1 that does not work), we have noticed the following:
    >
    >Account that works - 40070787 ? created the 2<sup>nd</sup> July 2011
    >
    > AddressListMembership : {Exchange Labs - All Students, Default Global Address List, All Students, Dept Admin}
    >
    >and
    >
    > LegacyExchangeDN : /O=Napier University/OU=Napier/cn=Recipients/cn=40070787
    >
    > Account that does NOT work - 10004199 ? created the 7<sup>th</sup> December 2011
    >
    > AddressListMembership : {Default Global Address List, All Students, Exchange Labs - All Students, Dept Admin}
    >
    >and
    >
    > LegacyExchangeDN :
    >
    >The removal of the old Exchange system also would have removed the recipient update service which might be the cause of the legacyexchangeDN not being populated.
     
    Absolutely correct. Your hoster (Live@EDU) can no longer just dump the
    objects into the AD and depend on the RUS to populate them with the
    necessary attributes and permissions.
     
    Have a look at the Enable-MailContact cmdlet in the EMS. If you want
    to fix just one or two you can use the EMC and select the existing
    contact to mail-enable.
     
    >Re- your points
    >
    >Is the domain "napier.ac.uk" in your "Accepted Domains" list? - Yes
     
    >Is your organization authoritative for the domain? - Yes
     
    So it's safe to assume that the Primary/External SMTP address on the
    Contact will be using something other than 'napier.ac.uk' in the
    domain portion? Office 365, for example, would use a domain like
    "hosted.napier.ac.edu" in the External E-Mail address and
    "napier.ac.edu" in the Primary SMTP Address to direct the messages to
    the hoster for delivery to the mailbox.
     
    >Can you find the Contact named "8E4AF092F266894899D1B2F158C57ABC" (that's probably the 'alias') in your AD? - NO
     
    I think it'd be a good idea to contact the hoster and explain this
    problem to them. Unless they require the presence of an Exchange 2003
    RUS they can tell you how to deal with this situation -- or then can
    fix it on their end.
     
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Proposed as answer by Sophia Xu Wednesday, December 14, 2011 2:26 AM
    • Marked as answer by admin_napier Wednesday, December 14, 2011 9:08 AM
    Tuesday, December 13, 2011 3:38 PM