Re: [ietf-822] (no subject)

Peter Occil <poccil14@gmail.com> Tue, 24 July 2018 04:33 UTC

Return-Path: <poccil14@gmail.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 19D80130DF2 for <ietf-822@ietfa.amsl.com>; Mon, 23 Jul 2018 21:33:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level:
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 ISoH7KSt6jgE for <ietf-822@ietfa.amsl.com>; Mon, 23 Jul 2018 21:33:12 -0700 (PDT)
Received: from mail-yb0-x235.google.com (mail-yb0-x235.google.com [IPv6:2607:f8b0:4002:c09::235]) (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 CBA4712426A for <ietf-822@ietf.org>; Mon, 23 Jul 2018 21:33:11 -0700 (PDT)
Received: by mail-yb0-x235.google.com with SMTP id x15-v6so1159432ybm.2 for <ietf-822@ietf.org>; Mon, 23 Jul 2018 21:33:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:mime-version:to:cc:from:subject:date:importance :in-reply-to:references; bh=I1I5jgeSToYpwSzPLWEQECYNskrzB+i2R93K05bTSvM=; b=r8pmWWwfy+Q0CpA5qBONBm/I8j46uHkN0wJ/6AMPJMtrj5w9JBYQCn4SFmEsYOu2Rq xnzwcSlTheeUzD0fMxJlyOpN64ukazFIX/9KWrcaiBDGLaoBB2yZuJavn6Lxx1HkmXHi 0a8S7d2L+nLD3wnFTGNUAe2al/mbUsaZAlL9C9elvG6kj04x4u4lPfF0JRfEwBqcIjeZ QpWUZq99hwTuh2erjwJ/nFd6oh9VYej+GzyHued2raryU0LJjMaB4T09Bm3zn/LQxxH1 gxJI2ff5mTnadgzKhg/trhFNhKAC3laeaAiyAyfkV/0NrUsV/JzlbjoYJ/2zQc+Va1YF KciA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:mime-version:to:cc:from:subject:date :importance:in-reply-to:references; bh=I1I5jgeSToYpwSzPLWEQECYNskrzB+i2R93K05bTSvM=; b=UU/3bC5edsElb0Jlstb+oli71fRnVhzmfVlZJYNnKB8Njgo3+MCE27mdDnozPgufvz KmQxBg1A1iuAaasR0fQnamfzU9yF83Ip+xA0iUYuF4GPHQ7I6rupmtTuKTNFUHKk6XBo ryChVC4KBeP8/ZgWeakNn+Rnp3KU+bo5caZMf9XpROdGIf1qJcErQhngqdHgydEQsM4X 3MQkUw9JE1LKUnVEBHyxa9DGVtwWYfPMpptCza1zTcWy0X6EOf78JhuBHPkQepBDGSYv JSFp+Fk8XONH2N6e4x0pboS014v/pxlbPMNZP0pdsUSYorE/P2mFZCTmpESZV2q3YKZl BwaQ==
X-Gm-Message-State: AOUpUlGR8MyIJnIAsoJd9VO1RICLwIfS4+Kp03DqnJLtqoUD69ex+TVW UuIno0XPJS4HrKpyuR4DYF4Cz+IbRjQ=
X-Google-Smtp-Source: AAOMgpfrJg8k61tGdlvpyxYmFi44G2KfUffXlNtIDxbfCxoH9XWp7YRd/ADw7xHcZzy1hdnl/2qZNQ==
X-Received: by 2002:a25:9d0d:: with SMTP id i13-v6mr8398086ybp.104.1532406790916; Mon, 23 Jul 2018 21:33:10 -0700 (PDT)
Received: from ?IPv6:2601:192:4e00:596:22:8b71:4eb9:6006? ([2601:192:4e00:596:22:8b71:4eb9:6006]) by smtp.gmail.com with ESMTPSA id 63-v6sm6240022ywd.8.2018.07.23.21.33.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 Jul 2018 21:33:10 -0700 (PDT)
Message-ID: <5b56ac06.1c69fb81.3d4fa.136e@mx.google.com>
MIME-Version: 1.0
To: John R Levine <johnl@taugh.com>
Cc: "ietf-822@ietf.org" <ietf-822@ietf.org>
From: Peter Occil <poccil14@gmail.com>
Date: Tue, 24 Jul 2018 00:33:12 -0400
Importance: normal
X-Priority: 3
In-Reply-To: <alpine.OSX.2.21.1807240026310.36374@ary.qy>
References: <5b56a4ba.1c69fb81.836c0.d955@mx.google.com> <20180724041315.771A32002CDBCF@ary.qy> <5b56aa40.1c69fb81.53109.c080@mx.google.com> <alpine.OSX.2.21.1807240026310.36374@ary.qy>
Content-Type: multipart/alternative; boundary="_B81BD1BB-4E6F-46B8-A16A-0ECC25297C57_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-822/CrKi2z_GYwlmXAKsyHPzpjpmN5w>
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:33:13 -0000

So in that case, would a reasonable update to RFC 2369 be to impose a character limit of 998 characters on list header fields, including the List-Unsubscribe header field?

--Peter Occil


From: John R Levine
Sent: Tuesday, July 24, 2018 12:28 AM
To: Peter Occil
Cc: ietf-822@ietf.org
Subject: RE: [ietf-822] (no subject)

[…]  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