none
Delay send message via online mode

    Question

  • Hello,

    I found one issue in my environment: when users connect to Exchange via Outlook in online mode they have following limitations:

    1 message per second

    30 messages per minute

    In cash mode I don;t see this issue.

    Exchange 2013 CU15 and Outlook 2016, connection method MAPI/HTTP, Client and Server in one subnet/AD site/location.

    Avg Resp in both scenarion not more 45

    Avg Proc in both scenarion not more 20

    How can I resolve it?

    Kind regards

    Friday, November 03, 2017 3:26 PM

All replies

  • Hi,

    How are the clients connecting to the Exchange server(s) i.e. HLB, DNS. Has the receive connectors setting changed?

    Friday, November 03, 2017 5:55 PM
  • Hi,

    Thanks for contacting our forum. 

    Does this issue affect users in OWA?

    Does this issue affect specific user in specific server/DB?

    Please also check if any events about message submission in event log and post out in detail if exist.

    Hope it helps and thanks for your efforts.


    Regards,

    Jason Chao


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, November 06, 2017 9:32 AM
    Moderator
  • DNS.

    Receive connectors on MB server have following config (server name removed):

    RunspaceId                              :
    AuthMechanism                           : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
    Banner                                  :
    BinaryMimeEnabled                       : True
    Bindings                                : {0.0.0.0:25}
    ChunkingEnabled                         : True
    DefaultDomain                           :
    DeliveryStatusNotificationEnabled       : True
    EightBitMimeEnabled                     : True
    SmtpUtf8Enabled                         : False
    BareLinefeedRejectionEnabled            : False
    DomainSecureEnabled                     : False
    EnhancedStatusCodesEnabled              : True
    LongAddressesEnabled                    : False
    OrarEnabled                             : False
    SuppressXAnonymousTls                   : False
    ProxyEnabled                            : False
    AdvertiseClientSettings                 : False
    Fqdn                                    :
    ServiceDiscoveryFqdn                    :
    TlsCertificateName                      :
    Comment                                 :
    Enabled                                 : True
    ConnectionTimeout                       : 00:10:00
    ConnectionInactivityTimeout             : 00:05:00
    MessageRateLimit                        : Unlimited
    MessageRateSource                       : IPAddress
    MaxInboundConnection                    : 5000
    MaxInboundConnectionPerSource           : Unlimited
    MaxInboundConnectionPercentagePerSource : 100
    MaxHeaderSize                           : 128 KB (131,072 bytes)
    MaxHopCount                             : 60
    MaxLocalHopCount                        : 12
    MaxLogonFailures                        : 3
    MaxMessageSize                          : 100 MB (104,857,600 bytes)
    MaxProtocolErrors                       : 5
    MaxRecipientsPerMessage                 : 5000
    PermissionGroups                        : ExchangeUsers, ExchangeServers, ExchangeLegacyServers
    PipeliningEnabled                       : True
    ProtocolLoggingLevel                    : None
    RemoteIPRanges                          : {0.0.0.0-255.255.255.255}
    RequireEHLODomain                       : False
    RequireTLS                              : False
    EnableAuthGSSAPI                        : False
    ExtendedProtectionPolicy                : None
    LiveCredentialEnabled                   : False
    TlsDomainCapabilities                   : {}
    Server                                  :
    TransportRole                           : HubTransport
    SizeEnabled                             : EnabledWithoutValue
    TarpitInterval                          : 00:00:05
    MaxAcknowledgementDelay                 : 00:00:30
    AdminDisplayName                        :
    ExchangeVersion                         : 0.1 (8.0.535.0)
    Name                                    : Default
    DistinguishedName                       : CN=Default Receive
                                              Connectors,CN=Protocols,,CN=Servers,CN=Exchange Administrative
                                              Group (FYDIBOHF23SPDLT),CN=Administrative Groups,
    Identity                                :
    Guid                                    : adf772d3-f3ef-49ee-9965-6a64349fc1c5
    ObjectCategory                          : /Configuration/Schema/ms-Exch-Smtp-Receive-Connector
    ObjectClass                             : {top, msExchSmtpReceiveConnector}
    WhenChanged                             : 10/30/2017 3:30:19 PM
    WhenCreated                             : 10/8/2017 10:24:38 AM
    WhenChangedUTC                          : 10/30/2017 3:30:19 PM
    WhenCreatedUTC                          : 10/8/2017 10:24:38 AM
    OrganizationId                          :
    Id                                      :
    OriginatingServer                       :
    IsValid                                 : True
    ObjectState                             : Unchanged

    RunspaceId                              : f8fe3fa2-272a-4903-9b10-d4b4dd6fced7
    AuthMechanism                           : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
    Banner                                  :
    BinaryMimeEnabled                       : True
    Bindings                                : {[::]:465, 0.0.0.0:465}
    ChunkingEnabled                         : True
    DefaultDomain                           :
    DeliveryStatusNotificationEnabled       : True
    EightBitMimeEnabled                     : True
    SmtpUtf8Enabled                         : False
    BareLinefeedRejectionEnabled            : False
    DomainSecureEnabled                     : False
    EnhancedStatusCodesEnabled              : True
    LongAddressesEnabled                    : False
    OrarEnabled                             : False
    SuppressXAnonymousTls                   : False
    ProxyEnabled                            : False
    AdvertiseClientSettings                 : False
    Fqdn                                    : t
    ServiceDiscoveryFqdn                    :
    TlsCertificateName                      :
    Comment                                 :
    Enabled                                 : True
    ConnectionTimeout                       : 00:10:00
    ConnectionInactivityTimeout             : 00:05:00
    MessageRateLimit                        : Unlimited
    MessageRateSource                       : User
    MaxInboundConnection                    : 5000
    MaxInboundConnectionPerSource           : 20
    MaxInboundConnectionPercentagePerSource : 2
    MaxHeaderSize                           : 128 KB (131,072 bytes)
    MaxHopCount                             : 60
    MaxLocalHopCount                        : 12
    MaxLogonFailures                        : 3
    MaxMessageSize                          : 100 MB (104,857,600 bytes)
    MaxProtocolErrors                       : 5
    MaxRecipientsPerMessage                 : 200
    PermissionGroups                        : ExchangeUsers, ExchangeServers
    PipeliningEnabled                       : True
    ProtocolLoggingLevel                    : None
    RemoteIPRanges                          : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
    RequireEHLODomain                       : False
    RequireTLS                              : False
    EnableAuthGSSAPI                        : True
    ExtendedProtectionPolicy                : None
    LiveCredentialEnabled                   : False
    TlsDomainCapabilities                   : {}
    Server                                  :
    TransportRole                           : HubTransport
    SizeEnabled                             : Enabled
    TarpitInterval                          : 00:00:05
    MaxAcknowledgementDelay                 : 00:00:30
    AdminDisplayName                        :
    ExchangeVersion                         : 0.1 (8.0.535.0)
    Name                                    : Client Proxy
    DistinguishedName                       : CN=Client Proxy Receive
                                              Connectors,CN=Protocols,,CN=Servers,CN=Exchange Administrative
                                              Group (FYDIBOHF23SPDLT),CN=Administrative Groups,
    Identity                                :
    Guid                                    : f5c21f87-5547-4c41-8938-b0bbe6b21fb2
    ObjectCategory                          : /Configuration/Schema/ms-Exch-Smtp-Receive-Connector
    ObjectClass                             : {top, msExchSmtpReceiveConnector}
    WhenChanged                             : 11/3/2017 2:38:22 PM
    WhenCreated                             : 10/8/2017 10:24:38 AM
    WhenChangedUTC                          : 11/3/2017 2:38:22 PM
    WhenCreatedUTC                          : 10/8/2017 10:24:38 AM
    OrganizationId                          :
    Id                                      :
    OriginatingServer                       :
    IsValid                                 : True
    ObjectState                             : Unchanged

    Maybe TarpitInterval attribyte answer for this delay?

    Wednesday, November 08, 2017 8:08 AM
  • Cannot be reproduced in OWA (because cannot generate too many messages in web session).

    Application which generate this messages used only one server (MB) and 6 DBs. All of these have this issue.

    Wednesday, November 08, 2017 8:11 AM
  • Thanks for your information.

    Could you please post out one message header of the delayed message? 

    And we can also run the command below to check the message tracking log of one delayed message to see the detailed info in the log:

    Get-MessageTrackingLog -ResultSize Unlimited -Start "11/13/2015 10:30:00AM" -End "11/14/2015 10:00:00AM" –Sender “app@contoso.com” -recipients "123@contoso.com" -MessageSubject "subject" | fl >c:\MTL.txt

    we need to check as below:

    MessageInfo             : 2017-09-29T08:14:42.156Z;SRV=ex2013.test.com:TOTAL-SUB=0.188|SA=0.078|MTSSDA=0.010|MTSSDC=0.0
                              11|MTSSDMO=0.063;MTSS|MTSSD;SRV=ex2013.test.com:TOTAL-HUB=0.265|UTH=0.002|SMRDI=0.010|SMRCL=0
                              .192|SMRC=0.193|SMR=0.203|QS=0.013|CATSM-Malware 
                              Agent=0.047|CATSM=0.048;CAT|CATRS|CATRS-Transport Rule Agent

    Thanks for your efforts.


    Regards,

    Jason Chao


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, November 10, 2017 9:57 AM
    Moderator
  • get-mailbox "internalsender" |fl *throttle*

    find the throttlingpolicy and try to set it to high usage.

    Then test the emails


    Thanks & Regards Ramandeep Singh

    Saturday, November 11, 2017 8:10 AM
  • Issue associated with MAPI over HTTP protocol.

    If Outlook client configured to use MAPI (IMAP4)/SMTP - all works without delay

    If Outlook client configured to use MAPI/RCP over HTTP - we have delay for 30 messages per minute.

    I've check IIS limit and didn't found any properly value for it.

    Maybe anyone know about it?

    Monday, November 13, 2017 7:57 PM
  • Hi,

    Since this issue only occurred in online mode, and didn’t occurred in cached mode.

    Please send one test email to the one test mailbox via the cached mode, and send another test email to the same mailbox via the online mode, record and copy the message header to the Message Analyzer to test.

    Check the difference between them and found which hop was delay.

    Thanks.


    Regards,

    Jason Chao


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Friday, November 17, 2017 2:39 AM
    Moderator