ietf-nntp Virtual NewsGroup hosting

Tim Roberts troberts at bigfoot.com
Wed Oct 11 14:25:22 PDT 2000


(Sorry for the html post earlier - I agree its a pain).

If I understand you correctly - INN supports virtual hosting based on the
USER and not the intended server?!?

Example: lets say that an ISP is virtually hosting news.cool.com (which has
cool.* groups) and news.verycool.com (which has verycool.* groups).

If I (using my newsreader) were to connect to news.cool.com - are you saying
that (given I am setup in the config to 'see' both) that I would see both
cool.* and verycool.* groups even though I connect to news.cool.com?

Obviously the owners of either cool.com or verycool.com would not think it
beneficial  - especially if they have a webpage forum on their site that
reads directly from the virtual hosted news and people see other companies
news groups!

----- Original Message -----
From: "Russ Allbery" <rra at stanford.edu>
To: <ietf-nntp at academ.com>
Sent: Wednesday, October 11, 2000 2:55 PM
Subject: Re: ietf-nntp Virtual NewsGroup hosting


> Tim Roberts <troberts at bigfoot.com> writes:
>
> > I always thought that News Hosting should be one of the virtual services
> > offered by an ISP similiar to mail or http so that if I connect to
> > news.virtualhost.com - I would only see the newsgroups that are being
> > hosted by virtualhost.com (versus every newsgroup being hosted by the
> > ISP).
>
> INN already supports this in the current version; you can use any of the
> mechanisms that readers.conf supports to distinguish between users from
> different domains (so the login, the origin IP address, ident responses,
> whatever).  In fact, INN has supported this to a limited extent for many
> years; you could exclude groups in the old nnrp.access file and they
> wouldn't show up to connecting clients matching that line, even as a
> result of a LIST command.  I think this was around as far back as 1.5 or
> older; I know it was in 1.7.2.
>
> I use this to hide the internal newsgroups that we use to gateway all of
> our role addresses to anyone other than staff members.
>
> I don't think this really requires any extensions to the protocol (apart
> from the standard authentication extensions).
>
> --
> Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>
>




More information about the ietf-nntp mailing list