Note Earl's regression fix for SSL_CTX_clear_options() on older OpenSSL.

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

diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html
index e78e566ef85171ef31c01b1f8e6a77fd4bcdce82..c57438fc2f58ffb079e61712488d0e6f209ea0d8 100644 (file)
--- a/fetchmail-FAQ.html
+++ b/fetchmail-FAQ.html
@@ -2003,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>
@@ -2508,6 +2517,15 @@ env PATH=/opt/openssl1.0.0/bin /opt/openssl1.0.0/bin/c_rehash /home/hans/certs
 
 <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>
@@ -2515,7 +2533,9 @@ 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.</p>
+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