diff options
Diffstat (limited to 'fetchmail-features.html')
| -rw-r--r-- | fetchmail-features.html | 395 |
1 files changed, 212 insertions, 183 deletions
diff --git a/fetchmail-features.html b/fetchmail-features.html index 2a83dbaf..fae01ede 100644 --- a/fetchmail-features.html +++ b/fetchmail-features.html @@ -1,259 +1,288 @@ -<!doctype HTML PUBLIC "-//W3O//DTD W3 HTML 3.2//EN"> -<HTML> -<HEAD> -<TITLE>Fetchmail Feature List</TITLE> -<link rev=made href="mailto:esr@snark.thyrsus.com"> -<meta name="description" content="The fetchmail brag sheet."> -<meta name="keywords" content="fetchmail, POP, POP3, IMAP, IMAP2bis, IMAP4"> -</HEAD> -<BODY> -<table width="100%" cellpadding=0 summary="Canned page header"><tr> -<td width="30%">Back to <a href="index.html">Fetchmail Home Page</a> -<td width="30%" align=center>To <a href="/~esr/sitemap.html">Site Map</a> -<td width="30%" align=right>$Date: 2002/07/28 09:27:52 $ -</tr></table> -<HR> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> +<title>Fetchmail Feature List</title> +<link rev="made" href="mailto:esr@snark.thyrsus.com" /> +<meta name="description" content="The fetchmail brag sheet." /> +<meta name="keywords" content="fetchmail, POP, POP3, IMAP, IMAP2bis, IMAP4" /> +<style type="text/css"> +/*<![CDATA[*/ + h1.c1 {text-align: center} +/*]]>*/ +</style> +</head> +<body> +<table width="100%" cellpadding="0" summary="Canned page header"> +<tr> +<td width="30%">Back to <a href="index.html">Fetchmail Home Page</a></td> +<td width="30%" align="center">To <a href="/~esr/sitemap.html">Site Map</a></td> +<td width="30%" align="right">$Date: 2002/07/28 09:28:52 $</td> +</tr> +</table> -<H1 ALIGN=CENTER>Fetchmail Feature List</H1> +<hr /> +<h1 class="c1">Fetchmail Feature List</h1> -<H2>Since 5.0:</H2> -<UL> -<LI>ESMTP AUTH (RFC 2554) is supported. +<h2>Since 5.0:</h2> -<LI>Has the capability of adding trace information to the Received header to -faciliate mail filtering by mailserver and remote account. +<ul> +<li>ESMTP AUTH (RFC 2554) is supported.</li> -<LI>Fetchmail now has options to handle SSL certificate validation. +<li>Has the capability of adding trace information to the Received +header to faciliate mail filtering by mailserver and remote +account.</li> -<LI>Fetchmail can be told to fall back to delivering via local -sendmail if it can't open port 25. +<li>Fetchmail now has options to handle SSL certificate +validation.</li> -<LI>Support for AUTH=CRAM-MD5 under POP3, a la RFC2195. +<li>Fetchmail can be told to fall back to delivering via local +sendmail if it can't open port 25.</li> -<LI>Support for ODMR (On-Demand Mail Relay), RFC 2645. +<li>Support for AUTH=CRAM-MD5 under POP3, a la RFC2195.</li> -<LI>It's now easy to deliver mail to a local LMTP socket. +<li>Support for ODMR (On-Demand Mail Relay), RFC 2645.</li> -<LI>The interface option now checks both local and remote interface IPs. +<li>It's now easy to deliver mail to a local LMTP socket.</li> -<LI> -The plugin facility has been enhanced; %h and %p options are now -available to pass in the hostname and service port number. +<li>The interface option now checks both local and remote interface +IPs.</li> -<LI> -Added a dropdelivered option to discard Delivered-To headers. This -addresses a problem with using fetchmail and postfix as a relay inside -a domain; when postfix sees incoming messages with delivered-to -headers looking exactly the same as the ones it adds himself, it -bounces the message. +<li>The plugin facility has been enhanced; %h and %p options are +now available to pass in the hostname and service port number.</li> -<LI> -Added --smtpname to set username and domain portion of SMTP "RCPT TO" -command. >fetchmail@mail.julianhaight.com>. +<li>Added a dropdelivered option to discard Delivered-To headers. +This addresses a problem with using fetchmail and postfix as a +relay inside a domain; when postfix sees incoming messages with +delivered-to headers looking exactly the same as the ones it adds +himself, it bounces the message.</li> -<LI> -Added "from" server's IP address to inserted Received line ->fetchmail@mail.julianhaight.com<. +<li>Added --smtpname to set username and domain portion of SMTP +"RCPT TO" command. >fetchmail@mail.julianhaight.com>.</li> -<LI> -Fetchmail now runs on BeOS, thanks to David Reid <david@jetnet.co.uk>. +<li>Added "from" server's IP address to inserted Received line +>fetchmail@mail.julianhaight.com<.</li> -<LI> -In IMAP, unseen-message counting and indexing is now done by SEARCH -UNSEEN at the beginning of each poll or re-poll (rather than with -the UNSEEN and RECENT responses and FLAGS queries on individual -messages). This significantly cuts down on traffic to and from the -server, and gives more reliable results. +<li>Fetchmail now runs on BeOS, thanks to David Reid +<david@jetnet.co.uk>.</li> -<LI> -The aka option now matches hostname suffixes, so (for example) saying -`aka netaxs.com' will match not just netaxs.com but also (say) -pop3.netaxs.com and mail.netaxs.com. +<li>In IMAP, unseen-message counting and indexing is now done by +SEARCH UNSEEN at the beginning of each poll or re-poll (rather than +with the UNSEEN and RECENT responses and FLAGS queries on +individual messages). This significantly cuts down on traffic to +and from the server, and gives more reliable results.</li> -<LI> -Fetchmail can optionally use the RFC 2177 IDLE extension on an IMAP -server that supports it. +<li>The aka option now matches hostname suffixes, so (for example) +saying `aka netaxs.com' will match not just netaxs.com but also +(say) pop3.netaxs.com and mail.netaxs.com.</li> -<LI> -Fetchmail now recognizes the RFC 2449 extended responses [IN-USE] and -[LOGIN-DELAY]. +<li>Fetchmail can optionally use the RFC 2177 IDLE extension on an +IMAP server that supports it.</li> -<LI> -Fetchmail running in daemon mode now restarts itself quietly when the -rc file is touched. +<li>Fetchmail now recognizes the RFC 2449 extended responses +[IN-USE] and [LOGIN-DELAY].</li> -<LI>Following recent court decisions and changes in U.S. federal -regulatory policy, hooks for Secure Sockets Layer (SSL) are now part -of the main fetchmail distribution. The distribution still contains -no actual cryptographic code. +<li>Fetchmail running in daemon mode now restarts itself quietly +when the rc file is touched.</li> -<LI>NTLM support under IMAP, so fetchmail can query Microsoft Exchange servers. +<li>Following recent court decisions and changes in U.S. federal +regulatory policy, hooks for Secure Sockets Layer (SSL) are now +part of the main fetchmail distribution. The distribution still +contains no actual cryptographic code.</li> -<LI>Expunge option can now be used to break POP3 retrieval into subsessions. +<li>NTLM support under IMAP, so fetchmail can query Microsoft +Exchange servers.</li> -<LI>Support for AUTH=CRAM-MD5 under IMAP, a la RFC2195. -</UL> +<li>Expunge option can now be used to break POP3 retrieval into +subsessions.</li> -<H2>Since 4.0:</H2> -<UL> -<LI>The interface and monitor options now work with freeBSD. +<li>Support for AUTH=CRAM-MD5 under IMAP, a la RFC2195.</li> +</ul> -<LI> Fetchmail now sends RFC1894-conformant bouncemail on SMTP and LMTP errors. +<h2>Since 4.0:</h2> -<LI> Full support for LMTP according to RFC2033. +<ul> +<li>The interface and monitor options now work with freeBSD.</li> -<LI> True multi-language support using GNU gettext. +<li>Fetchmail now sends RFC1894-conformant bouncemail on SMTP and +LMTP errors.</li> -<LI> Support for use of HESIOD with Kerberos. +<li>Full support for LMTP according to RFC2033.</li> -<LI> The --bsmtp option supports recording fetched mail as a BSMTP batch. +<li>True multi-language support using GNU gettext.</li> -<LI> The --limit option can now be used in daemon mode, with oversized-message -notifications being mailed to the calling user. +<li>Support for use of HESIOD with Kerberos.</li> -<LI> -Configurable support for the <a -href="http://www.demon.net/info/helpdesk/demon_products/mail/sdps-tech.shtml">SDPS -extensions</a> in <a href="http://www.demon.net/">www.demon.net</a>'s -POP3 service. +<li>The --bsmtp option supports recording fetched mail as a BSMTP +batch.</li> -<LI> There is now an interactive GUI fetchmail configurator, fetchmailconf. +<li>The --limit option can now be used in daemon mode, with +oversized-message notifications being mailed to the calling +user.</li> -<LI> Code is 64-bit clean and Y2K-safe. +<li>Configurable support for the <a +href="http://www.demon.net/info/helpdesk/demon_products/mail/sdps-tech.shtml"> +SDPS extensions</a> in <a +href="http://www.demon.net/">www.demon.net</a>'s POP3 service.</li> -<LI> Automatically decodes armored 7-bit MIME into 8 bits (this can be -suppressed). +<li>There is now an interactive GUI fetchmail configurator, +fetchmailconf.</li> -<LI> You can specify which SMTP error is recognized as a spam block. +<li>Code is 64-bit clean and Y2K-safe.</li> -<LI> Support for Kerberos V authentication. +<li>Automatically decodes armored 7-bit MIME into 8 bits (this can +be suppressed).</li> -<LI> Support for IMAP-OTP authentication using Craig Metz's patches - for UW IMAP. +<li>You can specify which SMTP error is recognized as a spam +block.</li> -<LI> Support for IPv6 (using glibc or Craig Metz's inet6-apps library). +<li>Support for Kerberos V authentication.</li> -<Li> Support for IPSEC (using Craig Metz's inet6-apps library). +<li>Support for IMAP-OTP authentication using Craig Metz's patches +for UW IMAP.</li> -<LI> Support for IMAP with RFC1731-conformant GSSAPI authentication. +<li>Support for IPv6 (using glibc or Craig Metz's inet6-apps +library).</li> -<LI> Fixed and verified support for Cyrus IMAP server, M$ Exchange, - and Post Office/NT. +<li>Support for IPSEC (using Craig Metz's inet6-apps library).</li> -<LI> Support for responding with a one-time password when a POP3 server - issues an RFC1938-conforming OTP challenge. +<li>Support for IMAP with RFC1731-conformant GSSAPI +authentication.</li> -<LI> Support for Compuserve's RPA authentication protocol for POP3 - (not compiled in by default, but configurable). -</UL> +<li>Fixed and verified support for Cyrus IMAP server, M$ Exchange, +and Post Office/NT.</li> -<H2>Since 3.0:</H2> -<UL> -<LI> Support for IMAP RFC 1731 authentication with Kerberos v4. +<li>Support for responding with a one-time password when a POP3 +server issues an RFC1938-conforming OTP challenge.</li> -<LI> Support for multiple-folder retrieval in a single session - under IMAP. +<li>Support for Compuserve's RPA authentication protocol for POP3 +(not compiled in by default, but configurable).</li> +</ul> -<LI> Following SMTP 571 response to a From line, fetchmail no longer - downloads the bodies of spam messages. +<h2>Since 3.0:</h2> -<LI> Support for a `hunt list' of SMTP hosts. +<ul> +<li>Support for IMAP RFC 1731 authentication with Kerberos v4.</li> -<LI> Support for ESMTP 8BITMIME and SIZE options. +<li>Support for multiple-folder retrieval in a single session under +IMAP.</li> -<LI> Support for ESMTP ETRN command. +<li>Following SMTP 571 response to a From line, fetchmail no longer +downloads the bodies of spam messages.</li> -<LI> The stripcr & forcecr options to explicitly control carriage-return - stripping and LF->CRLF mapping before mail forwarding. -</UL> +<li>Support for a `hunt list' of SMTP hosts.</li> -<H2>Since 2.0:</H2> -<UL> -<LI> Support for secure use with ssh. +<li>Support for ESMTP 8BITMIME and SIZE options.</li> -<LI> Mailserver passwords can be parsed out of your .netrc file. +<li>Support for ESMTP ETRN command.</li> -<LI> When forwarding mail via SMTP, fetchmail respects the 571 - "spam filter" response and discards any mail that triggers it. +<li>The stripcr & forcecr options to explicitly control +carriage-return stripping and LF->CRLF mapping before mail +forwarding.</li> +</ul> -<LI> Transaction and error logging may optionally be done via syslog. +<h2>Since 2.0:</h2> -<LI> (Linux only) Security option to permit fetchmail to poll a host - only when a point-to-point link to a particular IP address is - up. +<ul> +<li>Support for secure use with ssh.</li> -<LI> RPOP support (restored; had been removed in 1.8). -</UL> +<li>Mailserver passwords can be parsed out of your .netrc +file.</li> -<H2>2.0 and earlier versions:</H2> -<UL> -<LI> Support POP2, APOP, RPOP, IMAP2, IMAP2bis, IMAP3, IMAP4, IMAP4rev1. . +<li>When forwarding mail via SMTP, fetchmail respects the 571 "spam +filter" response and discards any mail that triggers it.</li> -<LI> Support for Kerberos V4 user authentication (either MIT or Cygnus). +<li>Transaction and error logging may optionally be done via +syslog.</li> -<LI> Host is auto-probed for a working server if no protocol is - specified for the connection. Thus you don't need to know - what servers are running on your mail host in advance; the - verbose option will tell you which one succeeds. +<li>(Linux only) Security option to permit fetchmail to poll a host +only when a point-to-point link to a particular IP address is +up.</li> -<LI> Delivery via SMTP to the client machine's port 25. This - means the retrieved mail automatically goes to the system - default MDA as if it were normal sender-initiated SMTP mail. +<li>RPOP support (restored; had been removed in 1.8).</li> +</ul> -<LI> Configurable timeout to detect if server connection is dropped. +<h2>2.0 and earlier versions:</h2> -<LI> Support for retrieving and forwarding from multi-drop mailboxes - that is guaranteed not to cause mail loops. +<ul> +<li>Support POP2, APOP, RPOP, IMAP2, IMAP2bis, IMAP3, IMAP4, +IMAP4rev1. .</li> -<LI> Large user community -- fetchmail has a large user base (the - author's beta list includes well over two hundred people). This - means feedback is rapid, bugs get found and fixed rapidly. +<li>Support for Kerberos V4 user authentication (either MIT or +Cygnus).</li> -<LI> Carefully written, comprehensive and up-to-date man page describing - not only modes of operation but also how to diagnose the most - common kinds of problems and what to do about deficient servers. +<li>Host is auto-probed for a working server if no protocol is +specified for the connection. Thus you don't need to know what +servers are running on your mail host in advance; the verbose +option will tell you which one succeeds.</li> -<LI> Rugged, simple, and well-tested code -- the author relies on it - every day and it has never lost mail, not even in experimental - versions. (In the project's entire history there has only been - one recorded instance of lost mail, and that was due to a quirk - in some Microsoft code.) +<li>Delivery via SMTP to the client machine's port 25. This means +the retrieved mail automatically goes to the system default MDA as +if it were normal sender-initiated SMTP mail.</li> -<LI> Strict conformance to relevant RFCs and good debugging options. - You could use fetchmail to test and debug server implementatations. +<li>Configurable timeout to detect if server connection is +dropped.</li> -<LI> For anybody who cares, fetchmail is Y2K safe. -</UL> +<li>Support for retrieving and forwarding from multi-drop mailboxes +that is guaranteed not to cause mail loops.</li> -<H2>Features in common with other remote-mail retrieval programs:</H2> +<li>Large user community -- fetchmail has a large user base (the +author's beta list includes well over two hundred people). This +means feedback is rapid, bugs get found and fixed rapidly.</li> -The other programs I have checked include fetchpop1.9, PopTart-0.9.3, -get-mail, gwpop, pimp-1.0, pop-perl5-1.2, popc, popmail-1.6 and upop. +<li>Carefully written, comprehensive and up-to-date man page +describing not only modes of operation but also how to diagnose the +most common kinds of problems and what to do about deficient +servers.</li> -<UL> -<LI> Support for POP3. +<li>Rugged, simple, and well-tested code -- the author relies on it +every day and it has never lost mail, not even in experimental +versions. (In the project's entire history there has only been one +recorded instance of lost mail, and that was due to a quirk in some +Microsoft code.)</li> -<LI> Easy control via command line or free-format run control file. +<li>Strict conformance to relevant RFCs and good debugging options. +You could use fetchmail to test and debug server +implementatations.</li> -<LI> Daemon mode -- fetchmail can be run in background to poll - one or more hosts at a specified interval. +<li>For anybody who cares, fetchmail is Y2K safe.</li> +</ul> -<LI> From:, To:, Cc:, and Reply-To: headers are rewritten so that - usernames relative to the fetchmail host become fully-qualified - Internet addresses. This enables replies to work correctly. - (Would be unique to fetchmail if I hadn't added it to fetchpop.) +<h2>Features in common with other remote-mail retrieval +programs:</h2> -<LI> Message and header processing are 8-bit clean. -</UL> +The other programs I have checked include fetchpop1.9, +PopTart-0.9.3, get-mail, gwpop, pimp-1.0, pop-perl5-1.2, popc, +popmail-1.6 and upop. -<HR> -<table width="100%" cellpadding=0 summary="Canned page footer"><tr> -<td width="30%">Back to <a href="index.html">Fetchmail Home Page</a> -<td width="30%" align=center>To <a href="/~esr/sitemap.html">Site Map</a> -<td width="30%" align=right>$Date: 2002/07/28 09:27:52 $ -</tr></table> +<ul> +<li>Support for POP3.</li> + +<li>Easy control via command line or free-format run control +file.</li> + +<li>Daemon mode -- fetchmail can be run in background to poll one +or more hosts at a specified interval.</li> + +<li>From:, To:, Cc:, and Reply-To: headers are rewritten so that +usernames relative to the fetchmail host become fully-qualified +Internet addresses. This enables replies to work correctly. (Would +be unique to fetchmail if I hadn't added it to fetchpop.)</li> + +<li>Message and header processing are 8-bit clean.</li> +</ul> + +<hr /> +<table width="100%" cellpadding="0" summary="Canned page footer"> +<tr> +<td width="30%">Back to <a href="index.html">Fetchmail Home Page</a></td> +<td width="30%" align="center">To <a href="/~esr/sitemap.html">Site Map</a></td> +<td width="30%" align="right">$Date: 2002/07/28 09:28:52 $</td> +</tr> +</table> + +<br clear="left" /> +<address>Eric S. Raymond <a href="mailto:esr@thyrsus.com"><esr@snark.thyrsus.com></a></address> +</body> +</html> -<br clear="left"> -<ADDRESS>Eric S. Raymond <A HREF="mailto:esr@thyrsus.com"><esr@snark.thyrsus.com></A></ADDRESS> -</BODY> -</HTML> |