* New configuration keyword <item>_alldb

This keyword is valid for backup items of mysql type.  If dumping all
databases is requested (i.e. the <item>_database variable is not
defined), it configures whether to dump each database into a separate
file (named after it), or to dump all databases to a singe file.

* Fix restoring from remote archives
	  

* Licensed under GPLv3 or later.

* mixal

** Location of listing file

By default, mixal creates listing file in the current working directory.

* mixsim

** The .mixsim file
When started in terminal mode, the utility searches for file `.mixsim'
in the current working directory and reads it, if present. The file
may contain any mixsim commands.

** The set of terminal commands is improved to make it compatible with GDB.

** New command, PASSCOUNT
Set the number of crossings after whcih to clear the breakpoint.

** Removed optional second argument to BREAK.
The functionality of `BREAK <ADDR> <COUNT>' is now obtained by two
commands:

BREAK <ADDR>
PASSCOUNT <N> <COUNT>

** New command DELETE.
An alias to CLEAR.

** New command IGNORE
Sets the number of hits to ignore before enabling the breakpoint.

** New commands ENABLE and DISABLE
Enable or disable the breakpoint with the given number.

** New command RUN
It is an alias for GO.

** New command SOURCE
Execute a file of mixsim commands.

** New command ADDRESS.
This command takes as its argument a breakpoint manipulation command
(DELETE, IGNORE, ENABLE, DISABLE, PASSCOUNT) with arguments
appropriate for the associated command.  However, the first argument
of the corresponding command is treated as MIX address, instead of a
breakpoint number.

** New command INFO.
An alias to LIST.

** New command SHELL.
Executes a subordinate shell or a shell command. Abbreviated to !.

** NEXT and STEP take optional argument.
The argument, if given, specifies number of instructions to
execute. Default is 1.

** INFO BREAK takes an optional argument specifying breakpoint number to list.
If prefixed with ADDRESS, it treats the argument as a MIX location and
lists all breakpoints set on that location.

	  

* Configuration file raddb/config

The syslog statement takes an optional 4th argument specifying syslog
tag to use, e.g.:

    channel default {
	    syslog local1.info radiusd;
    };

* New attributes

** GNU-Server-Address

Holds IP address of the RADIUS server that recieved the
request. Notice, that the value of this attribute is "0.0.0.0" if
there are no `listen' statement in your `raddb/config'.
    
** GNU-Server-Port

Holds UDP port number of the RADIUS server that recieved the request.

* Automake function AM_GNU_RADIUS is provided, for checking if
GNU Radius is installed from configure.ac scripts.

* Guile support requires Guile version 1.8 or later.

* Bugfixes
** Pass NAS-IP-Address to mlc_stop_query	
	
	  

Initial release.

	  

* Use IPv6 URLs as proposed by RFC 2732

The address part of an IPv6 URL must be either an IPv6 address in
numeric notation *enclosed in square brackets* or a host name, e.g.:

  inet6://[::1]:1100

  
	  

First actual release.

	  

* Support SNMPv3
* Default SNMP version is 2c
* Use newer Grecs
* Drop unneeded dependencies
* Variable assignments in expressions
* Detection of SNMP counter overflows
* Comma operator
* Support for indexed MIBs

This feature allows you to use symbolic names instead of the fixed MIBs
for MIBs that are part of SNMP subtrees.  For example, to get number of
packets sent over eth0 into variable "out", you would do the following:

    table iftable IF-MIB::ifDescr;
    variable out "IF-MIB::ifOutUcastPkts.$iftable[eth1]";

The first statement converts the subtree into a "table" named "iftable".
The second statement references an entry in this table that has
the value "eth1".  For example, if the SNMP tree has the following MIB

    IF-MIB::ifDescr.10: eth0

then the expression "$iftable[eth]" yields "10"

* Assertion syntax changed.

The assertion statement takes a single argument, which must be a
string consisting of the following three parts:

   <oid: string> [!]<opcode>[/i] <value: string>

The <opcode> part can be either an arithmetical operator (=, <, <=, >,
>=), or any of the following string operators:

    eq          string equality
    ne          string inequality
    prefix      oid value must begin with <value>
    suffix      oid value must end with <value>
    glob        <value> is a glob(7) pattern that oid value must match
    
