Re: [ietf-822] Question regarding RFC 2369
"John Levine" <johnl@taugh.com> Sat, 21 July 2018 20:19 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 24C78130E15 for <ietf-822@ietfa.amsl.com>; Sat, 21 Jul 2018 13:19:58 -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=BBMK0u2a; dkim=pass (1536-bit key) header.d=taugh.com header.b=tmNrPEfE
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 TyZGAOI0YH9f for <ietf-822@ietfa.amsl.com>; Sat, 21 Jul 2018 13:19:56 -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 8D277130DF1 for <ietf-822@ietf.org>; Sat, 21 Jul 2018 13:19:56 -0700 (PDT)
Received: (qmail 62195 invoked from network); 21 Jul 2018 20:19:54 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=f2f1.5b53956a.k1807; bh=uxu8xGXVYfrXXJlnLHVGhac4krMvHUARmgzw+85iexs=; b=BBMK0u2aggNMk+QX4szjKDCoWS4OS2JYmGWT5qYuYva9X+w4/mx1TjHDVf/IhWmaBgD625HtreTsynUrJjQ0gP09iVZpM3W9I2zUgW2fK5ZrYDqFCnvJOTzMO73cQghPyKkNI67YbDILMLXuLVMiwCQu6V9At+aDHCOuI7D0OBTcDb3be+4n5YpxTkTsQXMdbSInvszTTa0n2ccmif+/ejg8bJHpnlXj3112D+joTbUVH+XxwzvhuKShn3wkIBE3
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=f2f1.5b53956a.k1807; bh=uxu8xGXVYfrXXJlnLHVGhac4krMvHUARmgzw+85iexs=; b=tmNrPEfEA4tDxfqRY5EDW0utmorrZpDjo/RK/MOJjcNXPkfr0jRmgJNFUtinDfYLGb1gO8977FIsQUokj6+EN5iexN/VpjQL9sv6WlZ6MOxHzLCJOhTp/b8simBH7CTNXUrjuxHY0zgfd7wA/NGz3AvX77EVLb7lGoxxvAbaz9Rxl9R/zqtd0lV3VlbANjwD9kQPO+vhZkIpId3eWFbvWZEIm9MBOdQYmxFdaKHh4Ce74wHruuWd2rOpJ/d+SIv1
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; 21 Jul 2018 20:19:54 -0000
Received: by ary.qy (Postfix, from userid 501) id 1823220028AAAD; Sat, 21 Jul 2018 16:19:53 -0400 (EDT)
Date: Sat, 21 Jul 2018 16:19:53 -0400
Message-Id: <20180721201954.1823220028AAAD@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-822@ietf.org
In-Reply-To: <1532183533.1694870.1448275552.60F55C41@webmail.messagingengine.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/NYKy-USpCoHBuA_92nD5pDDF4h8>
Subject: Re: [ietf-822] Question regarding RFC 2369
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: Sat, 21 Jul 2018 20:19:58 -0000
In article <1532183533.1694870.1448275552.60F55C41@webmail.messagingengine.com> you write: >> To the extent the first clause applies to software generating messages >> that might contain list header fields, usually for the purpose of >> first sending them, this makes it harder for software to encode >> message header fields in a generic manner rather than having to deal >> with special cases like the list header fields, since, among other >> things, such software may seek to comply with line length limitations >> in RFC 5322 by folding long lines in accordance with that RFC. Remember that MUST means "do this if you want to interoperate", not "do this or die." Plan A: update RFC 2369 to say MAY add spaces, send out a press release, wait for everyone in the world to update their software to remove spaces when parsing List-x headers. Plan B: figure out how to make your URLs short enough that your List-Unsubscribe headers are under 998 characters. I know what I'd do. R's, John
- Re: [ietf-822] Question regarding RFC 2369 John Levine
- Re: [ietf-822] Question regarding RFC 2369 Alexey Melnikov
- Re: [ietf-822] Question regarding RFC 2369 Peter Occil