ietf-nntp NNTP doubling of starting periods

Jean van Waterschoot <jvwater@mcs.net> Wed, 13 November 1996 14:13 UTC

Received: from cnri by ietf.org id am29057; 13 Nov 96 9:13 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa03615; 13 Nov 96 2:42 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.7.6/8.7.3) id BAA24802 for ietf-nntp-outgoing; Wed, 13 Nov 1996 01:37:37 -0600 (CST)
X-Authentication-Warning: academ2.academ.com: majordomo set sender to owner-ietf-nntp using -f
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by academ2.academ.com (8.7.6/8.7.3) with ESMTP id BAA24797 for <ietf-nntp@ACADEM2.ACADEM.COM>; Wed, 13 Nov 1996 01:37:35 -0600 (CST)
Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by academ.com (8.7.6/8.7.1) with ESMTP id BAA13089; Wed, 13 Nov 1996 01:37:33 -0600 (CST)
Received: from smtp-client.mcs.net (jvwater.pr.mcs.net [204.95.35.181]) by Kitten.mcs.com (8.8.2/8.8.2) with SMTP id BAA05943; Wed, 13 Nov 1996 01:37:31 -0600 (CST)
Date: Wed, 13 Nov 1996 01:37:31 -0600 (CST)
Message-Id: <199611130737.BAA05943@Kitten.mcs.com>
From: Jean van Waterschoot <jvwater@mcs.net>
To: Stan Barber <sob@academ.com>
Cc: ietf-nntp@academ.com
Subject: ietf-nntp NNTP doubling of starting periods
X-Mailer: Internet Squire 2.0 8
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

RFC 977 specifies the following for lines that start with a period (.)

>   The text forming the header and body of the message to be posted
>   should be sent by the client using the conventions for text received
>   from the news server:  A single period (".") on a line indicates the
>   end of the text, with lines starting with a period in the original
>   text having that period doubled during transmission.
>
>   No attempt shall be made by the server to filter characters, fold or
>   limit lines, or otherwise process incoming text.  It is our intent
>   that the server just pass the incoming message to be posted to the
>   server installation's news posting software, which is separate from
>   this specification.  See RFC850 for more details.

Is this still in use? It seems unnecessary to distinguish lines that
contain *only* a period (etx) from text lines that start with a period. Any
parser should be able to recognize that <cr><lf>.<cr><lf> is the end of the
data stream and treat lines that start with a period as normal text lines.

I tried sending lines that started with 1-5 periods on a line through INN
and it passed them unaltered as the second paragraph suggests it should.

If this is not used should it be phased out for the sake of transparency? 

Comments?

Jean. (jvwater@mcs.net)
http://www.mcs.net/~jvwater