Each of these can be suffixed with "/i" to request case-insensitive comparison.

A "!" in front of opcode reverts its meaning.   

The <value> part must not include the type prefix.

	  

* The program is installed in /usr/bin

Prior versions went to /usr/sbin, you will need to remove them
manually.

* Print /etc/issue before the prompt
* Sleep after incorrect password is input
* New options: -i (--issue), -s (--sleep), -c (--clear)
* Add a manpage
* Improve error checking and reporting
	  

** New operation mode: proxy

** Command line option precedence

Command line options take precedence over configuration file
statements.

** elif statement

A familiar `elif' statement is supported, e.g.:

if condition-1
  action-list-1
elif condition-2
  action-list-2
elif condition-3
  action-list-3
else
  action-list-4
fi
  
** New CONTROL statement esmtp-auth-delayed.

When set to `yes', this statement instructs Anubis to postpone ESMTP
authentication until MAIL command is issued by the client.  This
allows to change authentication credentials in the SMTP section (see
below).

** SMTP section

The new section "SMTP" is invoked each time an SMTP command
is received. This section may alter the command's argument, using the
"modify command", e.g.:

BEGIN SMTP
regex :extended
modify command [ehlo] "foo.bar.net"
if command ["mail from:"] "<(.*)>(.*)"
  modify command ["mail from:"] "<root@bar.net>\2"
fi
END

It is also allowed to use esmtp-* keywords in this section, provided
that `esmtp-auth-delayed yes' is set in the CONTROL section. Changes
in the ESMTP authentication credentials take effect if they occur
either before receiving MAIL command from the client, or when handling
this command, e.g.:

BEGIN SMTP
if command ["mail from:"] "<smith(\+.*)?@@example.net>"
  esmtp-auth-id smith
  esmtp-password guessme
else
  esmtp-auth no
fi
END

** New keywords: log-facility and log-tag

** Guile output

By default Scheme's standard error and output ports are redirected to
syslog, using priorities `err' and `warning' correspondingly.

** MySQL options file

When using MySQL for Anubis user database, the database parameters and
access credentials are read from the file /etc/my.cnf, section
"anubis".  Additionally, two URL parameters are provided:
"options-file", which sets the name of the options file, and
"options-group", which sets the name of the group.

	  

* ftp

An old inability to allow other names than the canonical name has
been corrected.  This means that a machine entry in the .netrc file
will now be used as expected.  Previously any alias name was replaced
by the corresponding canonical name, before reading the .netrc file.

The internal command `hash' accepts a suffixed letter to the size
argument, like `12k', instead of 12288.  Made a minor change to the
syntax of the command itself, allowing size changes independently
of activation of hash markings.  After a transfer the summary gives
the speed as `Mbytes/s', `kbytes/s', or `bytes/s'.

The .netrc file can be overridden by the environment variable NETRC.
Of even higher precedence is the new option `-N/--netrc'.  The access
to the resulting file, whatever method, is now denied unless it is a
regular file.

* ifconfig

Better command line parsing on BSD and Solaris systems.  Touch only
changeable flags on all systems.

* logger

The ability to use numerical facilities is restored to full range.

* ping, ping6

The ability to specify a pattern as payload is corrected.

* syslogd

A new switch `-T/--local-time' makes the service ignore a time
stamp passed on by the remote host, recording instead the local
time at the moment the message was received.  As a short form of
`--pidfile', the switch `-P' is new.

In common with other syslogd implementations, rsyslogd and sysklogd,
there has for a long time existed an attack vector based on large
facility numbers, made public in CVE-2014-3684.  This is now mended
in our code base.

* telnetd

The ability to autologin a client, without using authentication,
is now functional in the expected manner, i.e., the prompt for a
user name is suppressed in favour of an immediate password prompt.

In a setting where the client is using a UTF-8 encoding, it was
common to observe strange characters in most responses.  This was
caused by the server daemon, due to incomplete purging of internal
protocol data.  The issue should now be resolved.

* whois

