Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.
Course Of The Month
Become a Premium Member and unlock a new, free course in leading technologies each month.
Solved
SBS Server 2000 SP4 Exchange Problem Setting Max Incoming Email Size.
Posted on 2006-07-07
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: <3a502f570607030029h7de0e9
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: <3a502f570607030025k3d7885
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_13127
References: <3a502f570607030025k3d7885
------=_Part_13127_1774695
Content-Type: multipart/alternative;
boundary="----=_Part_13128
------=_Part_13128_7734654
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding:
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
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: <3a502f570607030029h7de0e9
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: <3a502f570607030025k3d7885
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_13127
References: <3a502f570607030025k3d7885
------=_Part_13127_1774695
Content-Type: multipart/alternative;
boundary="----=_Part_13128
------=_Part_13128_7734654
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding:
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
[X]
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
4 Comments
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.
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.
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.
Simon.
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.
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.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Unified and professional email signatures help maintain a consistent company brand image to the outside world. This article shows how to create an email signature in Exchange Server 2010 using a transport rule and how to overcome native limitations …
This article will help to fix the below error for MS Exchange server 2010
I. Out Of office not working
II. Certificate error "name on the security certificate is invalid or does not match the name of the site"
III. Make Internal URLs and External…
To show how to create a transport rule 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 Mail Flow >> Rules tab.: To cr…
how to add IIS SMTP to handle application/Scanner relays into office 365.
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month6 days, 4 hours left to enroll
Earn Certification
MTA Server Fundamentals Exam 98-365
$59.00$53.10
626 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.