Search the FAQ Archives

3 - A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z
faqs.org - Internet FAQ Archives

UK Newsadmin's FAQ
Section - 7. So which groups should I take on my site?

( Single Page )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Neighborhoods ]


Top Document: UK Newsadmin's FAQ
Previous Document: 6. What about the wales.*, scot.*, ni.* and england.* hierarchies?
Next Document: 8. How do I send articles to a moderated group?
See reader questions & answers on this topic! - Help others by sharing your knowledge
Well that is your prerogative to decide. If you want to take a standard uk.*
"full feed", then you should accept the periodic 'newgroup', 'rmgroup' and
'checkgroups' control messages issued by control@usenet.org.uk, and (for the
uk.* groups) no others. You may of course decide to take less than this if
your disc space and/or range of interests are limited.

It is possible to automate the acceptance of these control messages issued by
control@usenet.org.uk, and it is always safe to do so if you first verify the
PGP signatures with which they are authenticated (if you are unable to do
that, it is recommended that at least 'rmgroup's and 'checkgroups' be
inspected manually before acceptance - there are not so many of those,
anyway).

If you run CNews, then the following 'controlperm' file will achieve the
necessary effects. Note that this example also shows the correct way to
handle control messages for the "Big-8" and also what is believed to be
correct for several other hierarchies. Note that this example assumes that
you have installed the latest patch for CNews to implement the
verification of PGP signatures.

		--------------------------------

# Four/five fields per line,
# first a newsgroup pattern,
# second an author name (or "any"),
# third a set of operations ("n" newgroup, "r" rmgroup, "c" checkgroups),
# fourth a set of flags ("p" do it iff poster's identity is pgpverified,
#    "y" do it, "n" don't, "q" don't report at all, "v" include
#    entire control message in report) (default "yv"),
# fifth (optionally) the entity allowed to pgpsign it.

# group-admin@isc.org run the main Usenet hierarchies
comp,sci,misc,rec,soc,talk,news,humanities group-admin@isc.org n p news.announce.newgroups
# but their name can be forged, so don't let them rmgroup unless you use 'p'...
comp,sci,misc,rec,soc,talk,news,humanities group-admin@isc.org r p news.announce.newgroups
# likewise checkgroups
comp,sci,misc,rec,soc,talk,news,humanities group-admin@isc.org c p news.announce.newgroups
# and nobody else gets any attention in these hierarchies
comp,sci,misc,rec,soc,talk,news,humanities	any	nrc	nv

uk	control@usenet.org.uk		nrc	p uk.net.news.announce
wales	control@wales-usenet.org 	nrc	p wales-usenet
england	admin@england.news-admin.org	nrc	p england-usenet
europa	group-admin@usenet.eu.org	nrc	p group-admin@usenet.eu.org
de	moderator@dana.de		nrc	p de.admin.news.announce
nl	nl-admin@nic.surfnet.nl		nrc	p nl.newsgroups
nz	root@usenet.net.nz		nrc	p nz-hir-control
bionet	dmack@*.bio.net			n	y
bionet	dmack@*.bio.net			rc	nv
bionet	kristoff@*.bio.net		n	y
bionet	kristoff@*.bio.net		rc	nv
bionet	shibumi@*.bio.net		nrc	nv
linux	hpa@yggdrasil.com		nrc	nv
bit	jim@*american.edu		nrc	p bit.admin
biz	edhew@xenitec.on.ca		n	y
biz	edhew@xenitec.on.ca		rc	nv
clari	clarinet@clarinet.com		nrc	p ClariNet.Group

# it's really tempting to change this one to nq...
alt	any				nr	nv
alt	any				c	nq

# to.all groups are manually manipulated only
to	any				nrc	nq

# final default:  refuse noisily
all	any				nrc	nv

		--------------------------------

If you run INN, the corresponding file is 'control.ctl' and the facilities
available are slightly different. Here is the nearest equivalent to the
'controlperm' file above.

		--------------------------------

##  $Revision: 1.4 $
##  control.ctl - access control for control messages
##  Format:
##	<message>:<from>:<newsgroups>:<action>
##  The last match found is used.
##	<message>	Control message or "all" if it applies
##			to all control messages.
##	<from>		Pattern that must match the From line.
##	<newsgroups>	Pattern that must match the newsgroup being
##			newgroup'd or rmgroup'd (ignored for other messages).
##	<action>	What to do:
##			    doit	Perform action (usually sends mail too)
##			    doifarg	Do if command has an arg (see sendsys)
##			    doit=xxx	Do action; log to xxx (see below)
##			    drop	Ignore message
##			    log		One line to error log
##			    log=xxx	Log to xxx (see below)
##			    mail	Send mail to admin
##			    verify-ddd	doit if pgpverified by ddd
##			    verify-ddd=xxx
##			xxx=mail to mail; xxx= (empty) to toss; xxx=/full/path
##			to log to /full/path; xxx=foo to log to ${LOG}/foo.log
##	last entry matched is used 
##	DEFAULT
all:*:*:mail