Improved cooperation with servers like `whois.arin.net', `whois.eu',
and `whois.ripe.net'.
	  

* Convert textual frames to/from the currently used character set

The character set is deduced from the locale settings.  It can also be
set explicitly using the --charset option.

* New option --broken-8bit-encoding

Use this option for files where textual frames are stored as
ISO-8859-1, but are actually using another 8-bit encoding.  The
argument to this option is the name of the enchoding actually used.

In query mode, this option helps display such frames properly.

Use it with the --fixup option to fix such frames in the file.

* New option --encoding

Specifies encoding to store textual frames in ID3 tags.

* New option --fixup

Modifies the ID3 v2 tag so that it can be understood by most devices.

* The --convert option can be used to remove unnecessary ID3 formats.

For example, if the file input.mp3 contains both version 1 and 2 tags,
the following will remove version 1 tags:

  idest --convert=2 input.mp3

* Fix processing of unknown frames.

* Fix operation of setpic and pic modules with Guile 2.x.

* Improve documentation

	  

Don't throw exception on invalid tokens.
  Fix python 3 compatibility
	  

* Implement heartbeat event

* Add auxiliary program: ifactive

* Fix file descriptor leak

	  

Convert byte-like objects to UTF-8 strings.
	  

Rewrite as a stand-alone snmpd agent.

	  

* Bugfixes and organizational changes

	  

Initial release.

	  

Initial release.

	  

Initial release.

=========================================================================
Copyright information:

Copyright (C) 2016-2019 Sergey Poznyakoff

   Permission is granted to anyone to make or distribute verbatim copies
   of this document as received, in any medium, provided that the
   copyright notice and this permission notice are preserved,
   thus giving the recipient permission to redistribute in turn.

   Permission is granted to distribute modified versions
   of this document, or of portions of it,
   under the above conditions, provided also that they
   carry prominent notices stating who last changed them.

Local variables:
mode: outline
paragraph-separate: "[  ]*$"
eval: (add-hook 'write-file-hooks 'time-stamp)
time-stamp-start: "changes. "
time-stamp-format: "%:y-%02m-%02d"
time-stamp-end: "\n"
end:
	  

Initial release.
	  

* Fix CVE-2015-1197
* Fix CVE-2016-2037
* Fix CVE-2019-14866
	  

* Minor fixes in mysqlstat-setup
* Provide default values for NULL columns
	  

* Drop support for Varnish versions prior to 6.0.0

	  

Fix handling of archivation requests.

	  

* New command line option --done (-d)

This option is a counterpart of --init and supplies a cleanup
expression, i.e. an expression that will be evaluated when the
main loop has iterated over all nodes in the tree.

* New parser: DHCPD

A parser for dhcpd.conf file.

* Drop support for Guile versions prior to 2.2.0

	  

	- Change bugtracker address.

	  

* Fix parsing of po header fields

* Use the Language header instead of Language-Team.

Support for Language-Team and language tables is retained for
backward compatibility.

* Organizational change: repository moved to git

The repository along with links for cloning can be viewed online at
http://git.gnu.org.ua/cgit/wyslij-po.git.

See https://puszcza.gnu.org.ua/git/?group=wyslij-po for instructions.
	  

* Change bugtracker address.

	  

	- Change bugtracker address.

	  

	- Change bugtracker address.
	  

	- Change bugtracker address.

	  

	- Change bugtracker address.
	
	  

* Change bugtracker address.

	  

	- Change bugtracker address
	
	  

* Fix extraction over pipe (savannah bug #60002)

* Fix memory leak in read_header (savannah bug #59897)

* Fix extraction when . and .. are unreadable

See https://lists.gnu.org/archive/html/bug-tar/2021-01/msg00012.html

* Gracefully handle duplicate symlinks when extracting

See https://lists.gnu.org/archive/html/bug-tar/2021-01/msg00026.html

* Re-initialize supplementary groups when switching to user privileges
	  

* Change bugtracker address.

	  

	- Change bugtracker address
	  

* New configuration statement: sentinel

The "sentinel" statement declares the name of a file which, when
present in the destination directory, informs vcsync that this
directory is exempt from the normal synchronization process.  The
presense of the sentinel file is an indication that the destination
directory is updated by other means.

* Full documentation added

	  

	- Fix packaging
	
	  

* Use explicit DESTROY with AUTOLOADs

	  

* Bugfixes in the gcide module

* Fix searches in the gcider utility

* Support for Python 2 has been withdrawn

	  

* Syslog support

New option '-S FACILITY' switches diagnostic output to the given
syslog facility.

	  

* Support for Guile 2.2

* Bugfixes

* Improved testsuite

	  

* Fix the --timeout option

	  

	- Fix operation without -d option
	
	  

* Appending cronjob output to a file

Output of a cronjob can be captured and appended to a disk file,
instead of sending it via email or logging it using syslog.  This is
controlled by the _MICRON_OUTFILE (global) and _JOB_OUTFILE (per-job)
built-in variables.

* New option -P FILE

Writes PID of the running process to FILE.  The file will be removed
when the program terminates.

* Option -v replaces -o

To set initial value of a built-in variable, use the "-v NAME=VALUE"
option.

* The -V option

To obtain the micrond version, use the -V option.

* Bugfixes

** Fix allocation of environment and built-in variables defined in crontabs.
	  

* tallyman: if passed empty service ID, don't attempt to contact the collector

	  

* Multiple start functions are allowed

The '--main' option can be given multiple times.  A separate graph
will be drawn for each function given as its argument.

* New option --target=FUNCTION

If this option is given, the produced graph will contain only paths
leading from start function (or functions) to the given FUNCTION.

Multiple '--target' options are allowed.

* New output format: dot

The '-f dot' (or '--format=dot') option instructs cflow to output
graph as a description in DOT language, suitable as input to graphviz
programs.

* cflow-mode: new commands for navigating in the graph:

  c   go to the calling function
  n   go to the next function at the same nesting level
  p   go to the previous function at the same nesting level

* Bugfixes:

** CVE-2019-16165
** CVE-2019-16166
** Fix parsing of K&R style function declarations
** Improve parsing of typecasts
** Fix recursive call detection

	  

* Introduce compound events

The "change" event is implemented on GNU/Linux and FreeBSD.  This
event is delivered when a file was modified and closed.

* New configuration statement for manipulating the environment.

The "environ" statement is now a compound statement. It can contain
five kinds of substatements: "clear" to clear the environment, "keep"
to retain certain variables while clearing the environment, "set" to
set a variable, "unset" to unset a variable or variables, and "eval"
to evaluate a variable reference for side effects.

Both "keep" and "unset" can take globbing pattern as their argument,
in which case they affect all variables matching that pattern. 

The value part in the "set" statement is subject to variable
expansion.

The "environ" block can appear in global context as well.  In this
case it applies to all watchers.

The support for the old one-line "environ" syntax is retained for
backward compatibility.

* Variable expansion in arguments to some configuration statements.

Both macro and environment variables are expanded in arguments to all
substatements of the new "environ" block statement and in the argument
to the "command" statement.  In the latter case, expansion of the
environment variables is controlled by the "shell" option.  If the
option is set, the variable will be expanded by the shell.  Otherwise,
they are expanded by direvent prior to invoking the command.

* Rewrite the recursive watching support

In particular, this fixes the bug where recursive watchers silently
assumed that the "create" generic event was configured for the
watcher.

* Change interface for bulk closing of file descriptors

To speed up launching of the user commands, system-dependent
interfaces for closing the file descriptors above the given one are
used, if available.
	  

* Bucket cache switched from balanced tree to hash table

Change suggested by Terence Kelly.

* Speed up flushing the changed buckets on disk

* New option codes for gdbm_setopt

** GDBM_GETDBFORMAT

Return the database format.

** GDBM_GETDIRDEPTH

Return the directory depth, i.e. the number of initial (most significant)
bits in hash value that are interpreted as index to the directory.

** GDBM_GETBUCKETSIZE

Return maximum number of keys per bucket.

** GDBM_GETCACHEAUTO

Return the status of the automatic cache adjustment.

** GDBM_SETCACHEAUTO

Enable or disable automatic cache adjustment.
	  

* Implement the terminate-instances command.
* Implement MoveAddressToVpc (addr2vpc) and RestoreAddressToClassic (addr2ec2).
* Fix rmaddr -v.
* Document chvol and lschvol commands.
* Implement ModifyVolume and DescribeVolumesModifications.

	  

* Hostgroup stack

Rex now maintains a stack of hostgroups.  Once you push a hostgroup
name on stack, that hostgroup will be used by any subsequent rex
command, unless it is given the -g option.  The new command "group"
(see below) provides ways to pop items off the stack, swap arbitrary
element with the top of stack, select new hostgroups on the fly, etc.

* New command: rex group

The "rex group" command has the following forms:

  rex group push GROUP
    Push GROUP on stack.

  rex group pop
    Pop the topmost group off the stack.

  rex group swap N
    Exchange top of the stack with the Nth element (0-based).

  rex group drop N
    Remove Nth element from the stack.

  rex group select COMMAND ARGS...
    Create on top of the stack a temporary group that contains
    those hosts from the current hostgroup where the supplied
    shell command returns success, i.e. exits with code 0.

  rex group show
    List the contents of the hostgroup stack.

* Add configuration function for overriding PTR records from rc files
	  

* mbox format: don't count terminating empty line as part of the message

* Improve performance of the Sieve fileinto action

* Improve efficiency of operations on flat mailboxes in append mode

* Bugfixes in quoted-printable and fromrd filters

* Variois fixes in mbox and dotmail format libraries

* Fix compilation with flex version 2.6.1
	  

* Support for Slackware 15.0
	  

* pam_fshadow: skip-password option

Based on the proposal of Mirsad Goran Todorovac, the new option
skip-password instructs pam_fshadow to check whether the user
being authenticated is present in the passwd and/or shadow files,
without verifying his password.  This way pam_fshadow can be used as
an auxiliary module in the stack, actual authentication being
performed by one of the modules before it.
	  

	- Handle the 'resolvers' section.
	- New class methods for declaring (and undeclaring) sections.
	- Fix changing the argv of a Node.
	  

* Support for Varnish 7.1
	  

* Fix invalid memory addressing in remopt command

* Fix building with flex >= 2.6.1 (EOF check)
	  

* New configuration keywords

** sigterm SIG

Available for use in "component" sections.  This statement defines
signal which pies should send to the running component instance in
order to terminate it.  Defaults to SIGTERM.

* Fix the component shutdown sequence

The shutdown sequence is determined taking into account dependencies
between components, so that all dependent components are stopped
before their prerequisite components.

* Fallback log file

Fallback log file is a place where pies writes out of band log messages,
i.e. messages about not being able to open syslog socket or send logs
to it.  Regular log messages are diverted to this file if syslog was
requested, but cannot be used because of a permanent error.

* Bugfixes

** Fix piesctl config reload

** Fix configuration preprocessing.

** Varios fixes in REST API server.
	  

* Support for Varnish 7.1
* Drop support for Varnish versions prior to 6.0.0
	  

* Support for Varnish 7.1
	  

* Support for Varnish 7.1
	  

* Support for Varnish 7.1
	  

* Support for Varnish 7.1
	  

* Support for Varnish 7.1
* Drop support for Varnish versions prior to 6.0.0.
	  

* Support for Varnish 7.1
	  

* Fix https://puszcza.gnu.org.ua/bugs/?562
	  

Fix deadlock.
	  

Initial release.

=========================================================================
Copyright information:

Copyright (C) 2022 Sergey Poznyakoff

   Permission is granted to anyone to make or distribute verbatim copies
   of this document as received, in any medium, provided that the
   copyright notice and this permission notice are preserved,
   thus giving the recipient permission to redistribute in turn.

   Permission is granted to distribute modified versions
   of this document, or of portions of it,
   under the above conditions, provided also that they
   carry prominent notices stating who last changed them.

Local variables:
mode: outline
paragraph-separate: "[  ]*$"
eval: (add-hook 'write-file-hooks 'time-stamp)
time-stamp-start: "changes. "
time-stamp-format: "%:y-%02m-%02d"
time-stamp-end: "\n"
end:
	  

* Default MFL source file suffix

The default suffix for MFL files is changed to '.mfl'.  In particular,
the master script file is now "mailfromd.mfl".  This change is
intended to avoid confusion with Metafont files, which have suffix
'.mf'.

As of this version, the new suffix is recommended, but not obligatory:
the legacy '.mf' suffix is still supported.  If a file 'X.mfl' is not
found, mailfromd will look for 'X.mf'.

* MFL module search path

MFL modules loaded using the "require" or "import" statements are
looked up in module search path.  Previously, they were searched for
in include search path, which created confusion, since include
search path is intended for use by preprocessor.  To maintain backward
compatibility, if mailfromd is unable to find a module in module
search path, it will retry the search using include path.  This
behavior will be maintained during a transitional period (a couple of
releases), after which searches in include search path will be
discontinued.

* Preprocessor configuration

Use of preprocessor is configured by the following statement in the
main configuration file:

  preprocessor {
    # Enable preprocessor.
    enable yes;
    # Preprocessor command line stub.
    command "m4 -s";
    # Pass current include path to the preprocessor via -I options.
    pass-includes false;
    # Pass to the preprocessor the feature definitions via -D options
    # as well as any -D/-U options from the command line.
    pass-defines true;
    # Name of the preprocessor setup file.  Unless absolute, it is
    # looked up in the include path.
    setup-file "pp-setup";
  }

If preprocessor.pass-includes is true, the preprocessor.command
setting is augmented by zero or more -I options, thereby supplying it
the mailfromd include path.

Furthermore, if preprocessor.pass-defines is set, zero or more
-D options defining optional features are passed to it (e.g.
-DWITH_DKIM) as well as any -D and -U options from the mailfromd
command line.

Unless the value of preprocessor.setup-file begins with a slash,
the file with this name is looked up in the current include search
path.  If found, its absolute name is passed to the preprocessor as
first argument.

If the value begins with a slash, it is passed to the preprocessor
as is.

* New MFL operator: $@

The $@ operator can be used as the last argument in a call to
variadic function from another variadic function.  It passes
all variable arguments supplied to the calling function on to
the function being called.  E.g.:

    func x(...)
    do
      # do something
    done

    func y(string x, ...)
    do
      x($@)
    done

In this example, if "y" is called as y("text", 1, 2, 3) it will call
"x" as x(1, 2, 3).

This operator can also be used with a numeric argument: $@(N).  In
this case, it will remove first N elements from the argument list and
push remaining ones on stack.  This is similar to the 'shift'
operator in other programming languages, e.g.:

    x($@(2))

* Data types in variadic function declaration

The ellipsis in a variadic function declaration can be preceded by
the data type, e.g.:

  func sum (number ...) returns number

For compatibility with previous versions, if the type is omitted,
string is assumed.

* The void() type cast

The void() type cast can be used around a function call to indicate
that its return value is ignored deliberately.

* mfmod: dynamically loaded modules

This new type of mailfromd modules uses dynamically loaded libraries
to extend the program functionality without having to modify its code.
For a detailed discussion see the manual, section 4.22, "Dynamically
Loaded Modules".

Three mfmods exist at the time of this writing:

  - https://www.gnu.org.ua/software/mfmod_ldap/
    LDAP searches.

  - https://www.gnu.org.ua/software/mfmod_openmetrics
    Open metrics support.

  - https://www.gnu.org.ua/software/mfmod_prce/
    Support for Perl-comparible regular expressions.

* Syntax of special handler definitions

Special handlers ("begin" and "end", in particular) are now defined using
the standard "prog" keyword (similar to milter state handlers):

  prog begin
  do
    ...
  done

  prog end
  do
    ...
  done

Old syntax is supported for backward compatibility, but causes a
deprecation warning.  Application writers are advised to update their
code.

* New special handlers: startup and shutdown

These two handlers provide global initialization and cleanup routines.
The "startup" handler is run by the master mailfromd process as part
of the startup sequence, before the program starts to serve any milter
requests.  The "shutdown" handler is run when mailfromd is about to
terminate.

Notice an important differences between "startup"/"shutdown" and
"begin"/"end" special handlers.  The latter are session specific: they
are run at the start and end of a milter session.  The former are
global: they are run at the program startup and shutdown.

The "startup" handler is normally used by mfmod interface modules to
load the corresponding shared library.

* Use of STARTTLS in callout

If TLS is supported by libmailutils, the SMTP callout code will use
STARTTLS when offered by the remote server.  This is controlled by the
smtp-starttls configuration statement.  Its possible values are:

  never
    Never use STARTTLS.

  always
    Always use STARTTLS if offered by the server.

  ondemand
    Use STARTTLS only if MAIL FROM: command failed with the code
    530 (Authorization required).

The default is "ondemand".

* Qualified DBM file names in database configuration

Argument to database.file statement can be prefixed with "database
scheme" to select alternative DBM implementation.  For example:

  database rate {
     file "gdbm://rate.db";
  }

See the manual, section 7.11 "Database Configuration" for details.

* New command line option: --echo

The --echo option allows you to control where the output of the "echo"
statement goes in "run" and "test" modes.  When used without argument
it directs the output to the standard output stream.  If an argument
is supplied (as in: --echo=FILE), the output goes to the named file.
The file will be created if it doesn't exist.  Notice, that in the
latter case, the use of '=' is compulsory (--echo FILE won't work).

* Deprecated configuration statements removed

Deprecated configuration statements `lock-retry-count' and
`lock-retry-timeout' were removed in this version.  Use
the `locking' statement instead, e.g. instead of

  lock-retry-count 10;
  lock-retry-timeout 1;

