.\" Automatically generated by Pod::Man 4.14 (Pod::Simple 3.43) .\" .\" Standard preamble: .\" ======================================================================== .de Sp \" Vertical space (when we can't use .PP) .if t .sp .5v .if n .sp .. .de Vb \" Begin verbatim text .ft CW .nf .ne \\$1 .. .de Ve \" End verbatim text .ft R .fi .. .\" Set up some character translations and predefined strings. \*(-- will .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left .\" double quote, and \*(R" will give a right double quote. \*(C+ will .\" give a nicer C++. Capital omega is used to do unbreakable dashes and .\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff, .\" nothing in troff, for use with C<>. .tr \(*W- .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p' .ie n \{\ . ds -- \(*W- . ds PI pi . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch . ds L" "" . ds R" "" . ds C` "" . ds C' "" 'br\} .el\{\ . ds -- \|\(em\| . ds PI \(*p . ds L" `` . ds R" '' . ds C` . ds C' 'br\} .\" .\" Escape single quotes in literal strings from groff's Unicode transform. .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. .\" .\" Avoid warning from groff about undefined register 'F'. .de IX .. .nr rF 0 .if \n(.g .if rF .nr rF 1 .if (\n(rF:(\n(.g==0)) \{\ . if \nF \{\ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . if !\nF==2 \{\ . nr % 0 . nr F 2 . \} . \} .\} .rr rF .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. . \" fudge factors for nroff and troff .if n \{\ . ds #H 0 . ds #V .8m . ds #F .3m . ds #[ \f1 . ds #] \fP .\} .if t \{\ . ds #H ((1u-(\\\\n(.fu%2u))*.13m) . ds #V .6m . ds #F 0 . ds #[ \& . ds #] \& .\} . \" simple accents for nroff and troff .if n \{\ . ds ' \& . ds ` \& . ds ^ \& . ds , \& . ds ~ ~ . ds / .\} .if t \{\ . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u" . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u' . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u' . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u' . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u' . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u' .\} . \" troff and (daisy-wheel) nroff accents .ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V' .ds 8 \h'\*(#H'\(*b\h'-\*(#H' .ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#] .ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H' .ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u' .ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#] .ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#] .ds ae a\h'-(\w'a'u*4/10)'e .ds Ae A\h'-(\w'A'u*4/10)'E . \" corrections for vroff .if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u' .if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u' . \" for low resolution devices (crt and lpr) .if \n(.H>23 .if \n(.V>19 \ \{\ . ds : e . ds 8 ss . ds o a . ds d- d\h'-1'\(ga . ds D- D\h'-1'\(hy . ds th \o'bp' . ds Th \o'LP' . ds ae ae . ds Ae AE .\} .rm #[ #] #H #V #F C .\" ======================================================================== .\" .IX Title "NEWSGROUPS 5" .TH NEWSGROUPS 5 "2022-07-10" "INN 2.7.2" "InterNetNews Documentation" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l .nh .SH "NAME" newsgroups \- List of newsgroups and their short descriptions .SH "DESCRIPTION" .IX Header "DESCRIPTION" The file \fIpathdb\fR/newsgroups contains a list of newsgroups for which a short description is available. This file is generally updated by \&\fBcontrolchan\fR\|(8) whenever a control message is received; it is used by \&\fBnnrpd\fR in response to \s-1LIST NEWSGROUPS\s0 and is only meant to provide information to users. News readers often show the list of carried newsgroups along with these descriptions. .PP It is not necessary that all the groups carried by the news server (that is to say all the groups listed in the \fIactive\fR file) be listed in the \fInewsgroups\fR file. And it is also not necessary that all the groups listed in the \fInewsgroups\fR file be carried by the news server. Nonetheless, it is of course better if the \fIactive\fR and \fInewsgroups\fR files have exactly the same newsgroups. .PP If you use \f(CW\*(C`ctlinnd newgroup\*(C'\fR to manually create a group, only the \&\fIactive\fR file is updated. You should then edit the \fInewsgroups\fR file in order to add a short description for the created group. The same goes for manually removing or changing the status of a newsgroup. .PP Each line of the \fInewsgroups\fR file consists of two fields separated by at least one tabulation: .PP .Vb 1 \& \et .Ve .PP The first field is the name of the newsgroup. The second field is its description. .PP You can get the \fInewsgroups\fR file of another \s-1NNTP\s0 server with \fBgetlist\fR\|(1). .SH "PREFERRED FORMAT FOR A ONE-LINE NEWSGROUP DESCRIPTION" .IX Header "PREFERRED FORMAT FOR A ONE-LINE NEWSGROUP DESCRIPTION" As far as the format of the \fInewsgroups\fR file is concerned, there is a preferred format for each line. Since news administrators do not generally have the time to fix up the lines that are being automatically included from newgroup or checkgroups messages, this information is provided so that control message senders can craft better control messages. It will also be useful for news administrators to know how to format the description of their local newsgroups. .PP There should be at least one hard tab (8 column tab stops) between the group name and the description. If the group name is at least 16 characters, it should be followed with one tab. If the group name is at least 8 characters, it should be followed with two tabs. And in the unlikely event the group name is less than 8 characters, it should be followed with three tabs. For instance: .PP .Vb 3 \& misc.transport.rail.europe Railroads & railways in all of Europe. \& news.admin.nocem NoCeM protocol policy issues and information. \& news.groups Discussions and lists of newsgroups. .Ve .PP The total line length should be at most 79 columns. The description should start with a capital and not be more than 55 characters (79 \- 24) long. If the group name is longer than 24 characters, the description should be correspondingly shorter. If the group is moderated, it should have \f(CW\*(C` (Moderated)\*(C'\fR (note the space before the opening parenthesis) at the very end of the description, not counted as part of the length of the description. This text must be exactly that, with no variations, as it is used by news software to find moderated groups. .PP Here is an example of moderated newsgroup: .PP .Vb 1 \& news.lists.misc News\-related statistics and lists. (Moderated) .Ve .PP Traditionally, all newsgroup descriptions ended with a period, but this is not necessary and steals away one character that is occasionally useful for forming a better description. .PP Some over-long descriptions could be made to easily fit the length by dropping useless wordings like \f(CW\*(C`Discussion of\*(C'\fR which do not meaningfully contribute to the description. Others are usually pretty easy to get to no more than column eighty, except when the group names start getting really long. Hopefully then the group name itself contains quite a bit of description. .PP In some cases, a longer description really will be necessary; they can of course be used within the \fInewsgroups\fR file. However, they will probably be less readable and less useful for some Usenet users. .PP Descriptions must not contain any control characters (octets between 0x00 and 0x1F). .SH "ENCODING OF THE DESCRIPTIONS" .IX Header "ENCODING OF THE DESCRIPTIONS" There is, at present, no good mechanism for managing the character set of the newsgroup descriptions. Many non-English hierarchies include newsgroup descriptions in their native languages, since this is more useful for their users, and those are included verbatim in the \&\fInewsgroups\fR file. This unfortunately means that different lines of the file will require different character set settings to read properly, and those character sets are not documented in the file. Hopefully some future standard will provide a way to address this; in the meantime, using \s-1UTF\-8\s0 for non-ASCII characters is recommended. .SH "MINIMAL NEWSGROUPS FILE" .IX Header "MINIMAL NEWSGROUPS FILE" The minimal \fInewsgroups\fR file shipped with \s-1INN\s0 is: .PP .Vb 6 \& control Various control messages (no posting). \& control.cancel Cancel messages (no posting). \& control.checkgroups Hierarchy check control messages (no posting). \& control.newgroup Newsgroup creation control messages (no posting). \& control.rmgroup Newsgroup removal control messages (no posting). \& junk Unfiled articles (no posting). .Ve .PP These lines \fImust\fR be tab-delimited, so please be careful in case you copy and paste them from above. .SH "HISTORY" .IX Header "HISTORY" Written by Julien Elie for InterNetNews. The preferred format for a one-line newsgroup description is based on the policies by which the \fInewsgroups\fR file in is maintained; they were originally written by David Lawrence and updated by Russ Allbery . .SH "SEE ALSO" .IX Header "SEE ALSO" \&\fBactive\fR\|(5), \fBcontrolchan\fR\|(8), \fBctlinnd\fR\|(8), \fBgetlist\fR\|(1), \fBnnrpd\fR\|(8).