+<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>
+
+<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>
+
+<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>Strict conformance to relevant RFCs and good debugging options.
+You could use fetchmail to test and debug server
+implementatations.</li>
+
+<li>For anybody who cares, fetchmail is Y2K safe.</li>
+</ul>
+
+<h2>Features in common with other remote-mail retrieval
+programs:</h2>
+
+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.
+
+<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="right">$Date$</td>
+</tr>