%windir%\system32\inetsrv\appcmd.exe set config "Exchange Back End/owa/" -section:system.webServer/security/requestFiltering /requestLimits.maxAllowedContentLength:133000000 %windir%\system32\inetsrv\appcmd.exe set config "Default Web Site/owa/" -section:system.web/httpRuntime /maxRequestLength:133000 %windir%\system32\inetsrv\appcmd.exe set config "Default Web Site/owa/" -section:system.webServer/security/requestFiltering /requestLimits.maxAllowedContentLength:133000000 Open an elevated command prompt on the Exchange server and simply run the following commands while replace the ending numbers with your desired values. you need to do this in all of your Exchange servers. Instead of using a text editor to edit dozens of files, you can also configure this client-specific message size limits from the command line. So, by changing some values in some web.config files, issue will be resolved ? the answere is Yes.īut this is so much time consuming, specially in environments like mine, that there are dozens of exchange servers. then the root of this issue, is obviously these default configurations. The above variables that I just mentioned, in a default deployment of Microsoft Exchange, are set to a value near 35 MB. In the configuration file, you can set variables, such as " maxAllowedContentLength", " maxRequestLength", " maxReceivedMessageSize" and " maxStringContentLength" to control the way a user can interact with the website. The Outlook Web App ( OWA ) is actually a website! and as we explained, there are web.config files, which includes some configuration for the website.
In Microsoft Windows Server, every website function through IIS and IIS can get site configuration through a file called "web.config". If you chose a value higher than 35000 Kb (about 34MB) users will be able to attach bigger files via outlook, but it will not work through OWA ( Outlook Web App), and you should be blaming IIS for this issue!
In Microsoft Exchange, there are different places that you can change the size limit for messages, as follow :