write

  locking {
    retry-count 10;
    retry-sleep 1;
  }

* Removed support for obsolete features: legacy GeoIP and DSPAM
	  

* Handling of control characters in syslog messages

If the message text contains ASCII control characters (ASCII 0 to 31),
these are replaced with their "caret notation", i.e. a caret
character followed by the character value XORed with 0100.  Thus,
horizontal tabulation (ASCII 9) becomes ^I, carriage return
(ASCII 13) becomes ^M, etc.  By default the newline character is
exempt from this translation.  Instead, it is substituted with
horizontal space (ASCII 32).

The "-Wcontrol_chars=MODE" option can be used to alter this
processing. Possible values for MODE are:

 caret
    Replace all control characters with their caret notation.  The newline
    character is represented as ^J.

 caretnl
    The default algorithm as described above.

 octal
    Replace control characters with their octal representation.

 raw
    Reproduce control characters verbatim.

* New option -s: set input buffer size

The -s option changes the default input buffer size.  Its argument is
the desired size in bytes.  For UDP input, values of up to 4096 are
allowed.  The default is 1024.

* New output channel: pri:///DIR

  Distributes messages to two disk files located in directory DIR.
  The name of the file to write to is selected depending on the message
  severity.  Messages with severity greater than LOG_ERR are directed
  to file "1" ("out" file), messages with severity less than or equal
  to LOG_ERR are directed to file "2" ("err" file).

  This channel understands the following parameters:

    severity=SEVERITY
       Gives name of the delimiter severity.  Messages with severity
       less than or equal to that value will be directed to "err" file.
       (DIR/2, by default).

    errfile=NAME
       Sets the name of the "err" file.

    outfile=NAME
       Sets the name of the "out" file.

    prio=none|keep|decode
       Controls whether and how the message priority is reflected on
       the output.  See the channel "file:" for details.

  Default settings correspond to:

      -Wseverity=err -Werrfile=2 -Woutfile=1 -Wprio=none
	  

