Mercurial > noffle

comparison docs/noffle.conf.5 @ 222:bf290632d29e noffle

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[svn] * src/post.c: Always replace message ID in posted message if existing message ID fails Prt_isValidMsgId. * noffle.conf.example,docs/noffle.conf.5,src/configfile.c: Change replace-messageid default from 'yes' to 'no'. These days bad message IDs from newsreaders shouldn't happen (or should be more easily fixable from the newsreader config), and replacing message IDs causes havoc if you're gatewaying mailing lists or similar.
author bears
date Sun, 09 Dec 2001 11:32:31 +0000
parents 21200ce10e68
children a16ee4b00b66
comparison
equal deleted inserted replaced
221:0eaf93997170 222:bf290632d29e
1 .TH noffle.conf 5 1 .TH noffle.conf 5
2 .\" $Id: noffle.conf.5 331 2001-11-22 12:04:45Z mirkol $ 2 .\" $Id: noffle.conf.5 341 2001-12-09 11:32:31Z bears $
3 3
4 .SH NAME 4 .SH NAME
5 noffle.conf \- Configuration file for NOFFLE news server 5 noffle.conf \- Configuration file for NOFFLE news server
6 6
7 .SH DESCRIPTION 7 .SH DESCRIPTION
206 .TP 206 .TP
207 .B post-locally yes|no 207 .B post-locally yes|no
208 Place articles posted to external servers in the local aticle database 208 Place articles posted to external servers in the local aticle database
209 immediately. Some servers may rewrite Message-IDs, which will cause 209 immediately. Some servers may rewrite Message-IDs, which will cause
210 duplicate postings of this option is enabled. Also, if for some reason 210 duplicate postings of this option is enabled. Also, if for some reason
211 the post to the remote server fails, the article still exist in the local 211 the post to the remote server fails, the article still exists in the local
212 database, which may be a source of some confusion. 212 database, which may be a source of some confusion.
213 .br 213 .br
214 Default: no 214 Default: no
215 215
216 .TP 216 .TP
217 .B replace-messageid yes|no 217 .B replace-messageid yes|no
218 Replace Message-ID of posted articles by a Message-ID generated by 218 Always replace the Message-ID of a posted article with a Message-ID
219 NOFFLE. Some news readers generate Message-IDs that are not accepted by 219 generated by NOFFLE. NOFFLE will always add a Message-ID if none is
220 some servers. For generating Message-IDs, the domain name of your system should 220 present, or replace a Message-ID that does not meet the basic
221 be a valid domain name. If you are in a local domain, set it to your 221 formatting and content requirements for a Message-ID. However, some
222 provider's domain name. 222 news readers may generate Message-IDs that are not accepted by some
223 .br 223 servers (for example the server may insist the Message-ID domain is
224 Default: yes 224 part of the server domain) or may not always be unique. In either of
225 these cases you may prefer to have NOFFLE always replace the
226 Message-ID.
227 .br
228 Default: no
225 229
226 .TP 230 .TP
227 .B hostname <fully.qualified.domain.name> 231 .B hostname <fully.qualified.domain.name>
228 Specify right-hand side of Message-IDs generated by NOFFLE. 232 Specify right-hand side of Message-IDs generated by NOFFLE.
229 If omitted, the fully qualified domain name of your system will be used. 233 If omitted, the fully qualified domain name of your system will be used.