From owner-freebsd-questions Sat Feb 17 13:21:45 2001 Delivered-To: freebsd-questions@freebsd.org Received: from relay2.inwind.it (relay2.inwind.it [212.141.53.73]) by hub.freebsd.org (Postfix) with ESMTP id EBF8437B491 for ; Sat, 17 Feb 2001 13:21:40 -0800 (PST) Received: from [62.98.53.238] (62.98.53.238) by relay2.inwind.it (5.1.056) id 3A4739BB000E3C69 for freebsd-questions@freebsd.org; Sat, 17 Feb 2001 22:21:39 +0100 Received: (qmail 376 invoked by uid 1001); 17 Feb 2001 21:21:10 -0000 Date: Sat, 17 Feb 2001 22:21:10 +0100 From: Francesco Casadei To: freebsd-questions@freebsd.org Subject: fetchmail & CRAM-MD5 Message-ID: <20010217222110.A327@junior.kasby> Mail-Followup-To: freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="0OAP2g/MAC+5xKAE" Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 3.5-STABLE i386 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I have a problem with fetchmail and CRAM-MD5 authentication. I can't login = to an imap server because authentication fails (invalid username or password). I think ~/.fetchmailrc is ok, since I was been able to fetch mail from the imap server for about 3-4 weeks, before it stopped working WITHOUT any upgrade or modification to the config file. Since that server is also POP3-capable I simply changed the proto option in ~/fetchmailrc to pop3. No problems with that. Now I have the same problem even with pop servers! I upgraded fetchmail to version 5.6.5 and the new authentication module uses the most secure option supported by the server. When I fetch mail from a pop server: - fetchmail sends USER username - the server requests password - fetchmail sends AUTH - the server lists its capability - fetchmail detects CRAM-MD5 authentication and uses it. Booom! "invalid user or password". This happens only with 2 pop server: pop.tiscalinet.it and popmail.inwind.i= t. The other servers work well: pop.libero.it and mail.monrif.net. I reinstalled fetchmail-5.0.5 from the FreeBSD 3.3-RELEASE 4 cd set and it works with the old "good" POP3. Is it possible that the problem is related to the crypto library? I'm running FreeBSD 3.5-STABLE: # uname -a FreeBSD junior.kasby 3.5-STABLE FreeBSD 3.5-STABLE #5: Sun Feb 4 17:43:12 CET 2001 root@junior.kasby:/usr/src/sys/compile/JUNIOR i386 I'm using MD5-based crypto libraries (according to section 8.4 of the handbook): # cd /usr/lib # ll *crypt* lrwxr-xr-x 1 root wheel 11 Feb 16 22:31 libcrypt.a -> libscrypt.a lrwxr-xr-x 1 root wheel 13 Jan 4 12:10 libcrypt.so -> libcrypt.so.2 lrwxr-xr-x 1 root wheel 14 Feb 16 22:32 libcrypt.so.2 -> libscrypt.so= .2 lrwxr-xr-x 1 root wheel 13 Feb 16 22:33 libcrypt_p.a -> libscrypt_p.a -r--r--r-- 1 root wheel 13018 Feb 4 17:49 libdescrypt.a lrwxr-xr-x 1 root wheel 16 Feb 4 17:49 libdescrypt.so -> libdescrypt= .so.2 -r--r--r-- 1 root wheel 12965 Feb 4 17:49 libdescrypt.so.2 -r--r--r-- 1 root wheel 14750 Feb 4 17:49 libdescrypt_p.a -r--r--r-- 1 root wheel 6194 Feb 4 17:49 libscrypt.a lrwxr-xr-x 1 root wheel 14 Feb 4 17:49 libscrypt.so -> libscrypt.so.2 -r--r--r-- 1 root wheel 7579 Feb 4 17:49 libscrypt.so.2 -r--r--r-- 1 root wheel 6684 Feb 4 17:49 libscrypt_p.a Any ideas? Francesco Casadei --=20 You can download my public key from http://digilander.iol.it/fcasadei/ or retrieve it from a keyserver (pgpkeys.mit.edu, wwwkeys.pgp.net, ...) Key fingerprint is: 1671 9A23 ACB4 520A E7EE 00B0 7EC3 375F 164E B17B --0OAP2g/MAC+5xKAE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6jutGfsM3XxZOsXsRAiPMAKCUgO6mRaWUAXYHmuBW7BPW7xor9gCeMxRg pO/TAzronD+JdrjlpwdsUdE= =09ux -----END PGP SIGNATURE----- --0OAP2g/MAC+5xKAE-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message