Re: ietf-nntp BCP for RFC977 server/RFC1036 interaction

Ade Lovett <ade@demon.net> Mon, 07 April 1997 21:15 UTC

Received: from cnri by ietf.org id aa24603; 7 Apr 97 17:15 EDT
Received: from ANNOUNCER.ACADEM.COM by CNRI.Reston.VA.US id aa22162; 7 Apr 97 17:14 EDT
Received: (from majordomo@localhost) by announcer.academ.com (8.8.5/8.7.3) id QAA13847 for ietf-nntp-outgoing; Mon, 7 Apr 1997 16:10:41 -0500 (CDT)
X-Authentication-Warning: announcer.academ.com: majordomo set sender to owner-ietf-nntp using -f
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by announcer.academ.com (8.8.5/8.7.3) with ESMTP id QAA13842 for <ietf-nntp@ANNOUNCER.ACADEM.COM>; Mon, 7 Apr 1997 16:10:39 -0500 (CDT)
Received: from reverse.eng.demon.net (reverse.eng.demon.net [193.195.45.100]) by academ.com (8.8.5/8.7.1) with SMTP id QAA08769 for <ietf-nntp@academ.com>; Mon, 7 Apr 1997 16:10:37 -0500 (CDT)
Received: from ade by reverse.eng.demon.net with esmtp (Exim 1.61 #1) id 0wELgS-0002aP-00; Mon, 7 Apr 1997 22:10:36 +0100
To: ietf-nntp@academ.com
Subject: Re: ietf-nntp BCP for RFC977 server/RFC1036 interaction
Organization: Demon Internet Ltd.
Reply-To: ade@demon.net
In-reply-to: Your message of "Mon, 07 Apr 1997 14:46:53 EDT." <199704071846.OAA09145@Twig.Rodents.Montreal.QC.CA>
Date: Mon, 07 Apr 1997 22:10:35 +0100
From: Ade Lovett <ade@demon.net>
Message-Id: <E0wELgS-0002aP-00@reverse.eng.demon.net>
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

der Mouse writes:
>
>And in fact you may want to.  Any bets on how many ad-spammers are
>taking NNTP-Posting-User and NNTP-Posting-Host with an @ between them
>for their lists?

In which case, having something along the lines of:

	NNTP-Posting-Host: <host-or-ip> [ " " <host-or-ip> ]
	NNTP-Posting-User: <some-string>

	These headers MAY be present, giving information about the
	entity that submitted the original article from new.  The
	value of these headers MAY not be globally understandable,
	but SHOULD be in a form that administrators of the server
	to which the article is posted can decode.

	These headers SHOULD be generated by the server, and any
	currently existing versions of these headers SHOULD be deleted
	before the article is forwarded.

and leave it at that -- possibly with suggested examples as to the
kind of information we currently assume is likely to appear in such
headers.

Make sense?

-aDe

-- 
Ade Lovett, Demon Internet Ltd.