This is a bug-fix release with minimal changes.

* texi2any
  . do not distribute architecture-dependent files
  . build fixed on OpenIndiana 11

* info
  . further fix of recoding of UTF-8 files to ASCII
  . fix check for presence of man pages on Solaris

* install-info
  . fix build by avoiding function name clash on some platforms
  . compiler warning re strncat silenced
	  

	- New domain source: pound.
	  

* http server: fix the Connection: header in HTTP response
	  

* Fix handing of the Connection: HTTP handler (both server and client)
	  

* Diagnostic directives: $$warning and $$error

The $$warning directive emits warning message.  It does not alter exit
status in any way.

The $$error directive reports a fatal error and sets exit status to
65.

After both directives, processing is resumed at the next line.

* $$exit

New directive $$exit causes immediate termination of the program.
Decimal exit code may be supplied as argument.

* New directive: $$eval

The text between $$eval and $$end is expanded and the resulting
expansion is scanned again, producing the actual output.  This makes
it possible to create variable names on the fly and get their values.
Useful in loops, e.g.:

  $$loop I 0 1 2 3 4 5 6 7
  $$  eval
  \$\$ ifset VAR_$I
  Expand \$VAR_$I;
  \$\$ endif
  $$ end
  $$end

* Bugfixes

** Fix closing the $$range loop.
	  

