29 lines
1.1 KiB
Plaintext
29 lines
1.1 KiB
Plaintext
MBOX-Line: From alh at warhound.org Tue Sep 27 11:00:47 2005
|
|
To: imap-protocol@u.washington.edu
|
|
From: Adrian Hosey <alh@warhound.org>
|
|
Date: Fri Jun 8 12:34:36 2018
|
|
Subject: [Imap-protocol] partial fetch
|
|
In-Reply-To: <3D9D02497026344DB100E7D18A6C06E3B5E1F5@nbexch01.neubond.com>
|
|
Message-ID: <Pine.LNX.4.44.0509271254160.14967-100000@amorphous.bloomington.in.us>
|
|
|
|
On Tue, 27 Sep 2005, Otto Leung wrote:
|
|
:
|
|
: The reason I asked is that the client software is having problems with
|
|
: partial fetch. It hangs when it tries to get an attachment that's
|
|
: bigger than the chunk size.
|
|
|
|
I have seen something very similar to this when the attachment has been
|
|
corrupted on disk by a crash. (Or anything else that would cause
|
|
corruption.) If the attachment contains a null byte, 8 zero bits, this can
|
|
mess up the octet count between client and server. Since null bytes are
|
|
never supposed to be written to an IMAP store, some IMAP programs assume
|
|
they will never get a null byte from a disk read and if they do they will
|
|
transmit the null byte over the wire, which is a BIG no-no.
|
|
|
|
So, are your attachments corrupt or do they contain null bytes?
|
|
|
|
--
|
|
I am disrespectful to dirt!
|
|
|
|
|