From: Matthias A. <mat...@gm...> - 2009-05-26 00:30:52
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings, I have uploaded a fetchmail 6.3.10 beta version - "beta" means that some of the bug fixes have been nontrivial, and testing is required. See the log below for bugs supposed to be fixed. Find the tarball at the usual download location: <http://home.pages.de/~mandree/fetchmail/>. Happy fetching Matthias ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Changes in fetchmail 6.3.10-beta1 since 6.3.9: # ADVANCE WARNING OF FEATURES TO BE REMOVED OR CHANGED IN FUTURE VERSIONS * The maintainer may migrate fetchmail to C++ with STL or C#, and impose further requirements (dependencies), such as Boost or other class libraries. * The softbounce option default will change to "false" in the next release. fetchmail 6.3.10 (not yet released, beta1 on 2009-05-25): # INCOMPATIBLE BUGFIXES AND CHANGES * Fetchmail no longer drops permanently undelivered messages by default, to match historic documentation. It does this by adding a new "softbounce" option, see below. Fixes Debian Bug#471283, demotes Debian Bug#494418 to wishlist. * There is a new "softbounce" global option that prevents the deletion of messages that have not been forwarded. It defaults to "true" for fetchmail 6.3.X in order to match historic documentation. This may change its default in the next major release. # BUGFIXES * Fix misuse of canonical autoconf target as _TARGET when it should have been _HOST. Report and patch courtesy of Diego E. "Flameeyes" Pettenò. Details: http://blog.flameeyes.eu/2009/01/01/the-canonical-target * Do not lose PS_MAXFETCH (13) exit status when hitting maxpoll. Reported by Michelle Konzack, Debian Bug#508667. * Do not overlap source and destination fields in snprintf() in interface.c. Courtesy of Nico Golde, Debian. * When a pre- or post-connect command fails, now report the exit status or termination signal properly through sys/wait.h macros. * When acquiring a body, understand NIL ("no such data item"), as returned by some MS Exchange versions. Fixes BerliOS Bug #11980 by KB Sriram. * Make progress tickers (-v/--showdots) consistent, and update documentation accordingly ("." for each 1024 octets read, "#" for a header written, and "*" for each body line written.) The conditions under which these had been printed were inconsistent, illogical, and documentation hadn't matched real behaviour for long. * For NTLM authentication, use dynamically allocated buffers. Fixes Debian Bug#449179, reported by Stepan Golosunov. * Non-delivery notice ("bounce mail") now mentions the original reason again, before the address list. This fixes a regression introduced in 6.3.0. * Several compiler warnings were fixed. * The minimum recommended SMTP (RFC-5321) timeouts are enforced to leave sufficient time for the listener to respond. Some synchronous listeners, particularly when used with spam filtering and other policy enforcement services, take extended amounts of time to process messages after the sender, recipient, or data block and EOM line. This can cause fetchmail to not wait long enough for the "250 Ok" and make fetchmail believe the message wasn't properly delivered when in fact it was; fetchmail would then retry the download next time and never make progress. Fixes Berlios Bug #10972, reported by Viktor Binzberger. * The ESMTP/LMTP client will now apply an application-specific timeout while waiting for the EHLO/LHLO response, rather than wait for the server or TCP connection timeout. * Treat 530 errors as temporary, so as not to delete messages on configuration errors. Partially taken from Petr Cerny's patch in Novell Bugzilla #246829. The 501 part of said patch was not added, as the maintainer is not convinced 501 is a temporary condition, and softbounce takes care of this anyways. # CHANGES * Make the comparison of the SSL fingerprints case insensitive, to ease its use. Suggested by Daniel Richard G. # CHANGES TO CONTRIB * Fix bashism in contrib/fetchsetup. Fixes Debian Bug#530081. # DOCUMENTATION * Some parts of the the manual page were revised for clarity, accuracy, and updated recommendations (particularly SSL/TLS) and formatting conventions from man-pages(7). * The README and README.SSL documents were updated. * A document, README.SSL-SERVER, was added to describe server-side requirements for proper SSL and/or TLS service offerings. These are not specific to fetchmail. # TRANSLATION UPDATES AND ADDITIONS (ordered by language name): * [en_GB] English/British * [de] German * [it] Italian (Vincenzo Campanella) * [es] Spanish/Castilian (Francisco Molinero) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkobHBYACgkQvmGDOQUufZVlLQCcC3BGECLvxLPFRnFoK3kPhDUL aMwAoKnIMkE/WmOevCCPC/G/aR0ROl/z =o/Ah -----END PGP SIGNATURE----- |
From: Rob M. <rob...@gm...> - 2009-05-26 01:18:06
|
On Mon, May 25, 2009 at 23:30, Matthias Andree <mat...@gm...> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Greetings, > > I have uploaded a fetchmail 6.3.10 beta version - "beta" means that some > of the bug fixes have been nontrivial, and testing is required. See the > log below for bugs supposed to be fixed. Compiles cleanly, with SSL support, on FreeBSD 7.0 (I'll get around to upgrading it to something current in a few weeks, hopefully). -- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche |
From: Matthias A. <mat...@gm...> - 2009-05-26 09:52:09
|
Am 26.05.2009, 00:30 Uhr, schrieb Matthias Andree <mat...@gm...>: > I have uploaded a fetchmail 6.3.10 beta version - "beta" means that some > of the bug fixes have been nontrivial, and testing is required. See the > log below for bugs supposed to be fixed. Details on required testing in 6.3.10-beta1: - does fetchmail leave undeliverable messages on the server by default? - does NTLM authentication with M$ Exchange still work? (It works with Cyrus IMAP.) - does fetchmail now properly continue on Exchange messages that have no body? (Some Exchange versions respond with "NIL" rather than "0 bytes" - fetchmail up to 6.3.9 did not handle that and hung.) - does fetchmail-generated bounce mail still look right? Please also look at the README.SSL and README.SSL-SERVER documents and pinpoint sections you find hard to read, hard to understand, or if information is missing; same goes for the manual page. If you can offer a test account free of charge, i. e. an account where I can send a short email and retrieve it via POP3, IMAP, or other supported protocols, I'd be happy to take such offers. Thanks a lot! Best regards -- Matthias Andree |