From b7a995759e5d2dc7741c1352d817b38af5cd1ef7 Mon Sep 17 00:00:00 2001 From: "Eric S. Raymond" Date: Wed, 25 Jul 2001 09:06:23 +0000 Subject: Documentation fixes. svn path=/trunk/; revision=3421 --- fetchmail-FAQ.html | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) (limited to 'fetchmail-FAQ.html') diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html index fb66cac3..f2e3b44e 100644 --- a/fetchmail-FAQ.html +++ b/fetchmail-FAQ.html @@ -10,7 +10,7 @@
Back to Fetchmail Home Page To Site Map -$Date: 2001/07/25 07:18:36 $ +$Date: 2001/07/25 09:06:23 $

Frequently Asked Questions About Fetchmail

@@ -508,7 +508,7 @@ for AUTH=KERBEROS_V4 in the CAPABILITY response.

If you are fetching mail from a CompuServe POP3 account, you can use their RPA authentication (which works much like APOP). See S3 for details. If you are fetching mail from -Microsoft Exchange, you will be able to use NTLM. +Microsoft Exchange using IMAP, you will be able to use NTLM.

Your POP3 server may have the RFC1938 OTP capability to use one-time passwords (if it doesn't, you can get OTP patches for the 2.2 version @@ -1376,10 +1376,11 @@ RFC-compliant server. IMAP is alleged to work OK, though.

Older versions of Exchange are semi-usable. -

Fetchmail supports the proprietary NTLM mode used with M$ Exchange -servers. To enable this, configure fetchmail with the --enable-NTLM -option and recompile it. Note: if you specify a user option value -that looks like `user@domain', the part to the left of the @ will + +

Fetchmail using IMAP supports the proprietary NTLM mode used with +M$ Exchange servers. To enable this, configure fetchmail with the +--enable-NTLM option and recompile it. Specify a user option value +that looks like `user@domain': the part to the left of the @ will be passed as the username and the part to the right as the NTLM domain.

M$ Exchange violates the POP3 RFCs. Its LIST command does not reveal @@ -1465,8 +1466,6 @@ our friends in Redmond.