• none (Default style)
• gtk+ (GTK+ style)
• plastic (Aqua style)

Newer FLTK versions may accept additional schemes.

Attention: With some modes it is possible that lines will overlap and characters like underscore are clipped!

This file is not used if another location for the signature file is configured. See CONFIGURATION section below for details (configfile entry "signature_file").

Note: At this (shared) location the file should be US-ASCII encoded. If you want to use Unicode in signatures, a dedicated signature file for flnews should be configured.

The secret in this file must be a cryptographically random value according to RFC 4086 and should be at least 32 octets in length.

flnews must be compiled with support for ssl(3) or this file will be ignored, because the cryptographic functions are shared.

If this file is not present, it is automatically created and a new secret is written to it (using random data from the cryptographic PRNG).

If this file is present and not empty, and the fqdn entry is set, flnews creates "Cancel-Lock" (always) and "Cancel-Key" header fields when canceling or superseding articles.

To use the same secret as another installation of flnews (or another newsreader that use the algorithm recommended by RFC 8315 with HMAC based on SHA256), copy the file with the desired secret to this location.

To manually disable this feature, an empty file must be used.

Attention: Everybody who get his hands on this secret can cancel articles that were locked using this key in the past! This file should be readable only by the user.

The old scheme SHA1 is still supported too. See CONFIGURATION section below for details (configfile entry "cancelkey").

See CONFIGURATION section below for details.

Attention: In any case all newsreaders that share a groupfile must be configured to use the same server! There is a convention to name such files "newsrc-$HOSTNAME" to make it obvious for which server they can be used.

It is allowed to share the groupfile between multiple instances of flnews that run simultaneously. The file will contain the state of the instance that is terminated last.

It is allowed to share the scorefile between multiple instances of flnews that run simultaneously. The file will contain the state of the instance that is terminated last.

See SCORING section below for details.

flnews must be compiled with support for ssl(3) to make this work, because the cryptographic functions are shared.

If this entry and the fqdn entry are set, flnews creates "Cancel-Lock" (always) and "Cancel-Key" header fields when canceling or superseding articles.

Note: The scheme SHA1 is obsolete since RFC 8315. This entry is preserved for backward compatibility. After a transition period this entry should be left empty and the scheme SHA256 should be used. See section above (File "~/.config/flnews/.cancelsecret").

The value must be an 8-bit index for the FLTK colormap:

https://www.fltk.org/doc-1.3/drawing.html#drawing_colors

A nonzero value means that CRL checks are enabled.

flnews must be compiled with support for CRL checks to make this work.

A nonzero value means that, after the CRL update interval has elapsed, the user get a choice to select whether the CRL update should be delayed.

The value must be positive and is a period of time in hours. Too large values (longer than one year) are clamped to the upper limit. The value zero means that new CRLs should be downloaded for every new connection (not recommended).

This entry contains a timestamp in ISO 8601 format for the last successful CRL update.

Setting this to a nonzero value automatically initialize the distribution header field in the composer with suggested distribution data (if available). If no distribution suggestions are available for the target groups, the header field is initialized to "world" as with this option set to zero.

Any time a distribution suggestion is used, the user is informed with a popup window in the GUI.

With the NNTP protocol the command LIST DISTRIB.PATS is used to retrieve the distribution suggestions from the server.

The pathname of an executable program must be specified.

The pathname of a file containing the data is passed as parameter. If the external editor requires additional parameters, a start script must be specified (and the script must provide the additonal parameters).

The editor must be able to process Unicode data in UTF-8 format. The specified editor must terminate with exit status zero on success.

A temporary file is used. Consider to set the TMPDIR environment variable.

Only used if "Format=flowed" is declared.

A value of zero corresponds to the dumb behaviour up to version 0.16 (if a paragraph ends with an empty line, there is no separation to the following text).

A value of one adds an empty line separator after every paragraph that ends with an empty line. This is required to create single line paragraphs (allow single line to be rewrapped to smaller width for display). The author of an article can request this behaviour with the experimental parameter "InsLine=yes" in addition to "Format=flowed".

Must be empty or a valid "dot-atom" according to RFC 5322, this means the nameless root domain must be omitted (no trailing dot).

This entry is used to generate Message-IDs. They are only worldwide unique for all time if flnews runs on a machine with a FQDN. In addition the clock of the machine must be synchronized so that timestamps are not ambigous.

If a FQDN is configured, the header fields "Message-ID", "Injection-Date", "Cancel-Lock" and "Cancel-Key" (only when cancelling or superseding an article) are created by flnews for all outgoing articles. Note that RFC 5537 specifies some nasty details for the "Injection-Date" header field (they are the reason to handle it internally in this case).

With the value zero outgoing articles are converted to ISO 8859-1 if possible. With a nonzero value, all articles are sent using Unicode (UTF-8 transformation format).

The value one represents the default behaviour to authenticate immediately after a connection was established.

The value zero switches the behaviour, so that authentication against the server is only executed after a request to do so (480 response when using NNTP protocol).

The external inews must accept the article on its standard input and inject it into the network. After successful completion of this task it must terminate with exit status zero. In the case of an error, it must terminate with a nonzero exit status.

Note that the article feeded into the external inews has canonical format (CR+LF line breaks).

If your inews needs command line parameters or a different input format, specify a shell script here (and call the external inews from this script).

The content is automatically inserted into the body of every new regular article (that is not a followup, cancel or supersede).

