Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

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

Unable to send mail with attachments larger than 2 Mb

I am running SBS 2003 with Exchange Server 2003 built-in. I have read the MS KB article at http://support.microsoft.com/kb/322679 and so I have checked every possible place in Exchange where a mail size limit can be set and I have no limits anywhere. I am sending mail to an external test account which has a statuatory mail limit of 3.5 Mb. I have just checked with my business broadband provider and they have a mail limit of 50 Mb so as far as I can see there should be no problems.

The test attachment I am sending is a 2.5 Mb Autocad drawing file and when sending it I receive the standard delivery failure notification message

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 smtp;450 5.2.3 Msg Size greater than allowed by Remote Host>

If I send a message with a 1.9 Mb attachment it goes no problem and when I look at the external mail account it shows the total size of the message as 2665K.

Any ideas? Is there a hidden limit on attachment sizes somewhere? I have a firewall but as far as I can see it is not set to block attachments of any kind or size.

Rob
0
robspot
Asked:
robspot
  • 3
  • 2
1 Solution
 
jjoseph_xCommented:
I think that the key is "allowed by REMOTE host".   The problem is the receiving mail server, which means that nothing that you configure on your will change that.

When a binary attachment is encoded into a UUencode or, more commonly, base64 mime format it grows in size due to the overhead of the encoding (because you're taking a binary file and sending it in a 7-bit text format).  So your 2.5MB autocard drawing might well end-up growing to more than 3.5MB when it's base64 encoded.

Autocard drawings are pretty compressible though, so you could just zip it and send it.
0
 
robspotAuthor Commented:
I've tried sending it as a zip file of 2.28 Mb but it still won't go. Does that file size increase as well?

I know that the remote host bit indicates that it's a problem at the receivers end but the reason this came about is because one of my workers is having trouble sending drawings to someone (in another company) who swears that there are no mail restrictions at their end. It does seem that they may be fibbing doesn't it.
0
 
jjoseph_xCommented:
Any binary (including zips) that you send will increase in size (though I couldn't say by how much... it depends on the file).  And yeah, since the message is coming from their server they are definately limited the attachment size in either their 'mail' mail server or on their SMTP gateway (if any).

One possible solution would be to break the file into multiple, smaller parts.   Usually I use rar for that and I'd set the max size of each part to something like 1mb.

0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
robspotAuthor Commented:
Thanks for your help but that wasn't the answer.

It turns out that the delivery failure message was coming from MY server and was being generated because the mail was blocked by my firewall. There was a 3 Mb limit on the incoming SMTP proxy which for some reason was limiting the size of outgoing message. I increased the limit to 10 Mb and now the mail goes no problem.
0
 
ahrimannCommented:
pardon me for beating this dead horse, but robspot did you find the 3mb limit in your front-end exchange server? or are you running a different proxy? and also, was the firewall a separate firewall, or part of the proxy? i am having the identical problem.

thanx
0
 
robspotAuthor Commented:
Hi ahrimann

I have a Watchguard hardware firewall and it was on the SMTP proxy setting for this unit that the 3MB limit appeared. There are limits set in various places on Exchange but nonoe of these were set restrictively on my server. If you haven't already you might want to check the following locations

Open Exchange system manager and go to the connectors folder. right-click SMTP connector and go to properties. See if the allowed sizes box is checked.

Still in exchange system manager go to the Global Settings folder and right-click Message Delivery and go to properties. Click the default tab and check the incoming and outgoing sizes.

Apart from that I'm afraid I can't help you any further. Good luck.
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

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.

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