Unable to scan to email large documents in Exchange 2007

Posted on 2007-08-10
Medium Priority
Last Modified: 2008-05-30

I just did an upgrade of a SBS 2000 network with Exchange 2000 to Exchange 2007 and 2003 servers.  We have a 2003 Server that runs GFI MailEssentials which downloads our email using its POP3 connector.  Once downloaded it sends it to the Exchange 2007 server.  We have a network copier that we are having issues with scanning to email large documents (I believe around 10mb+) to user's email.  This obviously was not the case before.  I have checked the transport servers on Exchange and as far as I can tell I have set all to 250mb.  I also have increased user mailboxes and messages sizes. In Exchange all users have their internal email address and external address (external set as default).   Is there possibly something I am missing?  I am fairly new to Exchange 2007 so I am still learning.  

This is the output of my transport servers list:
Name                                    : RMD-EXCHANGE
AntispamAgentsEnabled                   : False
ConnectivityLogEnabled                  : False
ConnectivityLogMaxAge                   : 30.00:00:00
ConnectivityLogMaxDirectorySize         : 250MB
ConnectivityLogMaxFileSize              : 10MB
ConnectivityLogPath                     : E:\Program Files\Exchange 2007\Transp
DelayNotificationTimeout                : 04:00:00
ExternalDelayDsnEnabled                 : True
ExternalDNSAdapterEnabled               : True
ExternalDNSAdapterGuid                  : 00000000-0000-0000-0000-000000000000
ExternalDNSProtocolOption               : Any
ExternalDNSServers                      : {}
ExternalIPAddress                       :
ExternalDsnDefaultLanguage              : en-US
ExternalDsnLanguageDetectionEnabled     : True
ExternalDsnMaxMessageAttachSize         : 250MB
ExternalDsnReportingAuthority           : rmd.local
ExternalDsnSendHtml                     : True
ExternalPostmasterAddress               :
InternalDelayDsnEnabled                 : True
InternalDNSAdapterEnabled               : False
InternalDNSAdapterGuid                  : 00000000-0000-0000-0000-000000000000
InternalDNSProtocolOption               : Any
InternalDNSServers                      : {}
InternalDsnDefaultLanguage              : en-US
InternalDsnLanguageDetectionEnabled     : True
InternalDsnMaxMessageAttachSize         : 250MB
InternalDsnReportingAuthority           : rmd-exchange.rmd.local
InternalDsnSendHtml                     : True
MaxConcurrentMailboxDeliveries          : 7
MaxConcurrentMailboxSubmissions         : 20
MaxConnectionRatePerMinute              : 1200
MaxOutboundConnections                  : 1000
MaxPerDomainOutboundConnections         : 20
MessageExpirationTimeout                : 2.00:00:00
MessageRetryInterval                    : 00:01:00
MessageTrackingLogEnabled               : True
MessageTrackingLogMaxAge                : 30.00:00:00
MessageTrackingLogMaxDirectorySize      : 250MB
MessageTrackingLogMaxFileSize           : 10MB
MessageTrackingLogPath                  : E:\Program Files\Exchange 2007\Transp
MessageTrackingLogSubjectLoggingEnabled : True
OutboundConnectionFailureRetryInterval  : 00:10:00
IntraOrgConnectorProtocolLoggingLevel   : None
PickupDirectoryMaxHeaderSize            : 64KB
PickupDirectoryMaxMessagesPerMinute     : 100
PickupDirectoryMaxRecipientsPerMessage  : 100
PickupDirectoryPath                     : E:\Program Files\Exchange 2007\Transp
PipelineTracingEnabled                  : False
ContentConversionTracingEnabled         : False
PipelineTracingPath                     : E:\Program Files\Exchange 2007\Transp
PipelineTracingSenderAddress            :
PoisonMessageDetectionEnabled           : True
PoisonThreshold                         : 2
QueueMaxIdleTime                        : 00:03:00
ReceiveProtocolLogMaxAge                : 30.00:00:00
ReceiveProtocolLogMaxDirectorySize      : 250MB
ReceiveProtocolLogMaxFileSize           : 10MB
ReceiveProtocolLogPath                  : E:\Program Files\Exchange 2007\Transp
RecipientValidationCacheEnabled         : False
ReplayDirectoryPath                     : E:\Program Files\Exchange 2007\Transp
RootDropDirectoryPath                   :
RoutingTableLogMaxAge                   : 7.00:00:00
RoutingTableLogMaxDirectorySize         : 50MB
RoutingTableLogPath                     : E:\Program Files\Exchange 2007\Transp
SendProtocolLogMaxAge                   : 30.00:00:00
SendProtocolLogMaxDirectorySize         : 250MB
SendProtocolLogMaxFileSize              : 10MB
SendProtocolLogPath                     : E:\Program Files\Exchange 2007\Transp
TransientFailureRetryCount              : 6
TransientFailureRetryInterval           : 00:05:00
AntispamUpdatesEnabled                  : False
IsValid                                 : True
OriginatingServer                       : rmd-db.rmd.local
ExchangeVersion                         : 0.1 (8.0.535.0)
DistinguishedName                       : CN=RMD-EXCHANGE,CN=Servers,CN=Exchang
                                          e Administrative Group (FYDIBOHF23SPD
                                          LT),CN=Administrative Groups,CN=First
                                           Organization,CN=Microsoft Exchange,C
