none
The server response was: 4.4.2 Message submission rate for this client has exceeded the configured limit

    Question


  • Some Background: we have migrated the customers Exchange 2007 to a Exchange 2013 single server. there are 5 internal receive connectors that worked on the old server. we recreated them on the new Exchange server. We have an internal application that sends mail to the exchange server. we are missing some messages and the 192.168.10.6 server is reporting this message over and over

    from the customer: the program is creating one statement that is sent to no more than 2 or 3 recipients.It is not accepting the same document with a list of 100 recipients so the limit should not be a factor.  I perceive the issue to be with the volume of documents being sent and Exchange accepting them at a quick rate, there has to be a setting somewhere for this.   This worked on our old server and needs to setup the exact same way.

    The server response was: 4.4.2 Message submission rate for this client has exceeded the configured limit,  previosly we had a similar error and we increased the MaxinboundConectionPerSource from 20 to 200.
    maxReceipentsPerMessage was increased from 200 to 2000, maxInboundConection, MaxInboundconnectionPerSource are set to 5000, the connector uses port 25 

    [PS] C:\Windows\system32>Get-ReceiveConnector Mackapp | FL


    RunspaceId                              : 372c436b-fb6a-4e98-8045-9c158097da91
    AuthMechanism                           : Tls, Integrated, BasicAuth, 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                                    : MACKMAIL13.MACK.local
    ServiceDiscoveryFqdn                    :
    TlsCertificateName                      :
    Comment                                 :
    Enabled                                 : True
    ConnectionTimeout                       : 00:10:00
    ConnectionInactivityTimeout             : 00:05:00
    MessageRateLimit                        : Unlimited
    MessageRateSource                       : IPAddress
    MaxInboundConnection                    : 5000
    MaxInboundConnectionPerSource           : 5000
    MaxInboundConnectionPercentagePerSource : 100
    MaxHeaderSize                           : 128 KB (131,072 bytes)
    MaxHopCount                             : 60
    MaxLocalHopCount                        : 12
    MaxLogonFailures                        : 3
    MaxMessageSize                          : 35 MB (36,700,160 bytes)
    MaxProtocolErrors                       : 5
    MaxRecipientsPerMessage                 : 200
    PermissionGroups                        : AnonymousUsers, ExchangeUsers, ExchangeServers, ExchangeLegacyServers,
                                              Partners
    PipeliningEnabled                       : True
    ProtocolLoggingLevel                    : Verbose
    RemoteIPRanges                          : {192.168.100.6}
    RequireEHLODomain                       : False
    RequireTLS                              : False
    EnableAuthGSSAPI                        : False
    ExtendedProtectionPolicy                : None
    LiveCredentialEnabled                   : False
    TlsDomainCapabilities                   : {}
    Server                                  : MACKMAIL13
    TransportRole                           : FrontendTransport
    SizeEnabled                             : Enabled
    TarpitInterval                          : 00:00:05
    MaxAcknowledgementDelay                 : 00:00:30
    AdminDisplayName                        :
    ExchangeVersion                         : 0.1 (8.0.535.0)
    Name                                    : MACKAPP
    DistinguishedName                       : CN=MACKAPP,CN=SMTP Receive
                                              Connectors,CN=Protocols,CN=MACKMAIL13,CN=Servers,CN=Exchange Administrative
                                              Group (FDYIBOHF23SPDLT),CN=Administrative
                                              Groups,CN=MACKGroupAssociates,CN=Microsoft
                                              Exchange,CN=Services,CN=Configuration,DC=MACK,DC=local
    Identity                                : MACKMAIL13\MACKAPP
    Guid                                    : 766cfa96-6158-434f-9420-fe0f2966c8cd
    ObjectCategory                          : CGA.local/Configuration/Schema/ms-Exch-Smtp-Receive-Connector
    ObjectClass                             : {top, msExchSmtpReceiveConnector}
    WhenChanged                             : 3/5/2018 11:44:47 AM
    WhenCreated                             : 2/19/2018 4:45:01 PM
    WhenChangedUTC                          : 3/5/2018 4:44:47 PM
    WhenCreatedUTC                          : 2/19/2018 9:45:01 PM
    OrganizationId                          :
    Id                                      : MACKMAIL13\MACKAPP
    OriginatingServer                       : MACKSENDER.MACK.local
    IsValid                                 : True
    ObjectState                             : Unchanged

    Can anyone offer any other suggestions?

    Thanks


    Tuesday, March 6, 2018 9:35 PM

