ietf-nntp BCP for RFC977 server/RFC1036 interaction

Ade Lovett ade at demon.net
Mon Apr 7 14:10:35 PDT 1997


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.



More information about the ietf-nntp mailing list