Re: [ietf-822] utf8 messages

Jan Kundrát <jkt@flaska.net> Tue, 12 August 2014 16:08 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 DF6F71A00E7 for <ietf-822@ietfa.amsl.com>; Tue, 12 Aug 2014 09:08:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.268
X-Spam-Level:
X-Spam-Status: No, score=-2.268 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, 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 wrKajIAPIj0a for <ietf-822@ietfa.amsl.com>; Tue, 12 Aug 2014 09:08:46 -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 A35D41A00E6 for <ietf-822@ietf.org>; Tue, 12 Aug 2014 09:08:45 -0700 (PDT)
Received: by latimerie.flaska.net (Postfix, from userid 1000) id C007A61694; Tue, 12 Aug 2014 18:08:41 +0200 (CEST)
From: Jan Kundrát <jkt@flaska.net>
To: ietf-822@ietf.org
Date: Tue, 12 Aug 2014 18:08:36 +0200
User-Agent: Trojita/v0.4.1-316-g6c81ae2; Qt/4.8.5; X11; Linux;
MIME-Version: 1.0
Message-ID: <d0fa552b-f118-49e3-a04d-900bad7fa9bc@flaska.net>
In-Reply-To: <01PBABOOL4QO0000SM@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>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-822/CDquje5x7ARzbBk_AT_ipasDSf4
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: Tue, 12 Aug 2014 16:08:48 -0000

On Tuesday, 12 August 2014 16:54:30 CEST, Ned Freed wrote:
>> Or are you saying it would be fine for us to have such a 
>> header, but not to
>> leak it?
>
> It's one thing to manifest such a marker in your IMAP store as 
> a header. People
> have been exposing various sorts of store metadata that way for 
> years, and it
> seems to have been Mostly Harmless.

I'm afraid that once these headers show up in GMail, these will become a 
de-facto standard.

I don't have a horse in this race -- but I have seen what happens when a 
major player does something non-standard and people assume that it must've 
been the correct thing.

With kind regards,
Jan

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