Charles Bueche <cbueche(_at_)worldcom(_dot_)ch> writes:
Hi all,
One one side, I can use my fetchmail 5.6.2 to go to one of our UW imap
server (running IMAP4rev1 v12.264), but when I try to go to the 2nd
server (running IMAP4rev1 2000.283), it fails. Details :
[...]
You need the patch below. I sent this a while back when someone else
had the same problem, but it doesn't seem to have been applied to
the source, yet. The patch is against an older version of fetchmail,
probably 5.5.5...
Todd
Matthias Scheler <tron(_at_)zhadum(_dot_)de> writes:
Hello,
fetchmail 5.5.5 doesn't work with the latest UW IMAP software version
2000 (see "http://www.washington.edu/imap/";) because (at least) CRAM-MD5
authentification fails. I contacted the author of the UW IMAP software
Mark Crispin (mrc(_at_)cac(_dot_)washington(_dot_)edu) first but he told me
that his
server is behaving right by RFC 2060, section 2.2.2, fifth paragraph:
A client MUST be prepared to accept any server response at all times.
This includes server data that was not requested.
Please try this patch:
--- imap.c~ Tue Sep 26 04:03:23 2000
+++ imap.c Sun Nov 12 13:22:39 2000
@@ -825,13 +825,11 @@
strcat (buf1, "\r\n");
SockWrite (sock, buf1, strlen (buf1));
- if ((result = gen_recv (sock, buf1, sizeof (buf1))))
- return result;
-
- if (strstr (buf1, "OK")) {
- return PS_SUCCESS;
+ result = imap_ok (sock, NULL);
+ if (result == PS_SUCCESS) {
+ return result;
} else {
- return PS_AUTHFAIL;
+ return PS_AUTHFAIL;
}
}
Assuming this works, something similar needs to be done to the rest
of the SASL mechanisms as well...
Todd