Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 216
  • Last Modified:

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

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 msexchange.org 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:
   xxx@company.com
  ----- Original message -----
Received: by xx.xx.xxx.xx with SMTP id n17mr2228656hud;
       Mon, 03 Jul 2006 00:29:42 -0700 (PDT)
Received: by xx.xx.xxx.xx with HTTP; Mon, 3 Jul 2006 00:29:40 -0700 (PDT)
Message-ID: <3a502f570607030029h7de0e94s6f8048ea97a5bb60@mail.gmail.com>
Date: Mon, 3 Jul 2006 17:29:40 +1000
From: "xxxx@gmail.com" <xxxx@gmail.com>
To: xxx@company.com
Subject: Fwd: 7meg pdf documents
In-Reply-To: <3a502f570607030025k3d788526t5b9f130dc8b1f39e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
       boundary="----=_Part_13127_17746955.1151911780398"
References: <3a502f570607030025k3d788526t5b9f130dc8b1f39e@mail.gmail.com>
------=_Part_13127_17746955.1151911780398
Content-Type: multipart/alternative;
       boundary="----=_Part_13128_7734654.1151911780398"
------=_Part_13128_7734654.1151911780398
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:
http://www.msexchange.org/tutorials/Set-Size-Limits-Messages.html

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,
Broad
0
BroadAustralia
Asked:
BroadAustralia
  • 2
  • 2
1 Solution
 
BroadAustraliaAuthor Commented:
I also notice that the message received in the NDR is different to the message MS describe in their article ( http://support.microsoft.com/default.aspx?scid=kb;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.
<server.domain.com #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?

Broad.
0
 
SembeeCommented:
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.

Simon.
0
 
BroadAustraliaAuthor Commented:
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? )

Thankyou,

Broad.
0
 
SembeeCommented:
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.

Simon.
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

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

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