RE: [IMail Forum] Maximum size email

[Matrosity Hosting]

Seems like this really needs to be fixed as another potential problem. In the meantime, what should be entered into 2006.1 since it looks like the MB option doesn't take? Bill Foresman Matrosity Hosting www.matrosity.com 850.656.2644   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Sent: Friday, November 03, 2006 8:51 PM To: Imail_Forum@list.ipswitch.com Subject: Re: [IMail Forum] Maximum size email Ipswitch needs to fix their RFC 1870 issues.  Their documentation has stated that they are compliant with this since version 4 or 5, but there is almost no support for this, and it certainly is completely ineffective since all other servers rely on the recipient server to reject or accept based on the size of the message. I have been asking Ipswitch to fix this for a year and a half, along with several others that I work with and also experience this issue  This is the main cause of messages getting stuck in Outlook's outbox when sending an oversized message to IMail.  This is also the main cause of outgoing messages in IMail getting stuck retrying over and over again.  All of my IMail customers have experienced this, some more than others.  The lower the max E-mail size on either your server or the recipient server, the more frequently you will experience this issue. True and functional RFC 1870 support is where in EHLO connections, the size of the message in bytes is sent as an argument following the Mail >From address.  The recipient server then can take immediate action to accept or reject the message based on the size, and before a single bit of DATA is sent.  IMail doesn't listen to the Size value nor does it send using it.  This is further complicated by the fact that several servers, including Microsoft Exchange, Microsoft SMTP, and SmarterMail do not communicate oversized messages in a way that IMail understands (they send back the 550 as soon as the message goes oversize instead of waiting for the end of the DATA to stop, and IMail only understands a 550 after the end of DATA).  E-mail clients like Outlook, Outlook Express and Entourage have similar issues when sending which is why messages get stuck in their Outbox and sent continually. This not only causes messages to get stuck for long periods of time in a resending pattern, it also sucks up a ton of bandwidth.  I have had this completely suck up all of a customer's bandwidth on the end of a T1 with just a few messages stuck, and of course bandwidth costs us money, so this requires constant monitoring. Here are two charts showing a single message being stuck.  The first example is one stuck in an Outlook outbox, and the second is a message stuck in IMail's spool trying to be delivered to an Exchange server.  Both messages were approximately 25 MB.  Both charts start while the problem is already there and then the issue is fixed showing normal traffic.