yamo' wrote:
flnews has a good functionality : handle the Archive header
but not the classical XNAY.
Is it configurable?
There is no direct support, but the postprocessor feature can be used
to add additional headers.
Check the documentation for the entry "post_proc" in "configfile".
Example for a POSIX script "~/.config/flnews/pp_script.sh": ------------------------------------------------------------------------
#! /bin/sh
# Abort on error
set -e
# Set locale with UTF-8 encoding for awk
# Note: The filter will be feeded with whole article (body is always UTF-8 encoded)
export LC_ALL=en_US.UTF-8
# Process article
awk -v i=0 '/^Archive: no\r$/ { print ; if(!i) print "X-No-Archive: yes\r" ; i=1 ; next } /^\r$/ { i=1 } { print }'
------------------------------------------------------------------------
The locale name "en_US.UTF-8" must be modified to match an existing
locale of your system (that uses UTF-8 encoding).
Check with "locale -a" what your system offers.
awk looks for the header field "Archive: no" (as defined in RFC 5536)
and prints the nonstandard "X-No-Archive: yes" only if it is present.
This is done only once and only in the header of the article.
The postprocessor script must have the executable bit set and the
following entry in "configfile" tells flnews to execute it before
an article is sent:
|
| post_proc: /home/micha/.config/flnews/pp_script.sh
^^^^^^^^^^^^^^^^^^^
Modify this part to match your system.
If the checkbox for "Archive" in the GUI is deactivated, both headers
are added now.
A spell checker would also be great!
Currently not on the roadmap, but an external editor can be used (that
provides that feature).
Check the documentation for the entry "editor" in "configfile".
Example:
|
| editor: /usr/pkg/bin/xnedit
Attention:
The editor must support (and be configured for) UTF-8 encoding.
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)