Identity                                : RMD-EXCHANGE
Guid                                    : 7a18ab48-2ccc-4b43-a247-1a5ce9b817a9
ObjectCategory                          : rmd.local/Configuration/Schema/ms-Exc
ObjectClass                             : {top, server, msExchExchangeServer}
WhenChanged                             : 8/2/2007 4:43:47 PM
WhenCreated                             : 6/19/2007 3:10:42 PM

Question by:aiscom
  • 2
LVL 11

Accepted Solution

Zenith63 earned 2000 total points
ID: 19672592
This seems to be a bit of an issue with Exchange 2007, I've come across it in some shape or form on every 2007 site I've setup.  The problem seems to be there are numerous places where you can set limits, and limits don't inherit or override as you'd expect.

This is what I wrote down before when trying to solve this exact problem you're having with an A0 scanner, it did work in the end.

get-receiveconnector | select identity,maxmessagesize
to get the current maximum message sizes for each Receive Connector.

Then run for example
set-receiveconnector "Connector Name" -maxmessagesize 50MB

Also run
get-sendconnector | select identity,maxmessagesize
then the following to set it
Set-SendConnector "Default SMTP Connector" -maxmessagesize 100MB

You may also need to use something like the commands below to override the "unlimited" setting because the unlimited setting may get overridden by inheritance from something higher.  These commands set it to 100MB.
Set-TransportConfig -MaxSendSize 104857600
Set-TransportConfig -MaxReceiveSize 104857600

Unfortunately you may also alternatively need to do it at the mailbox level as well (I did in the case of the A0 scanner).  Use the following command to get the sizes for all mailboxes.
Get-Mailbox | select identity,maxsendsize
Get-Mailbox | select identity,maxreceivesize

Then use the following example to set the size to 100MB
Set-Mailbox -identity "username" -maxsendsize 104857600
Set-Mailbox -identity "username" -maxreceivesize 104857600
(replace username with the user's username and run for every user)

Hope that's of some use.  I'm keeping my fingers crossed for improved GUI control of these settings with SP1.
LVL 11

Expert Comment

ID: 19712598
I guess this sorted it out for you?  Which commands did you have to use in the end?

Author Comment

ID: 19718879
Yes, it worked out great.

I believe it was the get and send connectors I had to update if I remember correctly.


Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

Question has a verified solution.

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

Are you looking for the options available for exporting EDB files to PST? You may be confused as they are different in different Exchange versions. Here, I will discuss some options available.
Here in this article, you will get a step by step guidance on how to restore an Exchange database to a recovery database. Get a brief on Recovery Database and how it can be used to restore Exchange database in this section!
This video shows how to use Hyena, from SystemTools Software, to update 100 user accounts from an external text file. View in 1080p for best video quality.
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Suggested Courses

850 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