Hello all and thanks in advance,

Ex2013cu7

A sender can successfully send me a 7MB .zip file.  Anything larger, I won't receive.  The sender does not get any sort of rejection.  I believe I have the receive connector set to a 35MB limit.  The TransportConfig is also set to 10MB.  The receive limit on my mailbox is unlimited.  I'm thinking my Receive connector "Halff Frontend srvRCH12" and my TransportConfig should likely be the same number, but I raised the RC to 35 as part of my troubleshooting.

[PS] C:\Windows\system32>Get-ReceiveConnector | ft name, maxmessagesize

Name                                                        MaxMessageSize
----                                                        --------------
Default SRVRCH12                                            35 MB (36,700,160 bytes)
Outbound Proxy Frontend SRVRCH12                            10 MB (10,485,760 bytes)
Client Frontend SRVRCH12                                    10 MB (10,485,760 bytes)
Default Frontend SRVRCH12                                   10 MB (10,485,760 bytes)
Halff Frontend srvRCH12                                     35 MB (36,700,160 bytes)
Halff Internal Email Relay                                  11 MB (11,534,336 bytes)

[PS] C:\Windows\system32>Get-TransportConfig | ft maxsendsize, maxreceivesize

MaxSendSize                                                 MaxReceiveSize
-----------                                                 --------------
10 MB (10,485,760 bytes)                                    10 MB (10,485,760 bytes)

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

MaxSendSize                                                 MaxReceiveSize
-----------                                                 --------------
10 MB (10,485,760 bytes)                                    10 MB (10,485,760 bytes)

[PS] C:\Windows\system32>Get-Mailbox "Last, First" | FT name, maxsendsize, maxreceivesize

Name                                    MaxSendSize                             MaxReceiveSize
----                                    -----------                             --------------
Last, First                           Unlimited                               Unlimited

What piece am I missing? 

Thanks,

Willis

Seems like you've got all bases covered; did you restart the "Microsoft Exchange Transport" service after making the changes?  Here's the link to the TechNet, but guessing you may have already read it:

https://technet.microsoft.com/en-us/library/bb124345%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396#Types

Hi. See SMTP session log messages, and receive a response from yo

Hi. See SMTP session log messages, and receive a response from your ser

Hi. See SMTP session log messages, and receive a response from your ser

Hi. See SMTP session log messages, and receive a response from your ser

Hi Willis. Please see the status FAIL ROUTING. (Says Andy)
-Perhaps limiting delivery between servers in the organization.
-Ability to send to an external address, through contact.

Example Step by Step - Exchange 2013 Email Message Size Restriction Detail 

Thanks to B0ndoo7, Oleg.Kovalenko, and Andy David for providing suggestions and clues.

Here was the result of Andy's suggestion to run:  Get-MessageTrackingLog -ResultSize Unlimited -Start "8/25/2015 7:00AM" -End "8/25/2015 5:00PM" -Sender "wilxxxxx@hotmail.com"  |FL  

RecipientStatus : {}

RecipientStatus : {}

RecipientStatus : {}

RecipientStatus : {[{LRT=};{LED=550 5.2.3 RESOLVER.RST.SendSizeLimit.Org; message too large for this
                  organization};{FQDN=};{IP=}]}

Based on that error message, I went hunting and found this:  http://social.technet.microsoft.com/wiki/contents/articles/22765.step-by-step-exchange-2013-email-message-size-restriction-detail.aspx

Step by Step - Exchange 2013 Email Message Size Restriction Detail

Exchange Server 2013 email size restriction

Email size in Exchange server plays an important role for the organization since it acts important factor for bandwidth, storage limit, email queue, CPU utilization and mailbox size. The below article provide deeper stuff on how email size restriction plays in the Exchange server 2013.

The email message size value you are trying to configure should be 33% larger than the actual message sizes. For example if you want to allow 30 MB email size then the message size parameter should be 43 MB value. The reason behind is it uses Base64 encoding which increase the message size to 33% of the real message size.

So I chose to set my limits at 14MB (If my goal was 10MB, 14MB is ~33% more).  I restarted the Transport service and my messages are now flowing.

Willis

• Marked as answer by wilmiester 11 hours 31 minutes ago

Thanks to B0ndoo7, Oleg.Kovalenko, and Andy David for providing suggestions and clues.

Here was the result of Andy's suggestion to run:  Get-MessageTrackingLog -ResultSize Unlimited -Start "8/25/2015 7:00AM" -End "8/25/2015 5:00PM" -Sender "wilxxxxx@hotmail.com"  |FL  

RecipientStatus : {}

RecipientStatus : {}

RecipientStatus : {}

RecipientStatus : {[{LRT=};{LED=550 5.2.3 RESOLVER.RST.SendSizeLimit.Org; message too large for this
                  organization};{FQDN=};{IP=}]}

Based on that error message, I went hunting and found this:  http://social.technet.microsoft.com/wiki/contents/articles/22765.step-by-step-exchange-2013-email-message-size-restriction-detail.aspx

Step by Step - Exchange 2013 Email Message Size Restriction Detail

Exchange Server 2013 email size restriction

Email size in Exchange server plays an important role for the organization since it acts important factor for bandwidth, storage limit, email queue, CPU utilization and mailbox size. The below article provide deeper stuff on how email size restriction plays in the Exchange server 2013.

The email message size value you are trying to configure should be 33% larger than the actual message sizes. For example if you want to allow 30 MB email size then the message size parameter should be 43 MB value. The reason behind is it uses Base64 encoding which increase the message size to 33% of the real message size.

So I chose to set my limits at 14MB (If my goal was 10MB, 14MB is ~33% more).  I restarted the Transport service and my messages are now flowing.

Willis

• Marked as answer by wilmiester Wednesday, August 26, 2015 7:55 PM