• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2354
  • Last Modified:

Outlook 2011 for Mac Send email limitation

I have researched and researched and cannot figure out why Outlook 2011 for Mac cannot send and email attachment of more than 10MB in size.  I have changed the sending and receiving limits on exchange in the web.config files for owa and ews and also the personal mailbox limit for this individual.  We also have him set up on Mac Mail which he is able to send the same attachment through exchange.  We can send the same attachment through web access with his account so it is obviously, an Outlook 2011 for mac issue.  

This client upgraded to Exchange 2007 and Office 2011 for Mac because Outlook now works directly with exchange but this issue is putting a damper on the whole experience for him.  Any help is appreciated.
0
accucom
Asked:
accucom
  • 4
  • 3
1 Solution
 
endital1097Commented:
Look at your EWS web.config file (%programfiles%\microsoft\exchange server\clientaccess\exchweb\ews)
Verify that you have increased the maxRequestLength
0
 
accucomAuthor Commented:
Below is my web.config file in this directory.  At least most of it as I left out the middle of it which did not have maxRequestLength.   Bottom line, the maxrequestlength is not added and i am not sure where to add it or if I should?

<?xml version="1.0"?>
<!-- Note: As an alternative to hand editing this file you can use the web admin tool to
             configure settings for your application. Use the Website->Asp.Net Configuration option
             in Visual Studio.
     A full list of settings and comments can be found in machine.config.comments usually
     located in \Windows\Microsft.Net\Frameworks\v2.x\Config -->

<configuration>
      <runtime>
            <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
                  <dependentAssembly>
                        <assemblyIdentity name="Microsoft.Exchange.Common.IL" publicKeyToken="31bf3856ad364e35" culture="neutral" />
                        <codeBase version="0.0.0.0" href="file:///C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Common.IL.dll"/>
                  </dependentAssembly>
                  <assemblyIdentity name="microsoft.exchange.core.strings.resources" publicKeyToken="31bf3856ad364e35" culture="zh-CHS" />
                        <codeBase version="8.0.0.0" href="file:///C:\Program Files\Microsoft\Exchange Server\bin\zh-CHS\microsoft.exchange.core.strings.resources.dll"/>
                  </dependentAssembly>
                  <dependentAssembly>
                        <assemblyIdentity name="microsoft.exchange.core.strings.resources" publicKeyToken="31bf3856ad364e35" culture="zh-CHT" />
                        <codeBase version="8.0.0.0" href="file:///C:\Program Files\Microsoft\Exchange Server\bin\zh-CHT\microsoft.exchange.core.strings.resources.dll"/>
                  </dependentAssembly>
                  <dependentAssembly>
                        <assemblyIdentity name="microsoft.exchange.core.strings.resources" publicKeyToken="31bf3856ad364e35" culture="zh-HK" />
                        <codeBase version="8.0.0.0" href="file:///C:\Program Files\Microsoft\Exchange Server\bin\zh-HK\microsoft.exchange.core.strings.resources.dll"/>
                  </dependentAssembly>                  

            </assemblyBinding>
      </runtime>

      <appSettings/>
      <connectionStrings/>
      <system.web>
            <httpModules>
                  <add name="AuthorizationModule"
                        type="Microsoft.Exchange.Services.AuthorizationModule, Microsoft.Exchange.Services, Version=8.0.0.0, Culture=neutral, publicKeyToken=31bf3856ad364e35"/>
                  <add name="PerformanceCounterModule"
                        type="Microsoft.Exchange.Services.PerformanceCounterModule, Microsoft.Exchange.Services, Version=8.0.0.0, Culture=neutral, publicKeyToken=31bf3856ad364e35"/>
            </httpModules>

            <webServices>
                  <soapExtensionTypes>
                        <add type="Microsoft.Exchange.Services.ServiceExtensionManager, Microsoft.Exchange.Services, Version=8.0.0.0, Culture=neutral, publicKeyToken=31bf3856ad364e35" priority="1" group="1"></add>
                        <add type="Microsoft.Exchange.Services.ClientResponseSizeLimitSoapExtension, Microsoft.Exchange.Services, Version=8.0.0.0, Culture=neutral, publicKeyToken=31bf3856ad364e35" priority="1" group="1"></add>
                  </soapExtensionTypes>
                  <!-- Remove the autogenerated test page and wsdl file generation.  Consumers should use
                  Services.wsdl directly instead of folder.asmx?wsdl (for example) -->
                  <protocols>
                        <remove name="Documentation"/>
                  </protocols>
            </webServices>

            <identity impersonate="false"/>
            <!--
            Set compilation debug="true" to insert debugging symbols into the compiled page.
            Because this affects performance, set this value to true only during development.
        -->
            <compilation debug="false"/>
            <!--
            The <authentication> section enables configuration of the security authentication
            mode used by ASP.NET to identify an incoming user.
        -->
            <authentication mode="Windows"/>
            <!--
            The <customErrors> section enables configuration of what to do if/when an unhandled
            error occurs during the execution of a request.  Specifically, it enables developers
            to configure html error pages to be displayed in place of a error stack trace.
        -->
            <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
                  <!--
            <error statusCode="403" redirect="NoAccess.htm"/>
            <error statusCode="404" redirect="FileNotFound.htm"/>
        -->
            </customErrors>
      </system.web>
</configuration>


0
 
endital1097Commented:
I am attaching a sample web.config for ews (from an sp3 server)
web.config
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
accucomAuthor Commented:
Ok, it looks pretty much the same except that I am missing the <httpRuntime maxRequestLength="13280" /> right after the <system.web> and before httpModules.  Have you seen a web.config file that was missing the maxRequestLength before and is it safe to add it?  thanks.
0
 
endital1097Commented:
no, i've never seen that missing
that value is in kb, so you may want to increase for your environment as needed
0
 
accucomAuthor Commented:
ok, found another post where the maxrequestlength is missing from the web.config file in ews.  Not sure if I could just add it or not but this could be the solution!  Anybody else seen this before and did you find a solution?  The maxrequestlength is in the web.config file under owa but not ews.
0
 
endital1097Commented:
you need to add this for ews as that is what mac clients use
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now