IETF Logo Mail Archive

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

Thomas 'Mike' Michlmayr <mike@cosy.sbg.ac.at> Thu, 19 December 1996 21:00 UTC

Received: from cnri by ietf.org id aa14487; 19 Dec 96 16:00 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa20558; 19 Dec 96 16:00 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id OAA16915 for ietf-nntp-outgoing; Thu, 19 Dec 1996 14:56:40 -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.8.3/8.7.3) with ESMTP id OAA16910 for <ietf-nntp@ACADEM2.ACADEM.COM>; Thu, 19 Dec 1996 14:56:38 -0600 (CST)
Received: from loewe.cosy.sbg.ac.at (loewe.cosy.sbg.ac.at [141.201.2.12]) by academ.com (8.8.3/8.7.1) with ESMTP id OAA16598 for <ietf-nntp@academ.com>; Thu, 19 Dec 1996 14:56:05 -0600 (CST)
Received: from grizzly.cosy.sbg.ac.at (grizzly [141.201.2.153]) by loewe.cosy.sbg.ac.at (8.7.4/8.7.3) with ESMTP id VAA19861; Thu, 19 Dec 1996 21:54:43 +0100 (MET)
Received: (from mike@localhost) by grizzly.cosy.sbg.ac.at (8.8.2/8.8.2) id VAA04102; Thu, 19 Dec 1996 21:48:24 +0100 (MET)
Message-ID: <Mutt.19961219214823.mike@grizzly.cosy.sbg.ac.at>
Date: Thu, 19 Dec 1996 21:48:23 +0100
From: Thomas 'Mike' Michlmayr <mike@cosy.sbg.ac.at>
To: Evan Champion <evanc@synapse.net>
Cc: ietf-nntp@academ.com
Subject: Re: ietf-nntp BCP for RFC977 server/RFC1036 interaction
References: <9612190326.AA16288@sulphur.osf.org> <Pine.BSI.3.91.961218224644.11477C-100000@piano.synapse.net>
X-Mailer: Mutt 0.53-export
Mime-Version: 1.0
X-PGP-Key: finger -l mike@cosy.sbg.ac.at
In-Reply-To: <Pine.BSI.3.91.961218224644.11477C-100000@piano.synapse.net>; from Evan Champion on Dec 18, 1996 23:24:32 -0500
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

On Dec 18, evanc@synapse.net (Evan Champion) wrote:
[...]
> > If I bang-on the IP address of the client then this is not necessary,
> > in fact it is unduly restrictive.
> 
> I still don't understand why anyone would want to forge the path to make
> sure an article doesn't get to a particular site.  

I know of several people whose signatures have a disclaimer daying that the
Microsoft Network is not allowed to store/use/... their articles. most of
them just want to have a sig that makes them look good in the eyes of their
friends, but some mean it. these are the ones that bang the names of
microsofts newsservers on their path. if that's their choice, it's a valid
reason IMHO, but i don't want to give them IHAVE permissions just for that.

-- 
Thomas 'Mike' Michlmayr can not assert the truth of all statements in 
this article and still be consistent. <mike@cosy.sbg.ac.at>

v2.8.7 | Report a Bug | By Email