Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

SBS 2011 (Exchange 2010) Large Attachments Not Being Delivered

Posted on 2012-03-15
17
Medium Priority
?
1,933 Views
Last Modified: 2012-07-14
I recently upgraded from SBS 2003 to SBS 2011.  Pretty much all is well.  Running Exchange 2010 SP1 (plan on upgrading to SP2 this weekend).  However, external e-mails with larger r attachments somewhere around 7MB and up don't get delivered to mailboxes on our Exchange server.  24 to 48 hours later the sender gets a non-delivery report with either an smtp timeout or smtp read error listed.  Our incoming e-mail is filtered via Postini, but never had trouble like this before.  I think I have all of the limit size options disabled in Exchange 2010.  Any suggestions?
0
Comment
Question by:sswlewnix
[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
17 Comments
 
LVL 77

Expert Comment

by:Rob Williams
ID: 37727934
The default for send/receive is 10MB on SBS 2011, however depending on the attachment type that may limit you to about 7MB.  Please see the following link to make the necessary adjustments.
http://blog.lan-tech.ca/2011/10/27/quickie-changing-message-size-limits-on-sbs-std-2008-and-2011/
0
 
LVL 7

Expert Comment

by:withtu
ID: 37728128
There are different places you can do so, and the limit in SBS2011 is 10MB by default. That's not a problem but a by-design, you can change it though. Follow the SBS offical Blog article to change the value you want to:

http://blogs.technet.com/b/sbs/archive/2008/10/28/how-do-i-change-message-size-limits-in-exchange-2007.aspx
0
 
LVL 6

Expert Comment

by:jennylembert
ID: 37728603
As mentioned by Rob, the default limit is 10MB. If it is being restricted by the type of attachment you have, then you can increase it to 25 MB. Just add the following lines to your Exchange Management Shell and replace the Server Name with your SBS server.  

Set-TransportConfig –MaxSendSize 25MB –MaxReceiveSize 25MB
Set-ReceiveConnector “Windows SBS Internet Receive ServerName” –MaxMessageSize 25MB
Set-SendConnector “Windows SBS Internet Send ServerName” –MaxMessageSize 25MB

Hope this helps.
0
Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

 

Author Comment

by:sswlewnix
ID: 37731107
I checked all of my MaxSize settings and they are either unlimited, 50MB or 100MB.  Still not delivering 8MB - 9 MB file that I test sent from an outside account.  Any other ideas?
0
 
LVL 77

Expert Comment

by:Rob Williams
ID: 37731141
Many mail servce providers will limit message sizes to 6-10MB. It could be a 3rd party, but I agree iI have not known Postini to do so.

Could you possibly provide us with the content of one of the NDR's.  Headers might also be useful.
0
 

Author Comment

by:sswlewnix
ID: 37736286
Below is the body of the NDR; below that is the header information.  Any other ideas??

This Message was undeliverable due to the following reason:

Your message was not delivered because the destination computer was
not reachable within the allowed queue period.  The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.

Most likely there is a network problem that prevented delivery, but
it is also possible that the computer is turned off, or does not
have a mail system running right now.

Your message was not delivered within 1 days and 0 hours.
Host sswce.com is not responding.

The following recipients did not receive this message:

     <lnix@sswce.com>

The following attachments have been removed from the bounce message: Max Lucado - Your Are Special.mp3

****Headers start here****

Return-Path: <>
To: lewandkarah@charter.net
From: Mail Administrator
Subject: Mail System Error - Returned Mail
Reply-To: <Postmaster@charter.net>
Date: Sun, 18 Mar 2012 11:53:59 -0400
Message-ID: <20120318155358.UWUW6744.que21.charter.net@que21>
MIME-Version: 1.0
Content-Type: multipart/report;
            report-type=delivery-status;
            Boundary="===========================_ _= 6472473(6744)1332086038"


--===========================_ _= 6472473(6744)1332086038
Content-Type: text/plain

This Message was undeliverable due to the following reason:

Your message was not delivered because the destination computer was
not reachable within the allowed queue period.  The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.

Most likely there is a network problem that prevented delivery, but
it is also possible that the computer is turned off, or does not
have a mail system running right now.

Your message was not delivered within 1 days and 0 hours.
Host sswce.com is not responding.

The following recipients did not receive this message:

     <lnix@sswce.com>  The following attachments have been removed from the bounce message: Max Lucado - Your Are Special.mp3

--===========================_ _= 6472473(6744)1332086038
Content-Type: message/delivery-status

Reporting-MTA: dns; que21.charter.net
Arrival-Date: Sat, 17 Mar 2012 00:01:04 -0400
Received-From-MTA: dns; imp11 (10.20.200.11)

Final-Recipient: RFC822; <lnix@sswce.com>
Action: failed
Status: 4.4.7
Remote-MTA: dns; sswce.com
Diagnostic-Code: smtp; 250 Ok

--===========================_ _= 6472473(6744)1332086038
Content-Type: message/rfc822

Received: from imp11 ([10.20.200.11]) by mta11.charter.net
          (InterMail vM.8.01.05.02 201-2260-151-103-20110920) with ESMTP
          id <20120317040103.JEFS4059.mta11.charter.net@imp11>
          for <lnix@sswce.com>; Sat, 17 Mar 2012 00:01:03 -0400
Received: from TheNixFamilyPC ([75.143.67.122])
      by imp11 with smtp.charter.net
      id mU0W1i0082eGX5n05U0chp; Sat, 17 Mar 2012 00:01:03 -0400
X-Authority-Analysis: v=1.1 cv=rvNqJbVGdbt4egs52VbhtoJZG7AoPDG9H2iogr/sNfs=
 c=1 sm=1 a=yUnIBFQkZM0A:10 a=0sx+WFSDvadwZMzVTc7pcQ==:17
 a=YKGA95acHsSBVr7DufkA:9 a=wPNLvfGTeEIA:10 a=2tTXS9bGWPwFxbxjzFgA:9
 a=5zZJpWkY4ExBLtJlPqIA:7 a=_W_S_7VecoQA:10 a=eBg3fnfaVVse_G7LYJcA:9
 a=0sx+WFSDvadwZMzVTc7pcQ==:117
Message-ID: <314564D900364670BCEDC1CBBB66F50E@TheNixFamilyPC>
From: "Lew & Karah Nix" <lewandkarah@charter.net>
To: "Lew \(at work\)" <lnix@sswce.com>
Subject: testing large attachment
Date: Fri, 16 Mar 2012 23:00:29 -0500
MIME-Version: 1.0
Content-Type: multipart/mixed;
      boundary="----=_NextPart_000_015B_01CD03C8.95439830"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6002.18197
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18463

This is a multi-part message in MIME format.

------=_NextPart_000_015B_01CD03C8.95439830
Content-Type: multipart/alternative;
      boundary="----=_NextPart_001_015C_01CD03C8.9543BF40"


------=_NextPart_001_015C_01CD03C8.9543BF40
Content-Type: text/plain;
      charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

testing large attachment
------=_NextPart_001_015C_01CD03C8.9543BF40
Content-Type: text/html;
      charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 9.00.8112.16441">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2 face=3DArial>testing large =
attachment</FONT></DIV></BODY></HTML>

------=_NextPart_001_015C_01CD03C8.9543BF40--

------=_NextPart_000_015B_01CD03C8.95439830--

--===========================_ _= 6472473(6744)1332086038--
0
 
LVL 77

Expert Comment

by:Rob Williams
ID: 37736304
What makes you think this error is due to the attachment size?  This is not a typical NDR for a message bouced by Exchange due to message size limits. The message will state that specifically such as "#5.5.0 smtp;552 Error: message too large"
0
 

Author Comment

by:sswlewnix
ID: 37737555
That is exactly what I am trying to determine.  I don't think the problem is related to a message size issue as I have my message size parameters set pretty high.  I think it is due to some kind of SMTP timeout.  If I send a smaller attachment  (3MB to 5MB), it comes through fine.  Any suggestions on how to troubleshoot for timeouts and their causes?
0
 
LVL 77

Expert Comment

by:Rob Williams
ID: 37737670
Where you have a "middle man" Postini it is difficult to determine where it is being blocked.  Postini allows messages up to 200MB by default so it shouldn't be the problem, but they do have filters that you can enable.  Is there any chance this has been configured.

It's also possible the site from which you are sending it is blocking it, such as an ISP or local server.  Though 3MB should not be a problem, a 3MB message dues to file types, compression, and overhead can actually be 5MB which can be blocked by many system.

I would try sending from another site and try an attachment other than an .mp3, preferably a .doc or business type file.
0
 

Author Comment

by:sswlewnix
ID: 37738614
I tried an 8MB PDF today from another domain.  Actually another SBS 2011 server that I maintain.  Never received it.  Sent a plain text e-mail from same domain and an e-mail with a 3MB jpg.  Received both of them.  The 3MB did take about 15 minutes to arrive.  Seems to be something about the size taking too long to be delivered.  I won't get the NDR for the 8MB PDF for at least 24 hours to see what the NDR says.  Is there anything I can do on my SBS 2011 SMTP server from a logging perspective to see what is happening?
0
 
LVL 77

Expert Comment

by:Rob Williams
ID: 37738637
There won't be anything logged on the server if it is not received.
What is interesting about the NDR is it doesn't indicate where it was rejected, postini or the SBS. My hunch is it is not the SBS.  It is very odd.
There are test tools, but the domain doesn't resolve to the SBS, but rather postini.

If it were my site, I would take postini out of the picture by changing the public DNS records and have them point to the SBS itself for testing.  However I do appricate that can take up to 48 hours to propogate and although there should be no interuption in services, there could be.
0
 

Author Comment

by:sswlewnix
ID: 37738649
What could I check on my server via logging just to see if an SMTP connection ever is made to attempt to receive this specific email?
0
 
LVL 77

Expert Comment

by:Rob Williams
ID: 37738674
0
 

Accepted Solution

by:
sswlewnix earned 0 total points
ID: 37742224
OK...I think I solved the problem after talking with my Postini support.  They recommended increasing the connectiontimeout parameter on the ReceiveConnector.  The default was 10 minutes.  I increased this to 30 minutes and the e-mails that I had sent testing earlier in the day were delivered within the next 20 - 30 minutes.  I am still concerned that I have a lag issue or some other kind of setting issue on this new SBS 2011 server.  Should it really take 20 to 30 minutes to receive a 9MB attachment?  I don't know what this parameter was set to on our old SBS 2003 server.  Just wanting to make sure that I have our SBS 2011 server running optimally.
0
 
LVL 77

Expert Comment

by:Rob Williams
ID: 37742278
I was goj=ng to suggest it is highly unlikly it is the SBS itself, but apparently many others have had similar issues.

Are you using the POP connector or having the mail delivered directly?

Is there any chance power management is enabled on the network adapter?
0
 

Author Comment

by:sswlewnix
ID: 37742320
I am not using a POP connector.  Mail is delivered directly.  

I just check and the adapter did have power management turned on.  I turned it off.  Didn't request a restart/reboot, so I assume the change applies immediately.  I will test later today when I have time to see how long it takes to receive the same file.
0
 

Author Closing Comment

by:sswlewnix
ID: 38185439
None of the responses I got on EE mentioned connectiontimeout as a possible problem.  Everyone was suggesting message size restrictions.  I found this connectiontimeout parameter via google searches, etc.
0

Featured Post

Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

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 …
If you troubleshoot Outlook for clients, you may want to know a bit more about the OST file before doing your next job. IMAP can cause a lot of drama if removed in the accounts without backing up.
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…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

721 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