Forum Discussion

ArjanBroekhuizen's avatar
ArjanBroekhuizen
Iron Contributor
Apr 12, 2023

Delayed delivery for Dynamic Distribution Groups

Hi all,   We have some problems with the mail-delivery for Dynamic distribution groups. We come from an on-premise Exchange 2013 environment. We created some Dynamic groups, based on the AD-organiz...
exchange online
hybrid
ArjanBroekhuizen's avatar
ArjanBroekhuizen
Iron Contributor
Apr 13, 2023

Hello Andres Bohren,

Thanks. Trottling of old Exchange Servers isn't related, because we have an up-to-date Exchange 2019 server.

I don't think the number of messages p/hour is the problem, our on-premise server isn't that busy. That's why I don't understand some messages are delayed...

Move the Dynamic Distribution Groups to Azure crossed my mind also, but that isn't an option at this moment. Because of the OU based filtering. The properties to filter are in serveral ou's where the groups are based on. In Azure this will result in a wrong groupmembersship.
Knowing that we have to move the groups to Azure in the future, we will work out scenarios to deploy.

For now I hope someone has a suggestion for the problem off the delayed messages.

Andres-Bohren's avatar
Andres-Bohren
Iron Contributor
Apr 13, 2023

ArjanBroekhuizen 

>Trottling of old Exchange Servers isn't related, because we have an up-to-date Exchange 2019 server.

You mentioned Exchange 2013 in your first post. That's why i was pointing in that direction.

Anyway only Exchange 2007 should be throttled at this point.

 

>I don't think the number of messages p/hour is the problem, our on-premise server isn't that busy

It's not what's your Server is capable of delivering. It's what's microsoft is willing to receive.

To get a Number. How big are the dynamic Distribution Groups. How many Members are we're talking about?

 

>Knowing that we have to move the groups to Azure in the future, we will work out scenarios to deploy.

That's the way forward anyway.

 

Maybe you have set an Expansion Server that don't exist anymore. Check this:

Get-DynamicDistributionGroup | ft name, ExpansionServer

 

Regards

Andres Bohren

  • ArjanBroekhuizen's avatar
    ArjanBroekhuizen
    Iron Contributor
    Apr 14, 2023
    Hello Andres Bohren,

    Thanks again.
    The old environment was indeed Exchange 2013. We migrated to Exchange 2019.

    The members per Dynamic group are between 200 and 400.
    When I check the expansionserver, there is no server mentioned in the Powershell-output.
    • Andres-Bohren's avatar
      Andres-Bohren
      Iron Contributor
      Apr 15, 2023

      Hi ArjanBroekhuizen 

       

      >When I check the expansionserver, there is no server mentioned in the Powershell-output.

      Same here - so i guess that's good.

       

      >It is only the hop to Exchange 365 that is delayed.

      So we know the "bottleneck" is between your onPrem Servers (no Edge i guess?) and Exchange Online.

       

      Have a look at your Exchange Online Inbound Connector

      • ConnectorType : OnPremises
      • CloudServicesMailEnabled : True

      Check your Outbound connector OnPrem

      • CloudServicesMailEnabled : True
      • SmtpMaxMessagesPerConnection : 20

      You could also check Get-TransportConfig in EXO and OnPrem or rerun the Exchange Hybrid Wizard.

       

      Other than that i have no idea. Might be a Situation where you need to open a Microsoft Case.

       

      Regards

      Andres

      • ArjanBroekhuizen's avatar
        ArjanBroekhuizen
        Iron Contributor
        Apr 19, 2023
        Hello Andres Bohren,

        Thanks. I reviewed the connector setting and they are configured as you descriped.

        Regards,
        Arjan

Resources