* Load-balancing strategies

A load balancing strategy defines algorithm used to distribute
incoming requests between multiple regular backends.  This version
of pound implements two such strategies:

** Weighted Random Balancing

This is the default strategy and the one implemented by prior versions
of pound.  Each backend is assigned a numeric priority between 0 and 9
(inclusive).  The backend to use for each request is determined at
random taking into account backend priorities, so that backends with
numerically greater priorities have proportionally greater chances of
being selected than the ones with lesser priorities.

** Interleaved Weighted Round Robin Balancing

Requests are assigned to each backend in turn.  Backend priorities, or
weigths, are used to control the share of requests handled by each
backend.  The greater the weight, the more requests will be sent to
this backend.

* New statement: Balancer

The Balancer statement can appear in global and in Service scope.  It
defines the load balancer to use.  Possible arguments are: random, to
use weighted random balancing (default), and iwrr to use interleaved
weighted round robin balancing.

* Backreferences

Up to eight most recent matches are saved.  They can be referenced
as $N(M), where N is number of the parenthesized subexpression, and
M is number of the match.  Matches are numbered in reverse chronological
order with the most recent one being at index 0.  The (0) can be
omitted ($1 is the same as $1(0)).

For example, given the following statements:

  Host -re "www\\.(.+)"
  Header -re -icase "^Content-Type: *(.*)"
  Path "^/static(/.*)?"

