From: jeffrey.hundstad@mnsu•edu (Jeffrey Hundstad)
To: linux-arm-kernel@lists•infradead.org
Subject: Query: Patches break with Microsoft exchange server.
Date: Wed, 11 Aug 2010 11:16:50 -0500 [thread overview]
Message-ID: <4C62CCF2.5040206@mnsu.edu> (raw)
In-Reply-To: <1281542305.5107.11.camel@localhost>
On 08/11/2010 10:58 AM, David Woodhouse wrote:
> On Wed, 2010-08-11 at 10:46 -0500, Jeffrey Hundstad wrote:
>> Exchange 2010 does not handle IMAP "chunking" (partial message transfer)
>> correctly. Any request after about 1 megabyte of total message size
>> will fail.
>>
>> Thunderbird uses this "chunking" feature to give you a status update
>> while downloading large messages. The IMAP statements are of this type:
>> 11 UID fetch 244477 (UID RFC822.SIZE BODY[]<20480.12288>)
>>
>> When the 20480 is larger than 1MB Exchange "claims" there is no more.
>> Sigh....
>
> I think the problem is not with the fetching -- the problem is that
> Exchange lies about RFC822.SIZE before the IMAP client even starts to
> fetch the message. It reports a size which is smaller than the actual
> size of the message, thus leading to truncated fetches.
>
> In Evolution we have a workaround -- we don't just stop when we get to
> the reported RFC822.SIZE; we continue fetching more chunks until the
> server actually stops giving us any more. It's not as efficient (because
> we fall back to having only one more chunk outstanding at a time rather
> than the normal three in parallel), but at least it works around this
> brokenness of Exchange.
>
> http://git.gnome.org/browse/evolution-data-server/commit/?id=9714c064
>
In either case it can be used successfully by disabling
mail.server.default.fetch_by_chunks in Thunderbird.
--
Jeffrey Hundstad
next prev parent reply other threads:[~2010-08-11 16:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 20:23 Query: Patches break with Microsoft exchange server viresh kumar
2010-08-09 14:19 ` Richard Cochran
2010-08-10 22:04 ` Felipe Contreras
2010-08-11 7:01 ` viresh kumar
2010-08-11 15:46 ` Jeffrey Hundstad
2010-08-11 15:58 ` David Woodhouse
2010-08-11 16:16 ` Jeffrey Hundstad [this message]
2010-08-11 16:18 ` Avery Pennarun
2010-08-11 16:30 ` David Woodhouse
2010-08-11 16:39 ` Avery Pennarun
2010-08-12 4:41 ` viresh kumar
2010-08-16 0:32 ` Gururaja Hebbar K R
2018-06-19 20:24 ` Justin P. Mattock
2018-06-19 20:24 ` viresh kumar
2018-06-19 20:24 ` Justin P. Mattock
2018-06-19 20:24 ` Uwe Kleine-König
2018-06-19 20:24 ` viresh kumar
2018-06-19 20:26 ` Matti Aarnio
2018-06-19 20:26 ` viresh kumar
2010-08-10 9:22 ` Gadiyar, Anand
2010-08-10 9:26 ` viresh kumar
2018-06-19 20:26 ` Justin P. Mattock
2010-08-09 14:35 ` Mihai Donțu
2010-08-09 17:55 ` Justin P. Mattock
2010-08-09 18:15 ` Mihai Donțu
2010-08-09 18:53 ` Justin P. Mattock
2010-08-09 21:28 ` David Woodhouse
2010-08-09 21:56 ` Justin P. Mattock
2010-08-11 14:05 ` Geert Uytterhoeven
2018-06-19 20:26 ` David Woodhouse
2018-06-19 20:42 ` Willy Tarreau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C62CCF2.5040206@mnsu.edu \
--to=jeffrey.hundstad@mnsu$(echo .)edu \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox