On 14/6/03 8:54, "Scott Haneda" <[EMAIL PROTECTED]> wrote:
> on 06/12/2003 04:22 PM, Barry Wainwright at [EMAIL PROTECTED] wrote:
>
>>
>> This is an occasionally reported problem, and every issue followed to date
>> has
>> concluded with evidence that the user�s ISP�s mail server has incorrectly
>> handled the message and truncated it.
>>
>> If you see the problem when the period is at around the 72nd character (I
>> forget the exact number, but it is somewhere between 70 & 76), this is almost
>> certainly what you are seeing.
>>
>> If you want, I will willingly co-operate in some tests with you. Contact me
>> offlist if you want to.
>
> I must admit, I hate the fact that I even know about this, but it is the
> 76th character, RFC 1521 has all the gross details on it. In general, it has
> to do with quoted printable emails. I would have to say the chances of a
> email server munging the data is probably the wrong place to be looking.
> Most mta's simply pass the message along, whereas the client is what is
> probably doing the munging. In this case when I say client, I mean the
> sending client, not the recipient. The Quoted-Printable encoding REQUIRES
> that encoded lines be no more than 76 characters long. If longer lines are
> to be encoded with the Quoted-Printable encoding, 'soft' line breaks must be
> used. An equal sign as the last character on a encoded line indicates such a
> non-significant ('soft') line break in the encoded text. I have found
> entourage to always parse quoted printable just fine, and even go beyond
> that and encode and decode high ASCII as well, which is not part of the RFC
> spec. Since entourage favors curly quotes and such, I guess that is why it
> does this and does it well. Makes it harder to parse out quoted printable
> coming from Entourage, but I have gotten used to it. At any rate, look at
> where the message came from, not the ISP's server, I think you will find
> that there is a bug in their software, and I would almost put money on it
> being that one email app, QuickMail Pro, which is almost always in violation
> of RFC in one way or another. I have also seen Eudora do some really
> strange stuff as well, again, not a Entourage issue, but the other clients
> issue.
>
The problem I refer to happens when the last period is wrapped to a line on
it's own. A line on it's own should indicate to the SMTP server that the
message is at an end, and entourage prevents this from happening by
converting that one period to a double period (this can be checked by
watching the tcp stream using tcpFlow). Unfortunately, a very few mail
servers out there incorrectly accept the double period as a message
terminator as well as the single period ( I suspect they actually just look
for a period at the start of a line). This causes the message to be
truncated at the wrapped period.
As I stated, in every case reported that has been investigated thoroughly it
has turned out to be an SMTP server exhibiting this bug.
--
Barry
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
archives: <http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/>
old-archive: <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
