X-Git-Url: http://pileus.org/git/?a=blobdiff_plain;f=fetchmail-FAQ.html;h=6b425ea2c376cc9b7d049e76044f250bcaa9c6be;hb=7f6138ffd4935043382ce5f867ee9e177e0a9787;hp=c77f7900548f58f57ec1b91710cec3f1e7a932c1;hpb=5ac9f090d23e2b017aaf9c8025c4eaea7de7a388;p=~andy%2Ffetchmail diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html index c77f7900..6b425ea2 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

@@ -2523,10 +2532,11 @@ the most secure schemes are tried first.

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.

+GSSAPI that requires credentials to be acquired externally. In some +situations, fetchmail cannot know that the scheme will fail beforehand, +without trying it. In most cases, fetchmail should proceed to the next +authentication scheme automatically, but this sometimes does not +work.

Solution: Configure the right authentication scheme explicitly, for instance, with --auth cram-md5 or --auth