Fetchmail Release Notes ======================= This file is in Unicode charset with UTF-8 encoding. (The `lines' figures total .c, .h, .l, and .y files under version control. Abbreviations in parentheses are the maintainers who committed the respective change. MA = Matthias Andree, ESR = Eric S. Raymond, RF = Rob Funk.) # DEPRECATED FEATURES AND MAJOR INCOMPATIBLE CHANGE ADVANCE WARNINGS * The MX and host alias DNS lookups that fetchmail performs in multidrop mode are obsolete, deprecated and may be removed from a future fetchmail version. They have never supported IPv6 (including IPv6-mapped IPv4) anyhow. (MA) * The monitor and interface options may be removed from a future fetchmail version as they are not sufficiently portable. (MA) * POP2 is obsolete. Support for POP2 may be removed from a future fetchmail version. (MA) * RPOP is obsolete, support may be removed from a future fetchmail release. (MA) * --sslcertck may become a default setting in a future fetchmail version. (MA) * The multidrop To/Cc guessing code along with the fragile duplicate suppressor is deprecated and may be removed from a future release. (MA) -------------------------------------------------------------------------------- fetchmail 6.3.2 (to be released): Unless otherwise noted, changes to this release were made by Matthias Andree. # SECURITY FIX IN THIS RELEASE * CVE-2006-XXXX: Fix segfault or bus error after bouncing a message. This bug was introduced into 6.3.0 when removing alloca(); it caused fetchmail to free random memory. Reported by Nathaniel W. Turner, Debian Bug#348747. See fetchmail-SA-2006-01.txt # INCOMPATIBLE CHANGE: * Automatically disable the POP3 TOP command if the greeting string contains "Maillennium POP3/PROXY server", which is used by comcast and known to truncate messages after 80 kByte. Fall back to RETR, and complain if we had used TOP otherwise (the warning is printed only once per server in daemon mode). Suggested by Ed Wilts. *Note* that this means messages are marked read on these servers, which is a deviation from how 6.3.1 behaved, but we have no alternative, comcast haven't fixed this bug in years. Preventing the loss of the remainder of the message justifies this incompatible fix. * fetchmail, since 6.3.0, requires write permission to the directory holding the idfile. See the amendment in the 6.3.0 MAJOR INCOMPATIBLE CHANGES section below for details. The manual page was updated. # CHANGES RELEVANT TO PACKAGERS: * The outdated BUGS document was removed from the distribution. * Added fetchmail-SA-2006-01.txt to the distribution. # BUG FIXES: * SMTP/LMTP cleanup to fix these two bugs: - switch back to SMTP after having tried LMTP hosts (multiple smtphost hosts) - switch back to LMTP after sending a bounce. The patch removes the global state variable that was the root of this problem. Patch by Sunil Shetye. (MA) * Don't complain about fetchall keep in --configdump mode. Bug introduced in 6.3.0. * fetchmailconf.py: Fix novice help for Poll interval and fetchall. Reported by Justin Pryzby, Debian Bug #344978. * Some verbose output disappeared in debug mode. Adding further -v options would alternate between verbose and debug mode. debug mode now comprises all verbose output, and adding more -v options does not switch back from debug to verbose
To do a release:
1. Torture-test the code against the list of test sites usuing the
torturetest script.
2. Check in all files to RCS with an appropriate release label.
3. Run "makerelease" is root. Read the script to see what it generates.
4. Run "upload" as yourself.