Re: [ietf-822] (no subject)

"John Levine" <johnl@taugh.com> Tue, 24 July 2018 04:13 UTC

Return-Path: <johnl@iecc.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 F23F5130FD7 for <ietf-822@ietfa.amsl.com>; Mon, 23 Jul 2018 21:13:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.751
X-Spam-Level:
X-Spam-Status: No, score=-1.751 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=bHiDcg7n; dkim=pass (1536-bit key) header.d=taugh.com header.b=ne21FIE6
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 yYS6UQjihXho for <ietf-822@ietfa.amsl.com>; Mon, 23 Jul 2018 21:13:19 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 7EA36130FD4 for <ietf-822@ietf.org>; Mon, 23 Jul 2018 21:13:19 -0700 (PDT)
Received: (qmail 97619 invoked from network); 24 Jul 2018 04:13:15 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=17d50.5b56a75b.k1807; bh=v6f5Klr+3DlKpUycKBEusmWLRJsD0gxqSQ8e2F23bk4=; b=bHiDcg7nMB9ulLI1xnHCXtVzDa726c+3xiH1OyzILLE1EhxqLuVD+r8UrIW3AberFmHe/qwpxj2kQZPjymagzup2qYvdroDdFyzEy/kYsh9ebNmjMFX6oZTGpALDR/vvlQCrFTxSWfCz+FqhSz78Lj7D8z91++Q9ob428+LMieRkZ7MnngwyTbiYCsZzQurgMzQPWwUX95oZ4wIgrlFS1erB25W+JzJDZ4dSDqcNNGxDmnYIaqEbWOuFcakmTZQx
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=17d50.5b56a75b.k1807; bh=v6f5Klr+3DlKpUycKBEusmWLRJsD0gxqSQ8e2F23bk4=; b=ne21FIE6mjrb3BghGZRzRq3Uw3IbTFgo5f4x7alQ9yRv0MzTZNR9RkUg+PXkf1WTGB4mmyr2QjZ9MuKEHihXIvA3HmmgRnvyaq6q3ffZKvi5Mo/OReHnh9g6D7pHe44VB60h9JBsSdQHjGHsYWOemw0ms43o/1IBM62Y19OEFKf3jLH6jBcIMc1n2bqamp1RN8YL6l76DXjHbsQCEn707LX7q+5KVfL6A1CTDkjNjtM9MfEwhchu+xIy9EgZsV27
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 24 Jul 2018 04:13:15 -0000
Received: by ary.qy (Postfix, from userid 501) id 771A32002CDBCF; Tue, 24 Jul 2018 00:13:15 -0400 (EDT)
Date: 24 Jul 2018 00:13:15 -0400
Message-Id: <20180724041315.771A32002CDBCF@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: ietf-822@ietf.org
Cc: poccil14@gmail.com
In-Reply-To: <5b56a4ba.1c69fb81.836c0.d955@mx.google.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-822/L0HcMtGnOvWzOerQjtGsXBIHyd0>
Subject: Re: [ietf-822] (no subject)
X-BeenThere: ietf-822@ietf.org
X-Mailman-Version: 2.1.27
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: Tue, 24 Jul 2018 04:13:21 -0000

In article <5b56a4ba.1c69fb81.836c0.d955@mx.google.com> you write:

>> Plan B: figure out how to make your URLs short enough that your List-Unsubscribe
>headers are under 998 characters. ...

>Plan B is only feasible if the same person provides the URL _and_ writes the code to generate the
>List-Unsubscribe header field (or any other list header field) for the corresponding message; not so if a
>software library generates a message containing the value of a List-Unsubscribe (or other) header field
>provided by a (third-party) user that, while otherwise syntactically valid, could exceed 998 characters in
>length. ....

You lost me here.  Is there some force that requires you to pass giant
URLs to List-Unsubscribe?  If you want to interoperate, use reasonably
short URLs.  This should not be rocket science.

R's,
John