Re: [ietf-822] utf8 messages

Jan Kundrát <jkt@flaska.net> Fri, 15 August 2014 11:27 UTC

Return-Path: <jkt@flaska.net>
X-Original-To: ietf-822@ietfa.amsl.com
Delivered-To: ietf-822@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C972F1A8A50 for <ietf-822@ietfa.amsl.com>; Fri, 15 Aug 2014 04:27:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.267
X-Spam-Level:
X-Spam-Status: No, score=-2.267 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, MIME_QP_LONG_LINE=0.001, RP_MATCHES_RCVD=-0.668] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y-e1QJGb39Nw for <ietf-822@ietfa.amsl.com>; Fri, 15 Aug 2014 04:27:15 -0700 (PDT)
Received: from latimerie.flaska.net (latimerie.flaska.net [IPv6:2a02:2b88:2:1::4a7:333]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C6CC1A8A51 for <ietf-822@ietf.org>; Fri, 15 Aug 2014 04:27:15 -0700 (PDT)
Received: by latimerie.flaska.net (Postfix, from userid 1000) id 4773461676; Fri, 15 Aug 2014 13:27:12 +0200 (CEST)
From: Jan Kundrát <jkt@flaska.net>
To: ietf-822@ietf.org
Date: Fri, 15 Aug 2014 13:27:08 +0200
User-Agent: Trojita/v0.4.1-316-g6c81ae2; Qt/4.8.5; X11; Linux;
MIME-Version: 1.0
Message-ID: <d00d0474-d28c-4d05-b42d-79e22913d61b@flaska.net>
In-Reply-To: <01PBDQ3P6A8Q0000SM@mauve.mrochek.com>
References: <CABa8R6tWEhjjZSvq6NbM7EimokOms3suZufn0-6N1SB_fzGM8Q@mail.gmail.com> <01PB9FABWA4E0000SM@mauve.mrochek.com> <CABa8R6tns-idiZTj=+vb9fVNyH-nNYT+w9oNMb80XbCs5osvFw@mail.gmail.com> <01PBABOOL4QO0000SM@mauve.mrochek.com> <CABa8R6vBqS1ewmTtHh8tTOdzobsWpvSEokRxOqpj1Oq3hA+vsw@mail.gmail.com> <01PBBWUH11D60000SM@mauve.mrochek.com> <CABa8R6uJ--4Fcntdgef+h6ZXjP_q0q7hZaBW-SOozMTtiE918g@mail.gmail.com> <01PBCGZERCU20000SM@mauve.mrochek.com> <CABa8R6sbFQHaP=YgrejJjUKJS+20BFP+kATZ+PrDnTgUhPMpHw@mail.gmail.com> <01PBDQ3P6A8Q0000SM@mauve.mrochek.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-822/K6ZfpKBbeWM8XUU3LXuS1lG1ves
Subject: Re: [ietf-822] utf8 messages
X-BeenThere: ietf-822@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of issues related to Internet Message Format \[RFC 822, RFC 2822, RFC 5322\]" <ietf-822.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-822/>
List-Post: <mailto:ietf-822@ietf.org>
List-Help: <mailto:ietf-822-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Aug 2014 11:27:18 -0000

My understanding is that Brandon's system previously required no 
out-of-band label at all. Whenever a message was processed in their 
infrastructure, they would use a single algorithm, and that algorithm 
contained some heuristic for dealing with messages which were using 8bit 
data in headers. Everything worked pretty well for them.

Now, the EAI introduced another syntax, and that syntax breaks their 
heuristics. Ned's suggestion is to make use of the out-of-band labeling and 
extend the heuristic to only apply the old crutches when the label says 
that this isn't an EAI message, while Brandon's complaint is that they use 
no such labeling at this time because it isn't required at all. Brandon 
also suggests that there are many other places which process these messages 
without the external metadata.

By "out-of-band" or "external", I mean what gets set in the ESMTP envelope.

Hope this helps, and please correct me if my understanding of your 
positions is not correct.

>From my point of view, it would be most interesting to see what happens 
when I deploy e.g. a Postfix version which understands this new RFC along 
with an older Dovecot which doesn't do it. Suddenly, an IMAP client is in 
the same position as Brandon describes because there's no way of accessing 
the ESMTP envelope through IMAP.

Cheers,
Jan

-- 
Trojitá, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/