linux-kernel - Re: Query: Patches break with Microsoft exchange server.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 11 Aug 2010 12:18:02 -0400
From:	Avery Pennarun <apenwarr@...il.com>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	Jeffrey Hundstad <jeffrey.hundstad@...u.edu>,
	viresh kumar <viresh.kumar@...com>,
	Felipe Contreras <felipe.contreras@...il.com>,
	"git@...r.kernel.org" <git@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Justin P. Mattock" <justinmattock@...il.com>,
	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>,
	Valeo de Vries <valeo@...eo.co.cc>,
	Linus Walleij <linus.ml.walleij@...il.com>,
	Matti Aarnio <matti.aarnio@...iler.org>, mihai.dontu@...il.com,
	richardcochran@...il.com, "Gadiyar, Anand" <gadiyar@...com>
Subject: Re: Query: Patches break with Microsoft exchange server.

On Wed, Aug 11, 2010 at 11:58 AM, David Woodhouse <dwmw2@...radead.org> wrote:
> 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

Out of curiosity, why fall back to one chunk at a time?  It seems to
me that IMAP should be able to still support multiple outstanding
requests in that case, but you'd just get errors on the latter chunks.

It is just that there was no point optimizing the workaround case?

Have fun,

Avery
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/