| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
When Gene Heskett was updating his OpenSSL on Debian oldstable, we figured
that it might be helpful to print where OpenSSL goes look for the trusted
certificate. Add this information.
Also add documentation of OpenSSL's SSL_CERT_DIR/SSL_CERT_FILE environment
variables.
|
|
|
|
|
|
|
|
|
| |
This was found by Julian Bane debugging a situation where duplicate
suppression did not kick in (due to envelope-recording headers,
X-Original-To, Delivered-To). Historic behavior now documented in
fetchmail.man and NEWS in order to reduce confusion.
Gitlab, fixes issue #29.
|
| |
|
|
|
|
| |
Reported by David McKelvie on fetchmail-users today.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
When AC_LIB_LINKFLAGS came up with, for instance, /usr/lib/libssl.so,
configure.ac failed to check for TLS v1.2 and TLS v1.3 support in the
SSL library, disabling explicit TLS v1.2 and v1.3 support.
|
| |
|
| |
|
|
|
|
| |
After Ranjan Maitra's report on fetchmail-users 2020-07-02
|
| |
|
| |
|
| |
|
|
|
|
| |
Initial tests done by David Hough, now formal release candidate for translators.
|
| |
|
|
|
|
|
| |
The code was added in 3d4a8713e = 6.4.0-beta3,
but the documentation was missing from the manual page.
|
| |
|
| |
|
|
|
|
|
|
|
| |
* Minor cleanups, removing blank .PP.
* Switch all http:// references to https:// (all support it).
* Switch fetchmail.sourceforge.net to fetchmail.sourceforge.io after
the https:// migration.
|
| |
|
|
|
|
| |
As noted at the start of the entry it is now the default.
|
|
|
|
|
|
|
|
|
| |
- fix unterminated string in .IP macro
- fix .TH date format
- properly break line after .PP
- replace .br in table (unsupported by FreeBSD 12's mandoc)
FreeBSD Bug#241032 reported by Helge Oldach
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Obtained from: https://sources.debian.org/data/main/f/fetchmail/6.4.0~rc3-1/debian/patches/03_typo-manpage.diff
Obsoletes: Debian patch 03_typo_manpage.diff
|
| |
|
| |
|
|
|
|
|
|
| |
Since the addition of --nosslcertck documentation in Nov. 2015
with commit 6adcb0cc, the --sslcertfile documentation had become part of
--nosslcertck. Now --sslcertfile stands in a paragraph of its own.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
In response to Jeremy Chadwick's trouble 2014-11-19, fetchmail-users.
|
|
|
|
| |
Re-sign EN and SAs because that broke signatures.
|
| |
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
reported by Heinz Diehl.
|
| |
|
|
|
|
|
| |
In case logfile overrides syslog, send a message to the latter stating
where logging goes. Also revise manual page.
|
| |
|