none
Distribution List - Exchange 2003 e Exchange 2010

    Pregunta

  • I am having problems with DLs.

    We've migrated all mailboxes from Exchange 2003 to 2010, but not the DLs.

    We have a DL that is set with restrictions to receive messages, it only receives messages from specific users.

    But sometimes it doesn't work. We are receiving e-mails from user with no permissions to send to that DL.

    I've checked more then 10 times the permissions and groups from the user, and it is ok.

    Any ideas?


    viernes, 02 de marzo de 2012 2:00

Respuestas

  • That is the answer from Microsoft.

    "It is important to  mention that is recommended to make the upgrade for all the objects and for the Distribution Lists change the Group Scope to UNIVERSAL, once that the migration to Exchange 2010 is in place, this with the idea to be able to have the extended features from the Exchange 2010 and to avoid any possible issue due to the version on the objects (ExchangeVersion attribute). <u5:p></u5:p>

    <u5:p> </u5:p>

    A mail-enabled Active Directory global or local group object. Mail-enabled non-universal groups were discontinued in Exchange Server 2007 and can exist only if they were migrated from Exchange 2003 or earlier versions of Exchange. You can't use Exchange 2010 to create non-universal distribution groups.<u5:p></u5:p>

                   Ref: http://technet.microsoft.com/en-us/library/bb201680.aspx<u5:p></u5:p>

    <u5:p> </u5:p>

    In this particular scenario there are some know issues that may explain the behavior that you experience, this because the ExpansionServer attribute is not defined on the object:<u5:p></u5:p>

    <u5:p> </u5:p>

    In this scenario, the following chain of events occurs if an Exchange 2010 sender sends a message to the Sales distribution group:<u5:p></u5:p>

    1. The message is sent to a Hub Transport server. <u5:p></u5:p>
    2. Because the Sales distribution group isn't configured to use a Hub Transport server as the distribution group expansion server, the journal rules in the Exchange 2010 organization can't access the distribution group recipients. Therefore, no journal rules can be applied to the recipients in the distribution group.<u5:p></u5:p>
    3. The message is routed to the Exchange 2003 server for expansion. <u5:p></u5:p>
    4. The Exchange 2003 server expands the distribution group. Because the Exchange 2003 server can't access the Exchange 2010 journal rule configuration, no messages are journaled.<u5:p></u5:p>
    5. The Exchange 2003 server routes the expanded messages back to the Exchange 2010 Hub Transport server for delivery to the Exchange 2010 recipients.<u5:p></u5:p>
    6. The Hub Transport server receives the message. Because this isn't the first server to route these messages, the Hub Transport server assumes the messages have already been evaluated for journaling and the journal rules aren't applied.<u5:p></u5:p>

    Ref: http://technet.microsoft.com/en-us/library/aa997918.aspx<u5:p></u5:p>

     <u5:p></u5:p>

    <u5:p> </u5:p>

    In the last example the issue was related to a Journal rule and this is similar to the Message Restriction setting that are values that are being consulted by the Categorizer on the same process when the Distribution List is being expanded.<u5:p></u5:p>

    <u5:p> </u5:p>

    Also is important to mention that we could try to define the cause of the problem with the distribution list if the action plan didn’t provide a solution or more that data that lead us to the cause of the problem, this with extra troubleshooting and data collection with trace tags, but all this tasks will may require several hours that will be charged to your contract. If you agree to continue with the RCA for this issue without the upgrade to Exchange 2010 please let me now.<u5:p></u5:p>

    <u5:p> </u5:p>

    Additional information about the upgrade could be consulted in the following article: http://technet.microsoft.com/en-us/library/cc164375.aspx, http://technet.microsoft.com/en-us/library/bb124955.aspx"

    <u5:p></u5:p>

    <u5:p></u5:p>

    After that, it is working.

    Thank you everyone.

    lunes, 19 de marzo de 2012 17:55

