Mercurial > noffle
diff docs/noffle.conf.5 @ 88:1fcdced0246e noffle
[svn] Move posting code to post.c, add command line posting
author | bears |
---|---|
date | Thu, 18 May 2000 13:17:23 +0100 |
parents | dfcb28566d36 |
children | 2869baa02f3c |
line wrap: on
line diff
--- a/docs/noffle.conf.5 Thu May 18 13:11:05 2000 +0100 +++ b/docs/noffle.conf.5 Thu May 18 13:17:23 2000 +0100 @@ -1,5 +1,5 @@ .TH noffle.conf 5 -.\" $Id: noffle.conf.5 96 2000-05-17 10:51:22Z enz $ +.\" $Id: noffle.conf.5 100 2000-05-18 12:17:23Z bears $ .SH NAME noffle.conf \- Configuration file for NOFFLE news server @@ -38,6 +38,38 @@ after making changes to the server entries. .TP +.B getgroups <group pattern> [, <group pattern> ...] +Only retrieve from the most recently specified server newsgroups that match +the specified patterns. The patterns can contain \fIwildcards\fP, and +there can be multiple +.B getgroups +lines. For further details on +.B getgroups +processing in tandem with \fBomitgroups\fP, see the section on +.B omitgroups +following. +.br +Default: All groups + +.TP +.B omitgroups <group pattern> [, <group pattern> ...] +Don't retrieve from the most recently specified server newsgroups that match +the specified patterns. The patterns can contain \fIwildcards\fP, and +there can be multiple +.B omitgroups +lines. When processing a new newsgroup name, it is checked first to see +if it appears on the +.B getgroups +list (if any). If not, the group is rejected. +Then the group is checked to see if it appears on the +.B omitgroups +list. If it does not, the group is accepted as a group +.B NOFFLE +will list and collect as required. +.br +Default: No groups + +.TP .B max-fetch <n> Never get more than <n> articles. If there are more, the oldest ones are discarded. @@ -108,9 +140,14 @@ Default: yes .TP -.B remove-messageid yes|no -This option is deprecated and ignored. -It is only there for compatibility with old config-files. +.B post-locally yes|no +Place articles posted to external servers in the local aticle database +immediately. Some servers may rewrite Message-IDs, which will cause +duplicate postings of this option is enabled. Also, if for some reason +the post to the remote server fails, the article still exist in the local +database, which may be a source of some confusion. +.br +Default: no .TP .B replace-messageid yes|no