"$1" refers to the subgroup of Path, "$1(1)" - to that of Header, and
"$1(2)" - to that of Host.

Curly braces may be used to delimit reference from the text that
follows it.  This is useful if the reference is immediately followed
by a decimal digit or opening parenthesis, as in: "${1}(text)".

* Request matching directives

In addition to "URL" and "Header", the following matching directives
are provided

  Path [options] "value"
    Match path.

  Query [options] "value"
    Match query.

  QueryParam "name" [options] "value"
    Match query parameter.

* Request modification directives

Request modification directives apply changes to the incoming request
before passing it on to the service or backend.  They can be used both
in ListenHTTP (ListenHTTPS) and Service sections.  The following
directives are provided:

  DeleteHeader "header: pattern"
      Remove matching headers from the incoming requests.

  SetHeader "header: to add"
      Add the defined header to the request passed.  If the header
      already exists, change its value.

  SetURL "value"
      Sets the URL part of the request.

  SetPath "value"
      Sets the path part.

  SetQuery "value"
      Sets the query part.

  SetQueryParam "name" "value"
      Sets the query parameter "name" to "value".

  Rewrite ... [ Else ... ] End
      Conditionally apply request modification depending on whether request
      matches certain conditions, e.g.:

		Rewrite
			Path "\\.(jpg|gif)$"
			SetPath "/images$0"
		Else
			Match AND
				Host "example.org"
				Path "\\.[^.]+$"
			End
			SetPath "/static$0"
		Else
			Path "\\.[^.]+$"
			SetPath "/assets$0"
		End

* Request accessors

These are special constructs that, when used in string values, are
replaced with the corresponding parts of the incoming request.  The
supported accessors are:

 %[url]
   The URL of the request.

 %[path]
   The path part of the request.

 %[query]
   The query part of the request.

 %[param NAME]
   The value of the query parameter NAME.

 %[header NAME]
   The value of the request header NAME.

Request accessor can be used in all strings where the use of
backreferences is allowed: i.e. arguments to Redirect, ACME,
Error directives, and to all request modification directives described
above.

* Listener labels

Listeners can be assigned symbolic labels.  The syntax is:

  ListenHTTP "name"
or
  ListenHTTPS "name"

The "name" must be unique among all listeners defined in the
configuration.

This symbolic name can be used to identify listener in poundctl
requests (see below).

* Service labels

Service labels must be unique among all services within the
listener (or in the configuration file, for global ones).

* Use of listener and service labels in poundctl

Listeners and services can be identified both by their numbers and
labels.  For example:

  poundctl list /main/static/1

* Use of multiple redirects in single service

Use of multiple redirect backends in single service, as well as mixing
them with regular backends is deprecated and causes a warning message.