MBOX-Line: From jkt at flaska.net  Fri Aug 17 08:30:55 2012
To: imap-protocol@u.washington.edu
From: =?UTF-8?B?SmFuIEt1bmRyw6F0?= <jkt@flaska.net>
Date: Fri Jun  8 12:34:48 2018
Subject: [Imap-protocol] BINARY + multiparts
In-Reply-To: <E7F9B601-2050-46A2-8A57-C945F3206026@orthanc.ca>
References: <283BA59D-2B55-4E29-BD2F-D3C392D2E673@iki.fi>
	<E7F9B601-2050-46A2-8A57-C945F3206026@orthanc.ca>
Message-ID: <502E63AF.60001@flaska.net>

On 08/11/12 17:43, Lyndon Nerenberg wrote:
> But I would strongly advise
> client authors to restrict binary fetches to terminal body parts, as
> the behaviour of fetching non-terminals is going to be
> unpredictable.

I have to admit that I've just discovered the errata process of the 
IETF's RFCs and it's a new shiny toy for me, so take this suggestion 
with a grain of salt, but as a client developer, I've missed this corner 
case when implementing BINARY in Trojita. Could we therefore get an 
errata containing this note?

With kind regards,
Jan

-- 
Trojita, a fast e-mail client -- http://trojita.flaska.net/

