aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMatthias Andree <matthias.andree@gmx.de>2010-09-27 13:14:11 +0200
committerMatthias Andree <matthias.andree@gmx.de>2010-09-27 13:14:11 +0200
commitb32ab998cc4884e8f7aa804e814b04780c19da80 (patch)
tree74353e2cf8deff812687271b499a7205f14c434a
parent7276a0f7f39efacfc45a27783b3516bdbee29025 (diff)
downloadfetchmail-b32ab998cc4884e8f7aa804e814b04780c19da80.tar.gz
fetchmail-b32ab998cc4884e8f7aa804e814b04780c19da80.tar.bz2
fetchmail-b32ab998cc4884e8f7aa804e814b04780c19da80.zip
Revise FAQ R15 a little bit.
-rw-r--r--fetchmail-FAQ.html4
1 files changed, 3 insertions, 1 deletions
diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html
index e78e566e..48449fc6 100644
--- a/fetchmail-FAQ.html
+++ b/fetchmail-FAQ.html
@@ -2515,7 +2515,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