fix another typo, point one URL to CVE.

[~andy/fetchmail] / fetchmail-FAQ.html

diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html
index a57e4583e859351d8a74c1c70b60ba0c825d69ee..c57438fc2f58ffb079e61712488d0e6f209ea0d8 100644 (file)
--- a/fetchmail-FAQ.html
+++ b/fetchmail-FAQ.html
@@ -188,6 +188,7 @@ messages but before deleting them</a><br/>
     errors.</a><br />
 <a href="#R13">R13. What does "Interrupted system call" mean?</a><br />
 <a href="#R14">R14. Since upgrading fetchmail/OpenSSL, I can no longer connect!</a><br />
+<a href="#R15">R15. Help, I'm getting Authorization failure!</a><br />
 
 <h2 id="C_H">Hangs and lockups</h2>
 
@@ -2002,6 +2003,15 @@ sorts of strange effects, for instance, your sent mail may show up in
 the mail that fetchmail fetches. It's best to avoid fetching mail from
 Google until they are using standards-compliant software.</p>
 
+<p>If you still need to use Google's mail service, these links may help (valid as of 2011-04-13):</p>
+<ul>
+    <li><a href="http://mail.google.com/support/bin/topic.py?hl=en&amp;topic=12805">Other ways to access Gmail &gt; POP</a></li>
+    <li><a href="http://mail.google.com/support/bin/topic.py?hl=en&amp;topic=12806">Other ways to access Gmail &gt; IMAP</a></li>
+<li><a href="http://mail.google.com/support/bin/answer.py?hl=en&amp;answer=47948">Using POP on multiple clients or mobile devices</a></li>
+<li><a href="http://mail.google.com/support/bin/answer.py?hl=en&amp;answer=13291">Some [POP3] mail was not downloaded</a></li>
+<li><a href="http://mail.google.com/support/bin/answer.py?hl=en&amp;answer=78774">I'm having problems downloading [IMAP] mail</a></li>
+</ul>
+
 <hr/>
 <h1>How to set up well-known security and authentication
 methods</h1>
@@ -2505,6 +2515,37 @@ option is <kbd>--sslcertpath /home/hans/certs</kbd> on the commandline and
 env PATH=/opt/openssl1.0.0/bin /opt/openssl1.0.0/bin/c_rehash /home/hans/certs
 </pre>
 
+<h2><a id="R15" name="R15">R15. Help, I'm getting Authorization failure!</a></h2>
+
+<p>First, try upgrading to fetchmail 6.3.18 or newer. Release 6.3.18 has
+received a considerable number of bug fixes for the authentication
+feature (AUTH, AUTHENTICATE, SASL). Most notably, fetchmail aborts SASL
+authentication attempts properly with an asterisk if it detects that it
+cannot make progress with a particular authentication scheme. This fixes
+issues where GSSAPI-enabled fetchmail cannot authenticate against
+Microsoft Exchange 2007 and 2010. <strong>Note</strong> that this is a
+bug in old fetchmail versions!</p>
+
+<p>Fetchmail by default attempts to authenticate using various schemes.
+Fetchmail tries these schemes in order of descending security, meaning
+the most secure schemes are tried first.</p>
+
+<p>However, sometimes the server offers a secure authentication scheme
+that is not properly configured, or an authentication scheme such as
+GSSAPI does requires credentials to be acquired externally. In some
+situations, fetchmail cannot know the scheme will fail without trying
+it. In most cases, fetchmail should proceed to the next authentication
+scheme automatically, but this sometimes does not work.</p>
+
+<p><strong>Solution:</strong> Configure the right authentication scheme
+explicitly, for instance, with <kbd>--auth cram-md5</kbd> or <kbd>--auth
+    password</kbd> on the command line or <code>auth "cram-md5"</code> or
+       <code>auth "password"</code> in the rcfile. Details can be found
+       in the manual page.<br />
+       <strong>Note</strong> that auth password should only be used
+       across secure links (see the sslcertck and ssl/sslproto options).
+       </p>
+
 <hr/>
 <h1>Hangs and lockups</h1>
 <h2><a id="H1" name="H1">H1. Fetchmail hangs when used with
@@ -2560,7 +2601,7 @@ configuration of sendmail. You must enable the 'nodns' and
 <h2><a id="H3" name="H3">H3. Fetchmail hangs while fetching
 mail.</a></h2>
 
-<p>The symption: 'fetchmail -v' retrieves the first few messages,
+<p>Symptom: 'fetchmail -v' retrieves the first few messages,
 but hangs returning:</p>
 
 <pre>