Re: [ietf-822] utf8 messages

Ned Freed <ned.freed@mrochek.com> Wed, 13 August 2014 00:24 UTC

Return-Path: <ned.freed@mrochek.com>
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 419441A0A8B for <ietf-822@ietfa.amsl.com>; Tue, 12 Aug 2014 17:24:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.27
X-Spam-Level:
X-Spam-Status: No, score=-2.27 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.668, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 S6aF0QzNJnGo for <ietf-822@ietfa.amsl.com>; Tue, 12 Aug 2014 17:24:27 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 87A6E1A0AD4 for <ietf-822@ietf.org>; Tue, 12 Aug 2014 17:24:27 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01PBAUI082WG0015IH@mauve.mrochek.com> for ietf-822@ietf.org; Tue, 12 Aug 2014 17:19:25 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: TEXT/PLAIN; CHARSET="US-ASCII"; Format="flowed"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01PBAUCMQVN40000XX@mauve.mrochek.com>; Tue, 12 Aug 2014 17:19:23 -0700 (PDT)
Message-id: <01PBAUHYSGNA0000XX@mauve.mrochek.com>
Date: Tue, 12 Aug 2014 17:16:56 -0700
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Tue, 12 Aug 2014 18:08:36 +0200" <d0fa552b-f118-49e3-a04d-900bad7fa9bc@flaska.net>
References: <CABa8R6tWEhjjZSvq6NbM7EimokOms3suZufn0-6N1SB_fzGM8Q@mail.gmail.com> <01PB9FABWA4E0000SM@mauve.mrochek.com> <CABa8R6tns-idiZTj=+vb9fVNyH-nNYT+w9oNMb80XbCs5osvFw@mail.gmail.com> <01PBABOOL4QO0000SM@mauve.mrochek.com> <d0fa552b-f118-49e3-a04d-900bad7fa9bc@flaska.net>
To: Jan Kundrát <jkt@flaska.net>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-822/dx28lHB2wk_Yl5YG-I3LkLrxPvg
Cc: ietf-822@ietf.org
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: Wed, 13 Aug 2014 00:24:29 -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.

Good point. Consider my position changed to "don't do this, period".

As for the with clauses, they provide a "solution" for mail that undergoes
final delivery, but not for IMAP APPEND.

				Ned