|
||
| Menu | |
|
|
|
This page contains information, which are primarily of use for newsserver administrators. Here are some examples of configuration files which might be of use for the scout.* hierarchy.
It might be of use to change some of these configuration files to the own system. Because of this the examples are only guidelines. The configuration files are thought to be of use for INN, but can be changed similarly to other newssystems.
The moderators file specifies, which email address the server should take to forward the posting to the appropriate moderator. This applies only to moderated newsgroups. For scout.* this is quite easy:
## SCOUT (Newsgroups for scouts and guides) scout.*:%s@news.scoutnet.org
(This file can also be downloaded).
The control.ctl file defines the configuration which control messages are allowed to be executed on the newsserver.
We give here an example, which we think is appropriately for scout.*.
## SCOUT (Newsgroups for scouts and guides) # URL: http://news.scoutnet.org # Limited distribution hierarchy, visit above website for information. checkgroups:*:scout.*:drop newgroup:*:scout.*:drop rmgroup:*:scout.*:drop # PGP entries # Key URL: http://news.scoutnet.org/scout-pgpkey.asc # Key fingerprint = A74C F6D9 E33C 56E1 3FEB C6CE 490F 4B44 484C C331 #checkgroups:control@news.scoutnet.org:scout.*:verify-control@news.scoutnet.org #newgroup:control@news.scoutnet.org:scout.*:verify-control@news.scoutnet.org #rmgroup:control@news.scoutnet.org:scout.*:verify-control@news.scoutnet.org # Non-PGP entries # The best idea is to get PGP, due to security reasons #checkgroups:control@news.scoutnet.org:scout.*:mail #newgroup:control@news.scoutnet.org:scout.*:mail #rmgroup:control@news.scoutnet.org:scout.*:mail
(This file can also be downloaded).
The first part of the control.ctl file defines, that all control messages should be dropped generally. This is a limited distribution hierarchy. We want to protect our system against misusage. If this control.ctl is added in the worldwide directory of hierarchy the general action will be dropping the control message. So there will be no ghost groups on other servers.
The next two parts are the real configuration settings. Please uncomment one of them. If you have PGP installed, uncomment the second part and get the PGP-Key. If you don't have PGP installed uncomment the third part.
You can add other maintainers like your own country coordinator. He is allowed to create his own hierarchy. If the control authority sees that there is a control message about the creation of a new newsgroup, it will boost the control message to the rest of the network.
The file expire.ctl contains settings about how long an article will be stored on a newsserver.
This is just an example. It depends on how much space you have on your hard disk and how many newsgroups and messages there are. Some of our servers store messages for a year or even longer. It's up to you to decide how long you want to keep the messages.
## SCOUT (Newsgroups for scouts and guides) scout.*:A:90:90:90
(This file can be downloaded).
The file distrib.pats contains descriptions of the distributions just like the newsgroups file.
This file patches newsgroup patterns where the corresponding distribution headers should be added. In this example, every newsgroup that starts with scout.* gets the header "Distribution: scoutnet" added.
This is quite important when creating control messages. Most Servers that are configured halfway reasonably don't accept control messages from unknown distributions. This avoids scout.* groups being created on those servers. Of course there are others... :-/
## SCOUT (Newsgroups for scouts and guides) 10:scout.*:scoutnet
(This file can be downloaded).
Following are some of other config files for scout.*: