Exchange 2013 5MB attachment limit OWA

Posted on 2014-11-24
Last Modified: 2014-12-03
My client uses OWA to send and receive emails but cannot send attachments greater than 5MB

We changed eveything in web.config and the ECP and rebooted the server but alas no luck

We tried virtually every browser and it still does it

Transport limits are both in and out at 50MB
Question by:Bosaloski
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 3
LVL 16

Expert Comment

by:Rajitha Chimmani
ID: 40462487
Check if there are any limits applied at mailbox level. And how does it work in Outlook?

Author Comment

ID: 40462504
Outlook works just fine (only 1 user has it)
The rest have to use OWA
Already checked the limits at the mailbox limit and they are wide open
LVL 20

Expert Comment

by:Peter Hutchison
ID: 40462509
What a about the Receive Connectors and Send Connectors used by the Hub Transport roles?
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

LVL 16

Expert Comment

by:Rajitha Chimmani
ID: 40462533
Do you have the exact error message or is it a undeliverable?

Author Comment

ID: 40462538
They are set to 100MB for receive and unlimited for send.

Author Comment

ID: 40462542
The exact error is:

The following files weren't attached because adding them would cause the message to exceed the maximum size limit of 5MB
LVL 16

Expert Comment

by:Rajitha Chimmani
ID: 40462555
What is the current limit on web.config?

Have you tried moving the user mailbox? Appears to be some corruption as web.config settings are universal and should affect every user not just one.

Accepted Solution

Bosaloski earned 0 total points
ID: 40470525
I was able to resolve the issue myself by going into the advance options of Active Directory and setting the delivercontlength and submissioncontlength to 102400 (100MB) and bouncing the transport service.

Now OWA users can send up to 100MB (highly unlikely they will) as web.config and the exchange mailboxes could already send up to this much.

Author Closing Comment

ID: 40478142
I researched and found some information on AD attributes that are used by OWA and exchange.

Featured Post

Get proactive database performance tuning online

At Percona’s web store you can order full Percona Database Performance Audit in minutes. Find out the health of your database, and how to improve it. Pay online with a credit card. Improve your database performance now!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Unified and professional email signatures help maintain a consistent company brand image to the outside world. This article shows how to create an email signature in Exchange Server 2010 using a transport rule and how to overcome native limitations …
A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
how to add IIS SMTP to handle application/Scanner relays into office 365.
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Suggested Courses
Course of the Month8 days, 12 hours left to enroll

615 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question