The name of the cited author can be inserted with "%s". The newsgroups list of the cited article can be inserted with "%g". Every variable is allowed only once.

The last character should be a colon.

The value zero is the default behaviour (top down).

A nonzero value inverts the order of articles or thread branches respectively.

This file is imported at startup and used as groupfile. At exit the local groupfile is copied back to this location. Note that this file is replaced with rename(2) and is not modified in place. If the file is accessed via NFS, advisory locking must be available.

Setting this to a nonzero value disables usage of overview and makes the whole newsgroup list usable for scoring rules.

In general the default value 0 should be used. There are two scenarios for which this option may be useful.

If the network connection to the server is very slow and no data compression is available: In this case the transfer of the (larger) overview may be slower than the transfer of a few (smaller) new headers, because the older headers can be taken from the local cache.

If one or more scoring rules should match other (not the current or not subscribed at all) newsgroups in Xposts: Because the newsgroup list is not part of the overview, only the current group is available if the overview is used.

The string is inserted as 'Organization' header field in outgoing articles.

Note: The postprocessor can be used to insert custom header fields.

The postprocessor must be a filter in Unix sense. It must accept the article on its standard input, process it and write the result to its standard output. After successful completion of this task is must terminate with exit status zero. In the case of an error, the postprocessor must terminate with a nonzero exit status.

Note that the article feeded into the postprocessor has canonical format (CR+LF line breaks) and use Unicode UTF-8 encoding for the body. Modifications must preserve this format. The Unicode normalization, potential conversion to the target character set and the application of the transfer encoding to the body is done after the postprocessing. Therefore the postprocessor is not allowed to add "Content-Type" and "Content-Transfer-Encoding" header fields!

The header is already in RFC 2047 format. If the postprocessor modifies an existing header field, this format must be preserved. If a new header field is added, the postprocessor is responsible for creating valid RFC 2047 encoding and Unicode normalization to NFC.

The value zero is the default behaviour and disables the autorefresh feature.

A nonzero value refreshes the group list in the specified interval (in minutes).

This file is imported at startup and used as scorefile. At exit the local scorefile is copied back to this location. Note that this file is replaced with rename(2) and is not modified in place. If the file is accessed via NFS, advisory locking must be available.

Default value: ".signature".

If this file is present, its content is used as signature. The signature separator "dash dash space" plus LF line break is automatically prepended if not already present in this file. The file must be a POSIX text file (LF line break after every line, including the last one) with Unicode encoding in UTF-8 format (Unicode normalization is not important and applied automatically).

Use an empty string to disable signature generation.

If non US-ASCII characters are used in the regular expression, they must be representable in the codeset of the character classification locale used at runtime. Otherwise the regular expression from this entry is ignored and will never match. See the desciption for the LC_CTYPE environment variable above for details.

Note that this regular expression is used for matching against individual group names, not group lists. This means '^' and '$' will match start and end of individual group names.

If a match is detected against a group name, this group is treated as a test group that may require special control commands in the "Keywords" header field to silence e.g. reflector bots (see entry "testgrp_kwords" for keyword configuration).

If a target group of an article is identified as a test group (as described for the "testgrp_ere" entry), the header field "Keywords" is initialized to the value defined with this entry.

Attention: Version 1.2.0 of flnews currently only supports US-ASCII keywords. Do not use spaces around commas.

The value zero represents the default behaviour to append no comment.

The value one switches the behaviour, so that a comment with the name of the timezone is appended to the Date header field. If the operating system does not provide timezone information, this entry is ignored.

With nonzero value the trust anchor (X.509 root certificate) of a certificate chain is searched in the local location only. The system wide certificate store of the OpenSSL installation is ignored.

Local X.509 certificate path: ~/.config/flnews/certs

Copy the root certificate (in PEM format) to a file with arbitrary name in the path specified above. Then run the c_rehash utility to create the symlink that OpenSSL uses for searching.

With zero value searching for next unread article stays in current group.

With nonzero value the next group with unread articles is selected if there are no more unread articles in the current group.

This must be a wildmat according to RFC 3977. The wildmat "*" will match all groups.

The following types (in alphabetical order) are recognized by version 1.2.0.

Type "from": The string from the fourth field must match literally against the "From" header field.

Type "from_ere": The string from the fourth field is interpreted as a POSIX.2 extended regular expression and must match against the "From" header field.

Type "group": The string from the fourth field must match literally against a group element in the "Newsgroups" header field.

Type "msgid_ere": The string from the fourth field is interpreted as a POSIX.2 extended regular expression and must match against the "Message-ID" header field.

Type "subject": The string from the fourth field must match literally against the "Subject" header field.

Type "subject_ere": The string from the fourth field is interpreted as a POSIX.2 extended regular expression and must match against the "Subject" header field.

Note that rules using wildmats (other than "*") and/or regular expressions are ignored if flnews is compiled without support for regular expressions.

This must be a signed integer value. If the scorefile is shared between multiple instances of flnews, the values must be usable for the whole group. The machine with the smallest limits will clamp the values if they are too large or too small respectively.

This must always be an Unicode string (in UTF-8 format with NFC normalization).

Attention: If the normalization is wrong, the rule may not match as intended!

The colon has no special meaning inside this field anymore and must not be quoted for any of the rule types listed above.

Unicode is a registered trademark of Unicode, Inc. in the United States and other countries.

If compiled with support for TLS.

If compiled with support for TLS (as replacement for OpenSSL).

If compiled with support for compression.