Mercurial > noffle

comparison docs/noffle.conf.5 @ 494:372f8b55506e noffle

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[svn] Apply patch from Jan De Luyck. Add new option 'add-messageid-if-missing', which optionally postpones adding a message ID to the upstream server. If this is done, post-locally must be off. This is to deal with an upstream server troubling Jan. It usually (but not always) rejects posts with a Noffle message ID. I have changed Jan's original option of 'add-message-id-if-missing' for consistency with 'replace-messageid' and added the manual page entry. See SourceForge feature request 1513395.
author bears
date Wed, 12 Jul 2006 20:26:41 +0100
parents fb8cadeed4d4
children 614a3177b15c
comparison
equal deleted inserted replaced
493:4d3a1597813a 494:372f8b55506e
1 .TH noffle.conf 5 1 .TH noffle.conf 5
2 .\" $Id: noffle.conf.5 619 2003-10-31 15:54:59Z godisch $ 2 .\" $Id: noffle.conf.5 645 2006-07-12 19:26:41Z 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
233 Default: no 233 Default: no
234 234
235 .TP 235 .TP
236 .B replace\-messageid yes|no 236 .B replace\-messageid yes|no
237 Always replace the Message-ID of a posted article with a Message-ID 237 Always replace the Message-ID of a posted article with a Message-ID
238 generated by NOFFLE. NOFFLE will always add a Message-ID if none is 238 generated by NOFFLE. NOFFLE by default adds a Message-ID if none is
239 present, or replace a Message-ID that does not meet the basic 239 present. However, some news readers may generate Message-IDs that are
240 formatting and content requirements for a Message-ID. However, some 240 not accepted by some servers (for example the server may insist the
241 news readers may generate Message-IDs that are not accepted by some 241 Message-ID domain is part of the server domain) or may not always be
242 servers (for example the server may insist the Message-ID domain is 242 unique. In either of these cases you may prefer to have NOFFLE always
243 part of the server domain) or may not always be unique. In either of 243 replace the Message-ID.
244 these cases you may prefer to have NOFFLE always replace the
245 Message-ID.
246 .br 244 .br
247 Default: no 245 Default: no
246
247 .TP
248 .B add\-messageid\-if-missing yes|no
249 NOFFLE by default will always add a Message-ID a posted article if the
250 article does not have a Message-ID. This is required if
251 .B post\-locally
252 is set. However, some news servers in the wild have been observed
253 to prefer to assign their own Message-IDs, to the extent of often
254 rejecting posts with perfectly legitimate Message-IDs. If you are
255 unfortunate enough to be confronted by one of these beasts, you can
256 change
257 .B add\-messageid\-if-missing
258 to
259 .B no
260 to leave adding a Message-ID to the upstream server. If you do this,
261 you
262 .B must
263 also set
264 .B post\-locally
265 to
266 .B no
267 or posting an article without a Message-ID will generate an error.
268 .br
269 Default: yes
248 270
249 .TP 271 .TP
250 .B hostname <fully.qualified.domain.name> 272 .B hostname <fully.qualified.domain.name>
251 Specify right-hand side of Message-IDs generated by NOFFLE. 273 Specify right-hand side of Message-IDs generated by NOFFLE.
252 If omitted, the fully qualified domain name of your system will be used. 274 If omitted, the fully qualified domain name of your system will be used.