X-Git-Url: http://pileus.org/git/?a=blobdiff_plain;f=fetchmail-FAQ.html;h=c57438fc2f58ffb079e61712488d0e6f209ea0d8;hb=b06abacf4b2e334131e5743c0e4ea27ad2829f02;hp=48449fc661cb7eaaad0c66983d7044a95beed06d;hpb=b32ab998cc4884e8f7aa804e814b04780c19da80;p=~andy%2Ffetchmail diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html index 48449fc6..c57438fc 100644 --- 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.

+

If you still need to use Google's mail service, these links may help (valid as of 2011-04-13):

+ +

How to set up well-known security and authentication methods

@@ -2508,6 +2517,15 @@ env PATH=/opt/openssl1.0.0/bin /opt/openssl1.0.0/bin/c_rehash /home/hans/certs

R15. Help, I'm getting Authorization failure!

+

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. Note that this is a +bug in old fetchmail versions!

+

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.