IETF Logo Mail Archive

Re: [ietf-822] Encoding (Re: p^_^X^_ Re: Fwd: New Version Notification for draft-crocker-inreply-react-00.txt)

Brandon Long <blong@google.com> Fri, 09 October 2020 06:25 UTC

Return-Path: <blong@google.com>
X-Original-To: ietf-822@ietfa.amsl.com
Delivered-To: ietf-822@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A99D3A09C6 for <ietf-822@ietfa.amsl.com>; Thu, 8 Oct 2020 23:25:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level:
X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 j0xMUNbEiHq9 for <ietf-822@ietfa.amsl.com>; Thu, 8 Oct 2020 23:25:23 -0700 (PDT)
Received: from mail-vk1-xa30.google.com (mail-vk1-xa30.google.com [IPv6:2607:f8b0:4864:20::a30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9059B3A09C4 for <ietf-822@ietf.org>; Thu, 8 Oct 2020 23:25:06 -0700 (PDT)
Received: by mail-vk1-xa30.google.com with SMTP id l23so837716vkm.1 for <ietf-822@ietf.org>; Thu, 08 Oct 2020 23:25:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6t89nIvxX5ehXZ3tFwoELRRpWc7ZslqQ8BVhe9BiN7s=; b=pWD4CxO+u/2jgWdrMTao6m2aaJD//Lplbtlf69DmiTvwMcAo5lciVIOWjHgBV+I/VO ynT/9hsvF+475H7ASFflkdAXhfUmLaMYCSaSBM9KfDAcxI+xTFFeD4JahrczKHJcLS0g FaAj6VlPKH1lv5N5m2N8aUcHXzjSBdwVYPly9iSCpHbPzEDUj+dypU46KI+L36b17OTI s6Zvn946o8BrMFgSLVEBYVvKgmRzHK6RgR0Jq1w6PHNa3gRzZYk1sRHn2mjebbZBi9MX i/MSz5MrufB1GpIzWCAdc8ZCTWjbwOxC5bPAPMQiTmhcK13zjrXshDO1V/QYNjAUZnsL PMyw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6t89nIvxX5ehXZ3tFwoELRRpWc7ZslqQ8BVhe9BiN7s=; b=ECb7BAQiQaYm4vfJsCJDiaAvjf6WjeUpALwM3OwXf+AgJAw0BDTSnjzjp/tDI+MZRk BbGnRjDvcy6QttUJCptV64tHk87LCQlsBqWwwOYsVIN8/rMrV80at27SpQSfCuVzsZWc mmh9uyJKNpz0q/OCSUFRp0DheL4KU7ksODsVlJoC0r80udyfVUxcmweH4oULZRdI3vbt afSbU/WbHZtLlrSq2ywfS1C02C18nrNbB6B7Af1ySUGB2enEm1e+aosrlP7N+SlRsEiH +BbESMWY7m0wsj4GU02JYpWHOkh/yTMsdccIQo7l4H4LIO6KkiLWPwUNyLespBXstTmX UCNA==
X-Gm-Message-State: AOAM5313ha53EhR8RVJ3f7m4SMufs/yw1hZz4ked/YbfiQWsaPdoRdgA q1jzDGfgRkS5mwgRxFdeLonGWgM+RNacdfDsJ1OC
X-Google-Smtp-Source: ABdhPJyc7HGFtPb/y8xXYTzduBZ6EOmyZyZgLiULol66v169E6DCFg3WfDX4V8gZB6VQB4TEejroBxtVXDRQTvbpOuI=
X-Received: by 2002:a1f:2450:: with SMTP id k77mr6629326vkk.13.1602224705186; Thu, 08 Oct 2020 23:25:05 -0700 (PDT)
MIME-Version: 1.0
References: <75046.1601954458@turing-police> <20201006150921.EB4CD2301332@ary.qy>
In-Reply-To: <20201006150921.EB4CD2301332@ary.qy>
From: Brandon Long <blong@google.com>
Date: Thu, 08 Oct 2020 23:24:52 -0700
Message-ID: <CABa8R6tL-HxJbAJKLLFQF0KGPtf2sWF5-vOpX1o9fov_AzmkgA@mail.gmail.com>
To: John Levine <johnl@taugh.com>
Cc: ietf-822@ietf.org, Valdis Kletnieks <valdis.kletnieks@vt.edu>
Content-Type: multipart/alternative; boundary="000000000000678f9705b1370280"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-822/LGINrfNTfwhj28h8ys4kOmCvYsQ>
Subject: Re: [ietf-822] Encoding (Re: p^_^X^_ Re: Fwd: New Version Notification for draft-crocker-inreply-react-00.txt)
X-BeenThere: ietf-822@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Oct 2020 06:25:25 -0000

On Tue, Oct 6, 2020 at 8:09 AM John Levine <johnl@taugh.com> wrote:

> In article <75046.1601954458@turing-police> you write:
> >Only if the entire path is sufficiently 8-bit clean. Somewhere between
> ietf.org's
> >mail server, google, and fetchmail to my laptop the emoji got smashed into
> >a lower case 'p' followed by a 0x1f181f, almost certainly due to something
> >not being totally 8-bit-clean.
>
> I would blame fetchmail which is not famous for high quality standards
> compliant code. Postfix and Gmail do not screw up MIME encodings,
> particularly since all they need to do to comply is nothing. I see you
> use exmh but you presumably know what your code does.
>
> >Anything along the line of "if you don't have an 8-bit clean path, you
> >need to use rfc2047 to encode the utf-8" is fine by me.
>
> Well, yes, that's been the rule for about three decades.
>

We could say that the field isn't encoded and only available for SMTPUTF8
as a forcing function... you want your emojis, step up.

I know, doesn't really work that way, we'd probably just get 5 different
non-standard ways of encoding it instead.

Brandon

v2.23.0 | Report a Bug | By Email