diff options
author | Eric S. Raymond <esr@thyrsus.com> | 2001-02-15 23:10:02 +0000 |
---|---|---|
committer | Eric S. Raymond <esr@thyrsus.com> | 2001-02-15 23:10:02 +0000 |
commit | fe4cafeb17701dad78da08d8a4618cc70adb6664 (patch) | |
tree | 6eb8ec0b3fee53140348efdcf4d38926e4f08c67 /pop3.c | |
parent | 73a4db1005a730f9dce9becb7da457b8ae8aa209 (diff) | |
download | fetchmail-fe4cafeb17701dad78da08d8a4618cc70adb6664.tar.gz fetchmail-fe4cafeb17701dad78da08d8a4618cc70adb6664.tar.bz2 fetchmail-fe4cafeb17701dad78da08d8a4618cc70adb6664.zip |
Explain the < test.
svn path=/trunk/; revision=3108
Diffstat (limited to 'pop3.c')
-rw-r--r-- | pop3.c | 13 |
1 files changed, 8 insertions, 5 deletions
@@ -198,13 +198,16 @@ int pop3_getauth(int sock, struct query *ctl, char *greeting) /* * AUTH command may return a list of available mechanisms. - * if it doesn't, no harm done. Efficiency hack: most servers - * don't implement this, so don't do it at all unless the - * server advertises APOP with <> in the greeting line. This - * certainly catches IMAP-2000's POP3 gateway. + * if it doesn't, no harm done. + * + * APOP was introduced in RFC 1450, and POP3 AUTH not until + * RFC1734. So the < check is an easy way to prevent AUTH from + * being sent to the more primitive POP3 servers dating from + * RFC 1081 and RFC 1225, which seem more likely to choke on + * it. This certainly catches IMAP-2000's POP3 gateway. * * These authentication methods are blessed by RFC1734, - * POP3 AUTHentication command. + * describing the POP3 AUTHentication command. */ if (strchr(greeting, '<') && gen_transact(sock, "AUTH") == 0) { |