Re: [ietf-822] (no subject)

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

Return-Path: <johnl@taugh.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 C8596130E34 for <ietf-822@ietfa.amsl.com>; Mon, 23 Jul 2018 21:28:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=Emi7uRHj; dkim=pass (1536-bit key) header.d=taugh.com header.b=CnFio7Xx
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 sDOgI0EEthwn for <ietf-822@ietfa.amsl.com>; Mon, 23 Jul 2018 21:28:13 -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 1B18E130DF4 for <ietf-822@ietf.org>; Mon, 23 Jul 2018 21:28:12 -0700 (PDT)
Received: (qmail 2665 invoked from network); 24 Jul 2018 04:28:12 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=a67.5b56aadc.k1807; bh=vU18J5NkzZRa3EiwrrlwASTZTbuLA1KqChTTmtUmweA=; b=Emi7uRHjidiD5SnZmlFVd+PP/+5mNxBRvM2ko6BeMQDqRf0XLSKpE0GHvYlYhtDPrrhOJgcxxk3XA00DaM7v2LGFG1WW0lm+tBQTeI5sJkKlpIPD0/cSBNYvLFTQgmhBwWdGRD87C+hLKCH5ftEQyvcg3kK+HWOxRA8Th2J/biBd5zI8H/ILc8kYVPxH9BU5UcZUHB/S6a5YuKgpCINFeKHm5B50Iw7ZZCj23J9m3Aryl22qDSwh8p27Zad5CaoH
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=a67.5b56aadc.k1807; bh=vU18J5NkzZRa3EiwrrlwASTZTbuLA1KqChTTmtUmweA=; b=CnFio7XxeDCgEFrxjitRZVf45OhnfSgmg2qPjT9MPOkz5Kbc8jGkCYgN1Hm+9TUoXrr+ybA6kYpC37Dzz9tPy3DUy6ijcViy+ThiW8m4i0nV5fdIOBclQ8zUAFLhdSyfG3cRwrOUkLwB8zFTjDHLATp3EO6cD5w76Q4zEJQvsyOuD0vEnaT1zI1Uc96IIJr6NgqLmodZbMebGoyJDaloxOfit9Fq/e0i0U7CPdblOkeL3ngHlxqGfI7+jvK/WCdO
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 24 Jul 2018 04:28:11 -0000
Date: 24 Jul 2018 00:28:11 -0400
Message-ID: <alpine.OSX.2.21.1807240026310.36374@ary.qy>
From: "John R Levine" <johnl@taugh.com>
To: "Peter Occil" <poccil14@gmail.com>
Cc: "ietf-822@ietf.org" <ietf-822@ietf.org>
In-Reply-To: <5b56aa40.1c69fb81.53109.c080@mx.google.com>
References: <5b56a4ba.1c69fb81.836c0.d955@mx.google.com> <20180724041315.771A32002CDBCF@ary.qy> <5b56aa40.1c69fb81.53109.c080@mx.google.com>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-822/APx7GF6cqgSurHV0kza7XFWMhMI>
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:28:15 -0000

On Tue, 24 Jul 2018, Peter Occil wrote:
> I mean from the point of view of a software developer creating a library to generate email messages.  This software developer is not the one who comes up with values for header fields (such as URLs for List-Unsubscribe header fields).  If the developer's software library is passed a List-Unsubscribe header field value greater than 998 characters in length (e.g., when a third-party user uses that library to generate a blank message, then to set the List-Unsubscribe header field to such a value, then to generate a finished message), the software developer would then have to make a choice whether to program that library--

But this is engineering, not theology.  If you use long URLs in headers, 
they don't work very well.  So don't do that.  If it were my library I'd 
throw an error if the list-unsubscribe header didn't fit in 998 characters 
so the person calling it would know to fix whatever was generating giant 
URL strings.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly