The 6.3.25 release of fetchmail is available

--===============8023089395054773953==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="1yeeQ81UyVL57Vl7"
Content-Disposition: inline


--1yeeQ81UyVL57Vl7
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

The 6.3.25 release of fetchmail is now available at the usual locations,
including <http://developer.berlios.de/projects/fetchmail> and
<http://sourceforge.net/projects/fetchmail/>.

The source archive is available at:
<http://prdownload.berlios.de/fetchmail/fetchmail-6.3.25.tar.xz>
<http://sourceforge.net/projects/fetchmail/files/branch_6.3/fetchmail-6.3.2=
5.tar.xz/download>

or in the older bzip2 format:
<http://prdownload.berlios.de/fetchmail/fetchmail-6.3.25.tar.bz2>

Here are the release notes:

fetchmail-6.3.25 (released 2013-03-18, 26149 LoC):

# NOTE THAT FETCHMAIL IS NO LONGER PUBLISHED THROUGH IBIBLIO.
* They have stopped accepting submissions and consider themselves an archiv=
e.

# BUG FIXES
* Fix a memory leak in out-of-memory error condition while handling plugins.
  Report and patch by John Beck (found with Parfait static code analyzer).
* Fix a NULL pointer dereference in out-of-memory error condition while han=
dling
  plugins.
  Report and patch by John Beck (found with Parfait static code analyzer).

# CHANGES
* Improved reporting when SSL/TLS X.509 certificate validation has failed,
  working around a not-so-recent swapping of two OpenSSL error codes, and
  a practical impossibility to distinguish broken certification chains from
  missing trust anchors (root certificates).
* OpenSSL decoded errors are now reported through report(), rather than dum=
ped
  to stderr, so that they should show up in logfiles and/or syslog.
* The fetchmail manual page no longer claims that MD5 were the default Open=
SSL
  hash format (for use with --sslfingerprint). Reported by Jakob Wilk,
  PARTIAL fix for Debian Bug#700266.
* The fetchmail manual page now refers the user to --softbounce from the
  SMTP/ESMTP ERROR HANDLING section.  Reported by Anton Shterenlikht.

# WORKAROUNDS
* Older systems that provide the older RFC-2553 implementation of getaddrin=
fo,
  rather than the current RFC-3493, and systems that do not provide this
  getaddrinfo() interface at all and thus use the replacement functions from
  libesmtp/getaddrinfo.?, might return EAI_NODATA when a host is registered=
 in
  DNS as MX or similar, but without A or AAAA records.  Handle this situati=
on
  when checking for multidrop aliases and treat EAI_NODATA the same as
  EAI_NONAME, i. e. name cannot be resolved.

  The proper fix, however, is to upgrade the operating system.

# TRANSLATION UPDATES
[cs] Czech, by Petr Pisar
[da] Danish, by Joe Hansen
[de] German
[eo] Esperanto, by Sian Mountbatten and Felipe Castro
[fr] French, by Fr=C3=A9d=C3=A9ric Marchal
[ja] Japanese, by Takeshi Hamasaki
[pl] Polish, by Jakub Bogusz
[sv] Swedish, by G=C3=B6ran Uddeborg
[vi] Vietnamese, by Tr=E1=BA=A7n Ng=E1=BB=8Dc Qu=C3=A2n

# KNOWN BUGS AND WORKAROUNDS
  (This section floats upwards through the NEWS file so it stays with the
  current release information)
* Fetchmail does not handle messages without Message-ID header well
  (See sourceforge.net bug #780933)
* BSMTP is mostly untested and errors can cause corrupt output.
* Sun Workshop 6 (SPARC) is known to miscompile the configuration file lexe=
r in
  64-bit mode.  Either compile 32-bit code or use GCC to compile 64-bit
  fetchmail.  Note that fetchmail doesn't take advantage of 64-bit code,
  so compiling 32-bit SPARC code should not cause any difficulties.
* Fetchmail does not track pending deletes across crashes.
* The command line interface is sometimes a bit stubborn, for instance,
  fetchmail -s doesn't work with a daemon running.
* Linux systems may return duplicates of an IP address in some circumstance=
s if
  no or no global IPv6 addresses are configured.
  (No workaround. Ubuntu Bug#582585, Novell Bug#606980.)
* Kerberos 5 may be broken, particularly on Heimdal, and provide bogus error
  messages. This will not be fixed, because the maintainer has no Kerberos 5
  server to test against. Use GSSAPI.


By popular demand, diffs from the previous release have been omitted.

--1yeeQ81UyVL57Vl7
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAlFHrLEACgkQvmGDOQUufZV17ACggo1ClsZN4jDDNc/UrizTMzKn
mUEAoL7+Jbt+K3OzzW5Sg30Ufx1amHmQ
=Pdwq
-----END PGP SIGNATURE-----

--1yeeQ81UyVL57Vl7--

--===============8023089395054773953==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
fetchmail-announce mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/fetchmail-announce
--===============8023089395054773953==--