A little something about everything

internet marketing and website development made simple..

This message wasn't delivered to anyone because it's too large. The limit is 10 MB. This message is / 550 5.2.3 RESOLVER.RST.SendSizeLimit.Org; message too large for this organization

21 August 2013 Shawn-Hyde Quick Tips (2)

Error:

This message wasn't delivered to anyone because it's too large. The limit is 10 MB. This message is

This message won't be sent because it's too large

#550 5.2.3 RESOLVER.RST.SendSizeLimit.Org; message too large for this organization ##

 

Solution:

Adjust the limits with the following powershell commands:

 Set-TransportConfig -InternalDsnMaxMessageAttachSize #MB

 Set-TransportConfig -ExternalDsnMaxMessageAttachSize #MB

then

 Set-TransportConfig -MaxReceiveSize #MB -MaxSendSize #MB

or

 Set-Mailbox "User" -MaxSendSize #MB -MaxReceiveSize #MB

Comments (2) -

  • Anonymus

    6/19/2015 4:44:33 AM |

    "Adjust the limits with the following powershell commands:

    Set-TransportConfig -InternalDsnMaxMessageAttachSize #MB

    Set-TransportConfig -ExternalDsnMaxMessageAttachSize #MB"

    This is incorrect. ExternalDsnMaxMessageAttachSize refers to the Delivery Status Notification Attachment Size not to the regular message users send out. Same for the InternaDsnMaxMessageAttachSize .

  • Shawn

    6/21/2015 6:43:19 AM |

    You would still want to set this in most cases, unless you are using archiving that charges a lot per GB and/or are sending lots of large attachments in your organization.

    The advantage is if you typo and email or it bounces for some other reason you have the full attachment right with the DSN, saving you time(money) looking for it in a sent folder.

Add comment

Loading