Revise M$ Exchange information.

svn path=/trunk/; revision=1340

1 files changed, 15 insertions, 23 deletions

diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html
index 21eaa089..c5be0056 100644
--- a/fetchmail-FAQ.html
+++ b/fetchmail-FAQ.html
@@ -10,7 +10,7 @@
 <table width="100%" cellpadding=0><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: 1997/09/14 19:28:00 $
+<td width="30%" align=right>$Date: 1997/09/14 20:31:17 $
 </table>
 <HR>
 <H1>Frequently Asked Questions About Fetchmail</H1>
@@ -711,7 +711,7 @@ header or message lines terminated with bare linefeeds.<p>
 If a mailhost is using the qmail package (see <a
 href="http://pobox.com/~djb/qmail.html">http://pobox.com/~djb/qmail.html</a>)
 then, providing the local hosts are also using qmail, it is possible
-to setup one fetchmail link to be reliably collect the mail for an
+to set up one fetchmail link to be reliably collect the mail for an
 entire domain.<p>
 
 One of the basic features of qmail is the `Delivered-To:' message
@@ -823,28 +823,20 @@ to \r\n, but its rules are not intuitive.  Use `forcecr'.<P>
 <hr>
 <h2><a name="T5">T5. How can I use fetchmail with Microsoft Exchange?</a></h2><p>
 
-Fetchmail works with M$ Exchange, despite the latter's braindamage.
-Guido Van Rooij explains a bug found by his colleague Arjan de Vet (we
-reprintthis as a public service):<P>
+M$ Exchange violates the POP3 RFCs.  Its LIST command does not reveal
+the real sizes of mail in the pop mailbox, but the sizes of the
+compressed versions in the exchange mail database (thanks to Arjan De
+Vet and Guido Van Rooij for alerting us to this problem).<P>
 
-We're having problems using fetchmail to etch mail from an Exchange server
-with POP3. The bug is actually in the Exchange site however it seems possible
-to have fetchmail work around it.<P>
+Fetchmail works with M$ Exchange, despite this braindamage.  Two
+features are compromised.  One is that the --limit option will not
+work right (it will check against compressed and not actual sizes).
+The other is that a too-small SIZE argument may be passed to your
+ESMTP listener, assuming you're using one (this should not be a
+problem unless the actual size of the message is above the listener's
+configured length limit).<P>
 
-<blockquote>
-What happens is that a LIST command does not reveal the REAL sizes of mail
-in the pop mailbox, but the sizes of the compressed versions in the
-exchange mail database.<P>
-
-So when fetchmail tries to read the headers AND if the mail is too short,
-it fails and a newline is inserted within the headers.
-Usually this does not happen because even the compressed mailsize 
-exceeds the header size but if you send an empty mail to the Exchange
-address you can reproduce this.<P>
-</blockquote>
-
-Some future release of fetchmail may work around this bug, but don't
-hold your breath.<P>
+If you want these fixed, go bug the Evil Empire.<P>
 
 <hr>
 <h2><a name="R1">R1. I think I've set up fetchmail correctly, but I'm not getting any mail.</a></h2>
@@ -1312,7 +1304,7 @@ are downloaded.<P>
 <table width="100%" cellpadding=0><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: 1997/09/14 19:28:00 $
+<td width="30%" align=right>$Date: 1997/09/14 20:31:17 $
 </table>
 
 <P><ADDRESS>Eric S. Raymond <A HREF="mailto:esr@thyrsus.com">&lt;esr@snark.thyrsus.com&gt;</A></ADDRESS>