##	CHECKGROUPS MESSAGES
checkgroups:*:*:mail
checkgroups:group-admin@isc.org:comp.*|misc.*|news.*|rec.*|sci.*|soc.*|talk.*|humanities.*:verify-news.announce.newgroups=mail
checkgroups:control@usenet.org.uk:uk.*:verify-uk.net.news.announce=mail
checkgroups:control@wales-usenet.org:wales.*:verify-wales-usenet=mail
checkgroups:admin@england.news-admin.org:england.*:verify-england-usenet=mail
checkgroups:group-admin@usenet.eu.org:europa.*:verify-group-admin@usenet.eu.org=mail

##	IHAVE/SENDME MESSAGES
ihave:*:*:drop
sendme:*:*:drop

##	NEWGROUP MESSAGES
##  Any newsgroups
newgroup:*:*:mail
newgroup:group-admin@isc.org:comp.*|misc.*|news.*|rec.*|sci.*|soc.*|talk.*|humanities.*:verify-news.announce.newgroups=newgroup
newgroup:control@usenet.org.uk:uk.*:verify-uk.net.news.announce=newgroup
newgroup:control@wales-usenet.org:wales.*:verify-wales-usenet=newgroup
newgroup:admin@england.news-admin.org:england.*:verify-england-usenet
newgroup:group-admin@usenet.eu.org:europa.*:verify-group-admin@usenet.eu.org=newgroup
newgroup:moderator@dana.de:de.*:verify-de.admin.news.announce=newgroup
newgroup:nl-admin@nic.surfnet.nl:nl.*:verify-nl.newsgroups=newgroup
newgroup:root@usenet.net.nz:nz.*:verify-nz-hir-control=newgroup
newgroup:dmack@*.bio.net:bionet.*:doit=newgroup
newgroup:kristoff@*.bio.net:bionet.*:doit=newgroup
newgroup:shibumi@*.bio.net:bionet.*:mail
newgroup:hpa@yggdrasil.com:linux.*:doit=newgroup
newgroup:jim@*american.edu:bit.*:verify-bit.admin=newgroup
newgroup:edhew@xenitec.on.ca:biz.*:doit=newgroup
newgroup:clarinet@clarinet.com:clari.*:verify-ClariNet.Group=newgroup

##	RMGROUP MESSAGES
##  Any newsgroups
rmgroup:*:*:mail
rmgroup:group-admin@isc.org:comp.*|misc.*|news.*|rec.*|sci.*|soc.*|talk.*|humanities.*:verify-news.announce.newgroups=mail
rmgroup:control@usenet.org.uk:uk.*:verify-uk.net.news.announce=mail
rmgroup:control@wales-usenet.org:wales.*:verify-wales-usenet=mail
rmgroup:admin@england.news-admin.org:england.*:verify-england-usenet=mail
rmgroup:group-admin@usenet.eu.org:europa.*:verify-group-admin@usenet.eu.org=mail
rmgroup:moderator@dana.de:de.*:verify-de.admin.news.announce=mail
rmgroup:nl-admin@nic.surfnet.nlnews@a3.xs4all.nl:nl.*:verify-nl.newsgroups=mail
rmgroup:root@usenet.net.nz:nz.*:verify-nz-hir-control=mail
rmgroup:dmack@*.bio.net:bionet.*:doit=mail
rmgroup:kristoff@*.bio.net:bionet.*:doit=mail
rmgroup:shibumi@*.bio.net:bionet.*:doit=mail
rmgroup:hpa@yggdrasil.com:linux.*:doit=mail
rmgroup:jim@*american.edu:bit.*:verify-bit.admin=mail
rmgroup:edhew@xenitec.on.ca:biz.*:doit=mail
rmgroup:clarinet@clarinet.com:clari.*:verify-ClariNet.Group=mail

		--------------------------------


User Contributions:

Comment about this article, ask questions, or add new information about this topic:

CAPTCHA




Top Document: UK Newsadmin's FAQ
Previous Document: 6. What about the wales.*, scot.*, ni.* and england.* hierarchies?
Next Document: 8. How do I send articles to a moderated group?

Single Page

[ Usenet FAQs | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
chl@clerew.man.ac.uk (Charles Lindsey)





Last Update March 27 2014 @ 02:12 PM