diff options
| author | Matthias Andree <matthias.andree@gmx.de> | 2012-11-06 08:44:50 +0100 |
|---|---|---|
| committer | Matthias Andree <matthias.andree@gmx.de> | 2012-11-06 08:44:50 +0100 |
| commit | 6463caede766da351104ef421c0bcea52d4c4ba7 (patch) | |
| tree | 6658c9fa3d10062adcc30b7aa5a04c5c9add1352 /fetchmail-FAQ.html | |
| parent | 39a6664bb026d3ecb54bae73794a3537c7ce0f51 (diff) | |
| download | fetchmail-6463caede766da351104ef421c0bcea52d4c4ba7.tar.gz fetchmail-6463caede766da351104ef421c0bcea52d4c4ba7.tar.bz2 fetchmail-6463caede766da351104ef421c0bcea52d4c4ba7.zip | |
Fix typo in R15, and clarify.
Diffstat (limited to 'fetchmail-FAQ.html')
| -rw-r--r-- | fetchmail-FAQ.html | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html index c57438fc..6b425ea2 100644 --- a/fetchmail-FAQ.html +++ b/fetchmail-FAQ.html @@ -2532,10 +2532,11 @@ 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> +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.</p> <p><strong>Solution:</strong> Configure the right authentication scheme explicitly, for instance, with <kbd>--auth cram-md5</kbd> or <kbd>--auth |