|
Lines 1-28
Link Here
|
| 1 |
fetchmail-6.4.10 (released 2020-08-27, 27596 LoC): |
1 |
fetchmail README |
|
|
2 |
================ |
| 2 |
|
3 |
|
| 3 |
# REGRESSION FIX: |
4 |
Introduction |
| 4 |
* configure: fetchmail 6.4.9's configure was unable to pick up OpenSSL |
5 |
------------ |
| 5 |
if it wasn't announced by pkg-config, for instance, on FreeBSD. |
|
|
| 6 |
|
| 7 |
# KNOWN BUGS AND WORKAROUNDS |
| 8 |
(This section floats upwards through the NEWS file so it stays with the |
| 9 |
current release information) |
| 10 |
* Fetchmail does not handle messages without Message-ID header well |
| 11 |
(See sourceforge.net bug #780933) |
| 12 |
* Fetchmail currently uses 31-bit signed integers in several places |
| 13 |
where unsigned and/or wider types should have been used, for instance, |
| 14 |
for mailbox sizes, and misreports sizes of 2 GibiB and beyond. |
| 15 |
Fixing this requires C89 compatibility to be relinquished. |
| 16 |
* BSMTP is mostly untested and errors can cause corrupt output. |
| 17 |
* Fetchmail does not track pending deletes across crashes. |
| 18 |
* The command line interface is sometimes a bit stubborn, for instance, |
| 19 |
fetchmail -s doesn't work with a daemon running. |
| 20 |
* Linux systems may return duplicates of an IP address in some circumstances if |
| 21 |
no or no global IPv6 addresses are configured. |
| 22 |
(No workaround. Ubuntu Bug#582585, Novell Bug#606980.) |
| 23 |
* Kerberos 5 may be broken, particularly on Heimdal, and provide bogus error |
| 24 |
messages. This will not be fixed, because the maintainer has no Kerberos 5 |
| 25 |
server to test against. Use GSSAPI. |
| 26 |
|
6 |
|
|
|
7 |
Fetchmail is a free, full-featured, robust, well-documented remote mail |
| 8 |
retrieval and forwarding utility intended to be used over on-demand TCP/IP |
| 9 |
links (such as SLIP or PPP connections). It retrieves mail from remote mail |
| 10 |
servers and forwards it to your local (client) machine's delivery system, so it |
| 11 |
can then be be read by normal mail user agents such as mutt(1), elm(1) or |
| 12 |
Mail(1). |
| 27 |
|
13 |
|
| 28 |
--------------------------------------------------------------------------------- |
14 |
Fetchmail supports all standard mail-retrieval protocols in use on the |
|
|
15 |
Internet: POP3 (including some variants such as RPOP, APOP, KPOP), IMAP4rev1 |
| 16 |
(also IMAP4, IMAP2bis), POP2, IMAP4, ETRN, and ODMR. On the output side, |
| 17 |
fetchmail supports ESMTP/SMTP, LMTP, and invocation of a local delivery agent. |
| 18 |
|
| 19 |
Fetchmail also fully supports authentication via GSSAPI, Kerberos 4 and 5, |
| 20 |
RFC1938 one-time passwords, Compuserve's POP3 with RPA, Microsoft's NTLM, Demon |
| 21 |
Internet's SDPS, or CRAM-MD5 authentication a la RFC2195. |
| 22 |
|
| 23 |
Fetchmail supports end-to-end encryption with OpenSSL, do read README.SSL for |
| 24 |
details on fetchmail's configuration and README.SSL-SERVER for server-side |
| 25 |
requirements. NOTE! To be compatible with earlier releases, fetchmail 6.4 |
| 26 |
default behaviour is more relaxed than dictated by recommendations - while it |
| 27 |
does away with SSLv2, only negotiates SSLv3 if forced to, it will by default |
| 28 |
still negotiate TLS v1.0. |
| 29 |
|
| 30 |
Portability |
| 31 |
----------- |
| 32 |
|
| 33 |
The fetchmail code was developed under Linux, but has also been extensively |
| 34 |
tested under the BSD variants, AIX, HP-UX versions 9 and 10, SunOS, Solaris, |
| 35 |
NEXTSTEP, OSF 3.2, IRIX, and Rhapsody once upon a time. |
| 36 |
|
| 37 |
The current maintainer does not have access to these systems, and assumes that |
| 38 |
the system is at least Single-Unix-Specification V2 compatible, yet fetchmail |
| 39 |
should be compilable by a C89 compiler. It currently ships with a copy of the |
| 40 |
trio library for systems that lack snprintf(). A further requirement is that |
| 41 |
either realpath() permits its 2nd argument to be NULL for auto-allocation, |
| 42 |
or that otherwise PATH_MAX be defined. |
| 43 |
|
| 44 |
Fetchmail should be able to be compiled with C89, C99, C11, C++98, C++03, |
| 45 |
C++11, C++14 compilers, but not C++17 because the "register" keyword is |
| 46 |
used in some parts of the code. |
| 47 |
|
| 48 |
Future fetchmail releases will require modern language features such as |
| 49 |
"long long" and others, so this release is the last to support C89. |
| 50 |
|
| 51 |
Further reading |
| 52 |
--------------- |
| 53 |
|
| 54 |
The INSTALL file describes how to configure and install fetchmail. |
| 55 |
|
| 56 |
See the distribution files FEATURES for a full list of features, NEWS for |
| 57 |
detailed information on recent changes, NOTES for design notes, and TODO for |
| 58 |
a list of things that still need doing. If you want to hack on this code, |
| 59 |
a list of known bugs and to-do items can be found in the file todo.html. |
| 60 |
|
| 61 |
Status, source code |
| 62 |
------------------- |
| 63 |
|
| 64 |
The fetchmail code appears to be stable and free of bugs affecting normal |
| 65 |
operation (that is, retrieving from POP3 or IMAP in single-drop mode and |
| 66 |
forwarding via SMTP to a local mail transfer agent). |
| 67 |
|
| 68 |
You can get the code from the fetchmail home page: |
| 69 |
|
| 70 |
https://www.fetchmail.info/ |
| 71 |
https://fetchmail.sourceforge.io/ |
| 72 |
|
| 73 |
Enjoy! |
| 74 |
|
| 75 |
-- esr, ma |