On 08/26/2004 10:03:59 PM, Larry Osterman wrote:
That's highly unlikely given how the Exchange 2000 store treats MIME
messages.

Was the message in question a pure MIME message (in other words did it come from an SMTP client) or did it originate with an Outlook (MAPI) client?


I see there headers:
Received: from xxx ([yyy]) by zzzz with Microsoft SMTPSVC
        (5.0.2195.5329); Mon, 23 Aug 2004 16:09:23 +0100
Received: from [vvv] (Not Verified[uuu]) by xxx with
        NetIQ MailMarshal (v5.5.6.7) id <B0000a8cc7>;
        Mon, 23 Aug 2004 16:09:22 +0100
X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2)

Is it enough to answer your question? I see NetIQ MailMarshal is available in both SMTP and "for Exchange" variants.


Pawel

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Pete Maclean
Sent: Wednesday, August 25, 2004 8:20 AM
To: Pawel Salek; [EMAIL PROTECTED]
Subject: Re: strange response to message part fetch command


At 04:30 AM 8/25/2004, Pawel Salek wrote:
>Hi,
>
I encountered a strange response to message part fetch command. It looks like a bug in the server to me but I would like to get a second opinion. Suggestions how to work around this problem are welcome too. The problem is the server promises to send 23824 octects long literal but sends 4040+ characters and happily announces the processing has finished (sanitized log below). Any clues?

Could it be that the server is counting 23824 as the size of the body part prior to base64 encoding? Encoding 23824 octets in base64 would typically result in slightly less than 4040 characters but it depends of course on the line length used. It would be a bad bug but, in a sense, an understandable one.


Pete Maclean





Reply via email to