[ietf-smtp] Delayed posting of draft-klensin-rfc5321bis-03

John C Klensin <john-ietf@jck.com> Mon, 09 March 2020 17:35 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id C8D123A1461 for <ietf-smtp@ietfa.amsl.com>; Mon, 9 Mar 2020 10:35:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id FKtRCsskw6Nz for <ietf-smtp@ietfa.amsl.com>; Mon, 9 Mar 2020 10:35:36 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66AED3A139A for <ietf-smtp@ietf.org>; Mon, 9 Mar 2020 10:35:36 -0700 (PDT)
Received: from [] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1jBMJT-000FzR-0t for ietf-smtp@ietf.org; Mon, 09 Mar 2020 13:35:35 -0400
Date: Mon, 09 Mar 2020 13:35:29 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf-smtp@ietf.org
Message-ID: <8F76526688B97CFE79D28BED@PSB>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/PN6INUFzTmhZuIr7z_jEehgvZaw>
Subject: [ietf-smtp] Delayed posting of draft-klensin-rfc5321bis-03
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2020 17:35:45 -0000


draft-klensin-rfc5321bis-03 is not going up today as
planned.  My current target is April 1, which seems
appropriate.  Explanation below for anyone interested;
otherwise there is no more useful information in this note.


When Hector asked that I go ahead and post my current
working version of the I-D, I assumed that I'd just find five
minutes to compile it, push it through the posting tool,
confirm it, and get the thing up.

Instead, we've uncovered two problems:

(1) Something in my mail system is causing some plain text
attachments to be stripped of line endings (both the LR and
CRLF persuasions).  The finger at the moment points to Mulberry
(yes, I'm still running Mulberry and, while it is showing its
age, still agree with Chris Newman's comment about IMAP clients
from many years ago).

(2) Something in the submission process is looking at the file
(even with proper line endings and whether I run the process or
the Secretariat does), concluding that the file is not
text/plain but text/x-Algol68, and then refusing to post.  Who
knew we'd be hearing from Algol68 a half-century since a few of
us did some programming in it?

I have encouraged Henrik and AMS to not spend more time on this
today unless others have problems.  Given the rate at which we
are moving with getting a WG together (that is _not_ an attack
or slur on anyone, just an observation), I don't see any
advantage to putting anything else even slightly at risk by
rushing a patch or workaround through the system.

If anyone urgently wants to see the working version in the
meantime, contact me offlist and we will try to figure out how
to get it to you.