| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
Let the system allocate realpath() buffers intead
of trying to portably derive a buffer size.
This was found with default GCC fortify settings on
Ubuntu 18.04 and showed with -D_FORTIFY_SOURCE=2 on Fedora, too.
|
|
|
|
|
| |
dist-tools/makerelease.pl looks for lines matching ^fetchmail- to extract
from NEWS, so make fetchmail 6.4.0 not match that regex.
|
|
|
|
|
|
|
|
| |
The fix between 6.4.0-rc4 and 6.4.0 for Debian Bug#941129 caused
a regression in the default file locations, some files were looked
for without dot (.fetchmail.pid, .fetchmailrc).
Reported by Cy Schubert.
|
|
|
|
| |
This entails recording new line numbers in po/*.po files.
|
|
|
|
|
|
|
|
| |
If FETCHMAILHOME is specified as relative path, then it can become
the victim of a chdir("/") that happens in daemon mode, so that
switching to daemon mode will change behaviour of FETCHMAILHOME.
Reported by Alex Andreotti, Debian Bug #941129.
|
| |
|
|
|
|
|
|
| |
* Normalize include order.
* Backport missed bug fixes.
* Remove dead code.
|
|
|
|
|
|
|
| |
Fixes a regression introduced in release 5.0.0 in March 1999 that was
attributed to Henrik Storner.
(cherry-pick from master, e45e718a80379391f8ba457e64e19f75f061741a)
|
| |
|
|
|
|
|
|
|
| |
* Remove a bogus check that would prevent editing the first items from list boxes.
* Require Python 2.3.
* Convert apply() call to function(*(tuple,)) syntax
* string.atoi() -> int() on select[0], to continue where it's not a string
|
|
|
|
| |
These have < 500 translated messages each.
|
| |
|
| |
|
|
|
|
| |
Fixes Debian Bug#928916, reported by Paul Kimoto.
|
|
|
|
|
|
|
|
|
| |
* CS: Petr Pisar <petr.pisar@atlas.cz> [Czech]
* EO: Felipe Castro <fefcas@gmail.com> [Esperanto]
* FR: Frédéric Marchal <fmarchal@perso.be> [French]
* JP: Takeshi Hamasaki <hmatrjp@users.sourceforge.jp> [Japanese]
* PL: Jakub Bogusz <qboosh@pld-linux.org> [Polish]
* SV: Göran Uddeborg <goeran@uddeborg.se> [Swedish]
|
| |
|
|
|
|
|
| |
to avoid failing the security check on the next run.
Reported by Fabian Raab, Debian Bug#831611.
|
|
|
|
| |
Reported in private by Greg Hudson.
|
|
|
|
| |
Greg Hudson reported this broke Exchange 2013 authentication.
|
| |
|
| |
|
| |
|
|
|
|
| |
(Cherry-picked from master's 1a92b2909610096a11d26f7a7317d32819354be3.)
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
There are no sslcertck (rcfile) and --nosslcertck (command line) options
that can be combined with [--]sslfingerprint if so desired.
The documentation is deliberately not updated everywhere, so that
recommendations to use --sslcertck stand, this is for the benefit of
users that read fetchmail v6.4.0 manuals to configure a fetchmail v6.3.X
implementation.
|
| |
|
| |
|
|
|
|
|
|
| |
This condition does not leave traces in the SSL error queue,
and must be checked explicitly. Result from debugging Jerry Seibert's
issue with outlook.com/pop3.live.com.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Removes SSLv2, enables TLSv1.1 and v1.2 more easily,
permits SSLv3 (only if specified) and newer TLSv1.1+ for STLS/STARTTLS.
Only negotiates TLSv1 and newer by default, SSLv3 must now be specified
explicitly, as a consequence of the POODLE attack.
This is meant to be a minimally upgraded version, and cannot be usefully
done as a 6.3.X release.
It is strongly recommended that users review their configuration -
especially --sslproto - per instructions in the NEWS file and manual
page. It has changed semantics and in many cases --sslproto auto or
perhaps --sslproto tls1.2+ should be used now.
|
|
|
|
|
| |
These are the macros OpenSSL defines when configured with no-ssl2 or no-ssl3,
the actual macro names are OPENSSL_NO_SSL2 and OPENSSL_NO_SSL3.
|
|
|
|
|
|
|
| |
providing that these also omit the declaration of SSLv3_client_method().
Related to Debian Bug#775255.
Version report lists -SSLv3 on +SSL builds that omit SSLv3_client_method().
Version report lists -SSLv2 on +SSL builds that omit SSLv2_client_method().
|
|
|
|
| |
In response to Jeremy Chadwick's trouble 2014-11-19, fetchmail-users.
|
| |
|
|
|
|
| |
Re-sign EN and SAs because that broke signatures.
|
|
|
|
| |
Reported by Gonzalo Pérez de Olaguer Córdoba, Debian Bug#744907.
|
|
|
|
| |
Fixes Debian Bug#706776, submitted by David Lawyer.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The mimedecode feature failed to ship the last line of the body if it
was encoded as quoted-printable and had a MIME soft line break in the
very last line. Reported by Lars Hecking in June 2011.
Bug introduced on 1998-03-20 when the mimedecode support was added by
ESR before release 4.4.1 through code contributed by Henrik Storner,
in driver.c.
Workaround for older releases: do not use mimedecode feature.
|
| |
|
| |
|
|
|
|
|
| |
The fetchmail manual page now refers the user to --softbounce from the
SMTP/ESMTP ERROR HANDLING section. Reported by Anton Shterenlikht.
|
|
|
|
|
|
|
| |
The fetchmail manual page no longer claims that MD5 were the default OpenSSL
hash format (for use with --sslfingerprint).
Reported by Jakob Wilk, PARTIAL fix for Debian Bug#700266.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
* 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 dumped
to stderr, so that they should show up in logfiles and/or syslog.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Older systems that provide the older RFC-2553 implementation of
getaddrinfo, 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 situation 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.
|