Leafnode - NNTP Server for small sites http://leafnode.org Leafnode is a software package that implements a store & forward NNTP proxy (client and server). It can be used to give a regular newsreader off-line functionality, merge news articles from several upstream newsservers for newsreaders that only support one server well and avoid duplicate news download for a small LAN with multiple users reading news. Leafnode is intended for use at home or in small offices. Scalability for large user or newsgroup counts has not been a design goal. Leafnode requires no maintenance and can run unattended. It will recover from most problems without user intervention if possible. No configuration of a newsfeed at the upstream server is necessary, leafnode looks to the upstream server like a regular newsreader program. Leafnode will automatically figure which newsgroups are read locally and will download them, and it will stop downloading from these newsgroups if they haven't been read locally. START_LEAFNODE Start the leafnode daemon 'yes' or 'no' Default: START_LEAFNODE='no' LEAFNODE_EXPIRE The number of days an article should be kept around. In the example, ten days after the article has last been read, it is deleted by texpire. This value MUST be at least 1. Default: LEAFNODE_EXPIRE='10' LEAFNODE_FETCH_CRON Start time for fetch job Example: LEAFNODE_FETCH_CRON='*/20 * * * *' LEAFNODE_EXPIRE_CRON Start time for deleting meassges by texpire Example: LEAFNODE_EXPIRE_CRON='20 1 * * *' LEAFNODE_SERVERS_N Number of external Newserver LEAFNODE_SERVER_%_SERVER External Newserver Example: LEAFNODE_SERVER_1_SERVER='news.spline.de' LEAFNODE_SERVER_%_PORT Port of external Newsserver (usually 119) Example: LEAFNODE_SERVER_1_PORT='119' LEAFNODE_SERVER_%_AUTH Need of Auth Example: LEAFNODE_SERVER_1_AUTH='no' LEAFNODE_SERVER_%_USER Username for Auth Example: LEAFNODE_SERVER_1_USER='username' LEAFNODE_SERVER_%_PASS Password for Auth Example: LEAFNODE_SERVER_1_PASS='secret' LEAFNODE_GROUPEXPIRE_N Number of groupexpire settings "LEAFNODE_GROUPEXPIRE" makes it possible to adjust expiry times for individual groups. Expiry times are given in days. This value is used by texpire. You can specify as many groupexpire lines as you like. It is possible to specify glob-like wildcard expressions. If set to -1 articles will never expire in these groups. Example: LEAFNODE_GROUPEXPIRE_N='0' LEAFNODE_GROUPEXPIRE_%_MASK Name of newsgroup(s). Wildcards allowed. e.g. spline.eisfair.* Example: LEAFNODE_GROUPEXPIRE_1_MASK='spline.test' LEAFNODE_GROUPEXPIRE_%_DAYS Number of days to keep messages in this newsgroup (-1=never expire). Example: LEAFNODE_GROUPEXPIRE_1_DAYS='1' LEAFNODE_FINETUNING You normally don't have to use the finetuning setting, but you are able to. :-) Example: LEAFNODE_FINETUNING='no' LEAFNODE_FETCH_MAX Specifies the maximum number of articles fetchnews should fetch from the upstream server in each group. default=0 (all) Example: LEAFNODE_FETCH_MAX='0' LEAFNODE_FETCH_MAX_CROSSPOST If you want to combat spam, you can filter out all postings that are posted to more than a certain number of newsgroups. Setting this parameter to very low values is probably a bad idea. This feature is switched off by default. Example: LEAFNODE_FETCH_MAX_CROSSPOST='0' LEAFNODE_FETCH_MAX_AGE If an article turns up on your upstream news server which is older than "LEAFNODE_FETCH_MAX_AGE" days it will not been fetched even if you don't have it yet. This is useful if your upstream server gets occasional "hiccups". The default is set to 10. If you want to switch this feature off, set maxage to some very large value, such as 20000 (this is equivalent to roughly 54 years). Example: LEAFNODE_FETCH_MAX_AGE='0' LEAFNODE_FETCH_MAX_LINES If you want to avoid receiving very large articles, you may set the "LEAFNODE_FETCH_MAX_LINES" parameter to the maximal number of lines an article should have. By default, this feature is switched off. Example: LEAFNODE_FETCH_MAX_LINES='0' LEAFNODE_FETCH_MIN_LINES Sometimes newsgroups are spammed with empty postings. To reject these postings, you can set the "LEAFNODE_FETCH_MIN_LINES" parameter. Setting minlines to a value larger 4 is probably not a good idea since you will also start to kill "real" postings then. By default, this feature is switched off. Example: LEAFNODE_FETCH_MIN_LINES='0' LEAFNODE_FETCH_MAX_BYTES If you want to avoid receiving very large articles, instead of using the "LEAFNODE_FETCH_MAX_LINES" parameter you can also use the "LEAFNODE_FETCH_MAX_BYTES" parameter. By default, this feature is switched off. Example: LEAFNODE_FETCH_MAX_BYTES='0' LEAFNODE_FETCH_TIMEOUT_SHORT By default, a group that has been accidentally touched is being fetched for two days. You can change this time by changing "LEAFNODE_FETCH_TIMEOUT_SHORT". Example: LEAFNODE_FETCH_TIMEOUT_SHORT='2' LEAFNODE_FETCH_TIMEOUT_LONG By default, a group that has not been read at all is being fetched for seven days before being unsubscribed. This interval can be changed by setting "LEAFNODE_FETCH_TIMEOUT_LONG" to a different value. Example: LEAFNODE_FETCH_TIMEOUT_LONG='7' LEAFNODE_FETCH_VERBOSE Verbosity of fetch job Example: LEAFNODE_FETCH_VERBOSE='0' LEAFNODE_FETCH_INITIAL Defines how many articles from a newly subscribed group should be fetched. The default is to fetch all old articles, which can get quite time-consuming when subscribing to a very busy group. This is equivalent to setting initialfetch to zero. If you want to get no old articles when subscribing to a new group, you should set initialfetch to one, as in the example. Example: LEAFNODE_FETCH_INITIAL='1' Default: LEAFNODE_FETCH_INITIAL='0' (all) LEAFNODE_FQDN If your news-client isn't able to create an valid msg-id, you have to enter an vaild an FQDN Example: LEAFNODE_FQDN='valid.domain