locked
universal security mailenabled groups RRS feed

  • Question

  • Hi

    After migrating from 2007 to 2013 i cant mail to universal security mailenabled groups. When running get-messagetrackinglog i can see that a message is sent to the universal mailenabled group but no one is receiving it. 

    Any clue?

    Monday, March 24, 2014 8:33 PM

Answers

  • it works with newly created universal security mail enabled groups so it has to be something with the migration to do

    I received the following error

    Remote Server at exch2007.contoso.local (IP) returned '400 4.4.7 Message delayed'
    2014-03-24 20:40:00 - Remote Server at
    exch2007.contoso.local (IP) returned '441 4.4.1 Error encountered while communicating with primary target IP address: "Failed to connect. Winsock error code: 10060, Win32 error code: 10060." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was IP:25'<o:p></o:p>

    Monday, March 24, 2014 8:54 PM
  • Hi,

    Please run the following command to check your distribution group configuration:

    Get-DistributionGroup MigratedGroup | FL

    Please make sure the ExchangeVersion is 0.10 (14.0.xxx.x) instead of 0.1 (8.0.xxx.x). If it is the legacy version, we need to update the distribution group to a modern Exchange version. Use Exchange 2013 EMS which can update the Exchange version attribute of the distribution group:

    Thanks,


    Winnie Liang
    TechNet Community Support

    Monday, March 31, 2014 2:50 AM
    Moderator

All replies

  • it works with newly created universal security mail enabled groups so it has to be something with the migration to do

    I received the following error

    Remote Server at exch2007.contoso.local (IP) returned '400 4.4.7 Message delayed'
    2014-03-24 20:40:00 - Remote Server at
    exch2007.contoso.local (IP) returned '441 4.4.1 Error encountered while communicating with primary target IP address: "Failed to connect. Winsock error code: 10060, Win32 error code: 10060." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was IP:25'<o:p></o:p>

    Monday, March 24, 2014 8:54 PM
  • Hi,

    Please run the following command to check your distribution group configuration:

    Get-DistributionGroup MigratedGroup | FL

    Please make sure the ExchangeVersion is 0.10 (14.0.xxx.x) instead of 0.1 (8.0.xxx.x). If it is the legacy version, we need to update the distribution group to a modern Exchange version. Use Exchange 2013 EMS which can update the Exchange version attribute of the distribution group:

    Thanks,


    Winnie Liang
    TechNet Community Support

    Monday, March 31, 2014 2:50 AM
    Moderator