Answers

  • Thanks for response.

    Yes, it could be. we can check the value MaxConcurrentMailboxSubmissions to 200 and check the results.

    Please note: after changed the value please restart the transport service.



    Best 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.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Marked as answer by ATS-OCSTEAM Thursday, April 26, 2018 1:38 PM
    Tuesday, April 3, 2018 2:36 AM
    Moderator

All replies

  • Have you check on with Transport Config? Try get-transportconfig 
    Wednesday, March 7, 2018 12:16 AM
  • looking it over now, here it is;

    [PS] C:\Windows\system32>Get-TransportConfig
    Creating a new session for implicit remoting of "Get-TransportConfig" command...


    AddressBookPolicyRoutingEnabled                             : False
    AnonymousSenderToRecipientRatePerHour                       : 1800
    ClearCategories                                             : True
    ConvertDisclaimerWrapperToEml                               : False
    DSNConversionMode                                           : UseExchangeDSNs
    JournalArchivingEnabled                                     : False
    ExternalDelayDsnEnabled                                     : True
    ExternalDsnDefaultLanguage                                  :
    ExternalDsnLanguageDetectionEnabled                         : True
    ExternalDsnMaxMessageAttachSize                             : 10 MB (10,485,760 bytes)
    ExternalDsnReportingAuthority                               :
    ExternalDsnSendHtml                                         : True
    ExternalPostmasterAddress                                   :
    GenerateCopyOfDSNFor                                        : {5.4.8, 5.4.6, 5.4.4, 5.2.4, 5.2.0, 5.1.4}
    HygieneSuite                                                : Standard
    InternalDelayDsnEnabled                                     : True
    InternalDsnDefaultLanguage                                  :
    InternalDsnLanguageDetectionEnabled                         : True
    InternalDsnMaxMessageAttachSize                             : 10 MB (10,485,760 bytes)
    InternalDsnReportingAuthority                               :
    InternalDsnSendHtml                                         : True
    InternalSMTPServers                                         : {192.168.109.0/24, 192.168.108.0/24, 192.168.103.0/24,
                                                                  192.168.10.20, 192.168.10.30, 192.168.10.152,
                                                                  192.168.10.0/24, 192.168.109.31, 192.168.108.25,
                                                                  192.168.109.20, 192.168.109.15, 192.168.10.6,
                                                                  192.168.10.11, 192.168.10.2}
    JournalingReportNdrTo                                       : <>
    LegacyJournalingMigrationEnabled                            : False
    LegacyArchiveJournalingEnabled                              : False
    LegacyArchiveLiveJournalingEnabled                          : False
    RedirectUnprovisionedUserMessagesForLegacyArchiveJournaling : False
    RedirectDLMessagesForLegacyArchiveJournaling                : False
    MaxDumpsterSizePerDatabase                                  : 36 MB (37,748,736 bytes)
    MaxDumpsterTime                                             : 3.00:00:00
    MaxReceiveSize                                              : Unlimited
    MaxRecipientEnvelopeLimit                                   : 5000
    MaxRetriesForLocalSiteShadow                                : 2
    MaxRetriesForRemoteSiteShadow                               : 4
    MaxSendSize                                                 : Unlimited
    MigrationEnabled                                            : False
    OpenDomainRoutingEnabled                                    : False
    RejectMessageOnShadowFailure                                : False
    Rfc2231EncodingEnabled                                      : False
    SafetyNetHoldTime                                           : 7.00:00:00
    ShadowHeartbeatFrequency                                    : 00:02:00
    ShadowMessageAutoDiscardInterval                            : 2.00:00:00
    ShadowMessagePreferenceSetting                              : PreferRemote
    ShadowRedundancyEnabled                                     : True
    ShadowResubmitTimeSpan                                      : 03:00:00
    SupervisionTags                                             : {Reject, Allow}
    TLSReceiveDomainSecureList                                  : {}
    TLSSendDomainSecureList                                     : {}
    VerifySecureSubmitEnabled                                   : False
    VoicemailJournalingEnabled                                  : True
    HeaderPromotionModeSetting                                  : NoCreate
    Xexch50Enabled                                              : True

    Wednesday, March 7, 2018 2:09 AM
  • Hello,

    Thanks for contacting our forum. Make sure the application is using this receive connector Mackapp via SMTP log. It’s recommended to check others with the command below:

    Get-receiveconnector | ft Name, messageratelimit

    We can set it with the command below:

    Get-receiveconnector -Identity "name" | Set-receiveconnector -messageratelimit unlimited

    Hope it helps.


    Best 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.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Wednesday, March 7, 2018 6:45 AM
    Moderator
  • Yes,

    We have that in there:

    MessageRateLimit                        : Unlimited

    I'll have to check back with the customer if they can run some tests

    Wednesday, March 7, 2018 2:07 PM
  • Some Additional information, This server is virtual on a hyper-v server 2 sockets, 8 virtual processors 36 gb ram, 24used.  Last Night, My co-worker  installed a windows server virtual and it took him over an hour to install,  the host has a raid5 raid array, E5-2420 48 gb ram on the host and we believe it has older 300 gb sas drives.

    We are now starting to think that the reason for the error messages may be the delays in the slow disk array. We had warned the customer of performance issues (in writing too)  before we started on the Exchange migration(300 mailboxes) and suggested a new server for the beginning.

    Let me know your opinion.

    Thanks

    Wednesday, March 7, 2018 5:39 PM
  • What happen if you create a DG and then have the list of recipients in the DG then send to the DG, does that work?
    Wednesday, March 7, 2018 10:51 PM
  • Some Additional information, This server is virtual on a hyper-v server 2 sockets, 8 virtual processors 36 gb ram, 24used.  Last Night, My co-worker  installed a windows server virtual and it took him over an hour to install,  the host has a raid5 raid array, E5-2420 48 gb ram on the host and we believe it has older 300 gb sas drives.

    We are now starting to think that the reason for the error messages may be the delays in the slow disk array. We had warned the customer of performance issues (in writing too)  before we started on the Exchange migration(300 mailboxes) and suggested a new server for the beginning.

    Let me know your opinion.

    Thanks

    Thanks for your response.

    Please check if any back pressure events like 1500X in application log of event viewer, and also check the performance log and make sure the disk AVE read/sec and wirte/sec are below 20ms.

    Hope it helps.


    Best 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.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
    Thursday, March 8, 2018 1:45 AM
    Moderator
  • I was unable to find any event viewer entries described above,  since it's the beginging of the Month, the customer has used his accounting program to send  his  monthly statements out to their customers,  and again received :

    Service not available, closing transmission channel. The server response was: 4.4.2 Message submission rate for this client has exceeded the configured limit

    we ran this command:

    [PS] C:\Windows\system32>Write-Host "Transport service:" -ForegroundColor yellow; Get-TransportService | Format-List Max
    Concurrent*,MaxConnection*,Max*OutboundConnections; Write-Host "Mailbox Transport service:" -ForegroundColor yellow; Get
    -MailboxTransportService | Format-List MaxConcurrent*
    Transport service:


    MaxConcurrentMailboxDeliveries  : 20
    MaxConcurrentMailboxSubmissions : 20
    MaxConnectionRatePerMinute      : 1200
    MaxOutboundConnections          : 1000
    MaxPerDomainOutboundConnections : 20

    Mailbox Transport service:
    MaxConcurrentMailboxDeliveries  : 20
    MaxConcurrentMailboxSubmissions : 20

    [PS] C:\Windows\system32>

    So the question is can the Mailbox deliveries  being 20  affect the incoming submission to the server ?

    Thanks

    Monday, April 2, 2018 1:42 PM
  • Thanks for response.

    Yes, it could be. we can check the value MaxConcurrentMailboxSubmissions to 200 and check the results.

    Please note: after changed the value please restart the transport service.



    Best 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.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Marked as answer by ATS-OCSTEAM Thursday, April 26, 2018 1:38 PM
    Tuesday, April 3, 2018 2:36 AM
    Moderator