fetchmail-6.2.5

equire that you *remove* the %s at the end of your MDA string. Local
delivery addresses will be appended to the end of the command in the
obvious way.
* The first message from a query now includes the number of old messages
when this can be determined (that is not under POP2).
* POP3 UID support really works now. I make rude noises at the POP3 mavens
who forced us to this with RFC1725, but thank Al Longyear
for fixing and verifying my slightly buggy implementation.
* Kerberos V4 support ditto. Thanks to Chris Hanson
for this feature.
* When there’s a daemon fetchmail in background, running fetchmail in
foreground without --quit now tries to wake the daemon and force it
to poll immediately.
* Add option to set server nonresponse timeout.
* Password is no longer displayed in verbose mode.
* You may use C-like escapes to embed non-printables in passwords and other
strings. Fetchmail -V will display them in a printable form.
* Program now tries to set itself to the ID of the local user before
running an MDA, and reset to root afterwards. This will work on
any system with seteuid(2), including Linux and the BSDs.
bugs --
* Default user name to deliver to is now the calling user, unless
program is running as root in which case it is the remote user name
(default can be overridden with an ‘is’ or ‘to’ declaration).
In versions up to 1.7 it was the calling user; in 1.8 the remote
user ID. This created some confusion.
* Accept RFC822 headers with a tab after the colon.
* You now see a "skipping" message for each message not retrieved.
* --keep no longer overrides --flush.
* Rewrite "To: jrh (J. Random Hacker)" correctly.
* Find "nnn octets" anywhere on a POP3 server’s RETR response line.
* Fixed various bugs in --check. It now reports PS_SUCCESS only if
there is new mail waiting.
* Under Linux, if fetchmail is run in daemon mode with the network
inaccessible, each poll leaves a socket allocated but in CLOSE state
(this is visible in netstat(1)’s output). These sockets aren’t
garbage-collected until fetchmail exits. When whatever kernel table
is involved fills up, fetchmail can no longer run even if the network is up.
To avoid this, fetchmail now commits seppuku after some number of
unsuccessful socket opens.
* Don’t try using FLAGS.SILENT, some allegedly IMAP2bis servers seem to
choke on it.