SBS Server 2000 SP4 Exchange Problem Setting Max Incoming Email Size.

Posted on 2006-07-07
Last Modified: 2010-03-06
Hi EE,

I have inherited a SBS 2000 Server.  I am not an Exchange expert so please bear with me. :)   I've run thru the tutorial but still large emails are rejected..

The users would like to recieve emails upto 10MB.  As a test I sent an email of approx 7MB in size to one of their accounts from my webmail service.

I got the following delivery failure message back days later:
This is an automatically generated Delivery Status Notification
Delivery to the following recipient failed permanently:
  ----- Original message -----
Received: by with SMTP id n17mr2228656hud;
       Mon, 03 Jul 2006 00:29:42 -0700 (PDT)
Received: by with HTTP; Mon, 3 Jul 2006 00:29:40 -0700 (PDT)
Message-ID: <>
Date: Mon, 3 Jul 2006 17:29:40 +1000
From: "" <>
Subject: Fwd: 7meg pdf documents
In-Reply-To: <>
MIME-Version: 1.0
Content-Type: multipart/mixed;
References: <>
Content-Type: multipart/alternative;
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
---------- Forwarded message ----------
  ----- Message truncated -----

Suffice to say, the message never arrive to the users inbox.

Have read and followed guidelines from here:

System was adhering to all:
- Global Setting - Message Delivery - Defaults Tab
Sending Message Size 10240  |  Receiving Message Size 102040

- Checked System Policies:
No limitations on mail box sizes.

- Active Directory Users - Properties of User - Delivery Restrictions Tab
- Set to Use Default Limit ( both Send & Receive ).   Tried setting this manually and resending message (after server reboot) - still fails.

- Check Virtual Server
Limit Message size set to 10240

As I am not too familiar with Exchange I also restarted the server after setting the users personal max message receive size to ensure it was taken on board.. PS. is this required?  Is there a command to run after any of these setting changes to "PUSH" it thru immediately?

Have tried every option that I know of ( ok which ain't much with exchange! ; ) .. Have I missed something?

PS. Just did internal send test -- this is unrestricted same size email went thru no problems at all.
Thanks for your help,
Question by:BroadAustralia
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
  • 2
  • 2

Author Comment

ID: 17063158
I also notice that the message received in the NDR is different to the message MS describe in their article (;en-us;322679 )

MS say to expect this when message exceeds incoming limits:
Subject: Test
Sent: 7/18/2002 2:40 PM
The following recipient(s) could not be reached:
Test Recipient on 7/18/2002 2:41 PM
This message is larger than the current system limit or the recipient's mailbox is full. Create a shorter message body or remove attachments and try sending it again.
< #5.2.3>

The server I am working on gives a NDR informing sender message was truncated... ( in original post ).  Not sure if this helps with diagnostic?

LVL 104

Accepted Solution

Sembee earned 500 total points
ID: 17204891
Do you get your email directly or via an ISP. Anything else scanning your email that could be causing problems? Antivirus, firewalls etc can all cause large emails to fail.


Author Comment

ID: 17212282
Hi Simon

Thanks for the reply..  Email is direct.. AntiVirus is running ( Symantec I am pretty sure.. )..  There is also a Watchguard Firewall in place.

Maybe first port of call is disable the AntiVirus and send a test thru?

If this still fails - maybe the firewall is the culprit?

How can I see in Exchange if the message got that far?  ( ie. was received at all by the Exchange server? )


LVL 104

Expert Comment

ID: 17215842
The message could have reached Exchange, and would show in any SMTP logs. But if something interferes with the traffic, then the connection will never complete.


Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

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

Read this checklist to learn more about the 15 things you should never include in an email signature.
A list of top three free exchange EDB viewers that helps the user to extract a mailbox from an unmounted .edb file and get a clear preview of all emails & other items with just a single click on mailboxes.
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
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…

734 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