Todas las respuestas

  • Have you upgraded the DLs to Mail Universal Distribution Groups?  How far are you on the decomm of Exchange 2003?  Did you move Public Folders over, update the OAB and move the generation to Exchange 2010?   Also, is the DL expansion setting been changed on the DLs? (that setting is on the Advanced tab of the DL)

    JAUCG


    • Editado JAUCGMVP viernes, 02 de marzo de 2012 19:52
    viernes, 02 de marzo de 2012 19:51
  • Any updates?

    JAUCG

    lunes, 05 de marzo de 2012 18:09
  • I have oppened a ticket with MS, and waiting for answers.

    I know what we need to do, I only need to know WHY?

    But thanks everyone.

    lunes, 05 de marzo de 2012 18:13
  • OK.  Let us know what Microsoft comes back with then.


    JAUCG

    lunes, 05 de marzo de 2012 19:30
  • On Mon, 5 Mar 2012 18:13:23 +0000, Pedro TS Menezes wrote:
     
    >I have oppened a ticket with MS, and waiting for answers.
    >
    >I know what we need to do, I only need to know WHY?
     
    Just curious, but does the DL require that all senders be
    authenticated? That wasn't the default in Exchange 2003. If you allow
    anonymous SMTP sessions to send to the DL then that may be your
    problem.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    lunes, 05 de marzo de 2012 22:08
  • It was requiring that all senders be authenticated, but was not working.
    martes, 06 de marzo de 2012 1:25
  • Hi Pedro,

    Could you run this command and post the result?

    Get-DistributionGroup -identity Distribution List| fl

    Thanks,

    Evan


    Evan Liu

    TechNet Community Support

    martes, 06 de marzo de 2012 10:12
  • Any updates?

    JAUCG

    miércoles, 07 de marzo de 2012 13:10
  • Any further updates?

    JAUCG

    viernes, 09 de marzo de 2012 21:42
  • That is the answer from Microsoft.

    "It is important to  mention that is recommended to make the upgrade for all the objects and for the Distribution Lists change the Group Scope to UNIVERSAL, once that the migration to Exchange 2010 is in place, this with the idea to be able to have the extended features from the Exchange 2010 and to avoid any possible issue due to the version on the objects (ExchangeVersion attribute). <u5:p></u5:p>

    <u5:p> </u5:p>

    A mail-enabled Active Directory global or local group object. Mail-enabled non-universal groups were discontinued in Exchange Server 2007 and can exist only if they were migrated from Exchange 2003 or earlier versions of Exchange. You can't use Exchange 2010 to create non-universal distribution groups.<u5:p></u5:p>

                   Ref: http://technet.microsoft.com/en-us/library/bb201680.aspx<u5:p></u5:p>

    <u5:p> </u5:p>

    In this particular scenario there are some know issues that may explain the behavior that you experience, this because the ExpansionServer attribute is not defined on the object:<u5:p></u5:p>

    <u5:p> </u5:p>

    In this scenario, the following chain of events occurs if an Exchange 2010 sender sends a message to the Sales distribution group:<u5:p></u5:p>

    1. The message is sent to a Hub Transport server. <u5:p></u5:p>
    2. Because the Sales distribution group isn't configured to use a Hub Transport server as the distribution group expansion server, the journal rules in the Exchange 2010 organization can't access the distribution group recipients. Therefore, no journal rules can be applied to the recipients in the distribution group.<u5:p></u5:p>
    3. The message is routed to the Exchange 2003 server for expansion. <u5:p></u5:p>
    4. The Exchange 2003 server expands the distribution group. Because the Exchange 2003 server can't access the Exchange 2010 journal rule configuration, no messages are journaled.<u5:p></u5:p>
    5. The Exchange 2003 server routes the expanded messages back to the Exchange 2010 Hub Transport server for delivery to the Exchange 2010 recipients.<u5:p></u5:p>
    6. The Hub Transport server receives the message. Because this isn't the first server to route these messages, the Hub Transport server assumes the messages have already been evaluated for journaling and the journal rules aren't applied.<u5:p></u5:p>

    Ref: http://technet.microsoft.com/en-us/library/aa997918.aspx<u5:p></u5:p>

     <u5:p></u5:p>

    <u5:p> </u5:p>

    In the last example the issue was related to a Journal rule and this is similar to the Message Restriction setting that are values that are being consulted by the Categorizer on the same process when the Distribution List is being expanded.<u5:p></u5:p>

    <u5:p> </u5:p>

    Also is important to mention that we could try to define the cause of the problem with the distribution list if the action plan didn’t provide a solution or more that data that lead us to the cause of the problem, this with extra troubleshooting and data collection with trace tags, but all this tasks will may require several hours that will be charged to your contract. If you agree to continue with the RCA for this issue without the upgrade to Exchange 2010 please let me now.<u5:p></u5:p>

    <u5:p> </u5:p>

    Additional information about the upgrade could be consulted in the following article: http://technet.microsoft.com/en-us/library/cc164375.aspx, http://technet.microsoft.com/en-us/library/bb124955.aspx"

    <u5:p></u5:p>

    <u5:p></u5:p>

    After that, it is working.

    Thank you everyone.

    lunes, 19 de marzo de 2012 17:55