A user who sends larger files asked me to raise her maximum size for sent messages. I see this can be done per user, and also, more generally: - Per Send Connector (Organization Level, Hub Transport) - Under the Global Settings tab > Transport Settings (Organization Level, Hub Transport) Where do I need to adjust the maximum size so this works for the sender? In her properties only? In all places listed above? If not one of those choices, which one? Thank you in advance.

When I encountered this issue, I thought it could be done at the user and even at the database level. Eventually, I ended up increasing the max send and receive for send and receive connectors. Take a look at this: http://www.msexchange.org/articles-tutorials/exchange-server-2007/management-administration/exchange-2007-message-size-limits.html.

Hi, For personal mailbox limit setting you can use cmdlet Set-mailbox , more detail information refer to : http://technet.microsoft.com/en-us/library/bb124345(EXCHG.80).aspx

please reffer to Order of Precedence for Message Size Limits You can set different message size limits for the same message component, such as the maximum message size, at different levels in the Exchange organization. When different message size limits are applied to the same message component, Exchange 2007 uses an order of precedence to enforce the message size limit that is imposed on the same message component. For example, the recipient will receive a message that was sent by a particular sender if the following conditions are true: An organization-wide send and receive message size limit of 10 MB is imposed on the Exchange 2007 organization. A particular sender's mailbox has a send message size limit of 20 MB. The recipient's mailbox has a receive message size limit of 20 MB. Generally, it is better to maximize the restrictiveness of your message size limits. You should base any exceptions on a proven need to exceed the established size limits, and you should put those limits as close as possible to the objects that must exceed the established size limits. This strategy helps make sure that messages in the transport pipeline are rejected as early as possible if they violate message size limits. It is a waste of system resources to set a high message size limit at the Exchange organization level, allow a message to enter the Exchange organization, and then reject the message at the last stage of delivery because of a violation of a message size limit. from http://technet.microsoft.com/en-us/library/bb124345(EXCHG.80).aspx Dhruv