Tickets :: [#2926] New IMAP Class defaults to CRAM-MD5?

6.0.0-alpha14

7/3/25

Summary	New IMAP Class defaults to CRAM-MD5?
Queue	IMP
Queue Version	HEAD
Type	Bug
State	Not A Bug
Priority	2. Medium
Owners	slusarz (at) horde (dot) org
Requester	jason (at) dixongroup (dot) net
Created	11/06/2005 (7179 days ago)
Due
Updated	02/09/2009 (5988 days ago)
Assigned	11/06/2005 (7179 days ago)
Resolved	12/10/2005 (7145 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

02/09/2009 05:58:09 AM	ksjulian (at) gmail (dot) com	Comment #10	Reply to this comment
i also facing this problem. my email server is vpopmail. Auth: CRAM-MD5. I can login in other's email client but horde cannot

12/10/2005 07:32:31 AM	Michael Slusarz	Comment #9 State ⇒ Not A Bug	Reply to this comment
No feedback.

11/29/2005 09:53:09 PM	Michael Slusarz	Comment #8 Version ⇒ HEAD Queue ⇒ IMP	Reply to this comment
Switching to IMP as all development of IMAP_Client is currently occuring there - changes are ported into MIMP as they stabilize.

11/13/2005 08:49:51 PM	Michael Slusarz	Comment #7	Reply to this comment
sorry - just realized this was reported as an issue in MIMP. Is this happening in IMP also (this will only be a factor if you are using a cvs version of IMP).

11/13/2005 08:48:26 PM	Michael Slusarz	Comment #6	Reply to this comment
You should place a print_r($results) on line 529 of imp/lib/IMAP/Client.php and report the results.

11/07/2005 12:19:50 AM	jason (at) dixongroup (dot) net	Comment #5	Reply to this comment
Yes, it supports CRAM-MD5. It is an OS X Server (10.3.9) running Cyrus. I usually just use PLAIN/LOGIN since connections have to be made only on the local network (either via VPN or through HTTPS webmail). I've confirmed that CRAM-MD5 is working fine via fetchmail: # fetchmail -c -p imap --auth cram-md5 -u jdixon mailserver Enter password for jdixon@mailserver: 1199 messages (7 seen) for jdixon at mailserver. However, here are the relevant messages when I try MIMP (HEAD or 1.0_ALPHA): Nov 6 16:07:04 mailserver PasswordService: incorrect digest response Nov 6 16:07:04 mailserver imap[1028]: badlogin: dmzweb1.raba.com [10.0.0.201] CRAM-MD5 This suggests an incorrect password, but it's the same password I always use for our production Horde system (both use IMAP).

11/06/2005 11:29:44 PM	Michael Slusarz	Comment #4 State ⇒ Feedback	Reply to this comment
I can verify that IMAP_Client connects just fine via CRAM-MD5 to a correctly setup IMAP server. It is likely that your IMAP server is incorrectly identifying that it can handle CRAM-MD5 passwords - actually, a better way to phrase this is that your IMAP server can handle the CRAM-MD5 authentication exchange fine, but the issue is with the authentication db your IMAP server is connecting to. A quick test to determine if your IMAP server should broadcast CRAM-MD5 is as follows: Does the authentication DB that your IMAP server connect to store its passwords in cleartext. If the answer is no, then you can not use CRAM-MD5.

11/06/2005 09:08:12 PM	jason (at) dixongroup (dot) net	Comment #3	Reply to this comment
Just tested MIMP_1_0_ALPHA, same problem.

11/06/2005 10:42:12 AM	Jan Schneider	Version ⇒ HEAD

11/06/2005 10:40:35 AM	Jan Schneider	Assigned to Michael Slusarz State ⇒ Assigned

11/06/2005 05:04:01 AM	jason (at) dixongroup (dot) net	Comment #2	Reply to this comment
Sorry, I should have mentioned this is on HEAD.

11/06/2005 05:03:29 AM	jason (at) dixongroup (dot) net	Comment #1 Priority ⇒ 2. Medium Type ⇒ Bug Summary ⇒ New IMAP Class defaults to CRAM-MD5? Queue ⇒ MIMP State ⇒ Unconfirmed	Reply to this comment
I'm getting the following error when trying to login. I tailed the mailserver log and noticed that this version is trying CRAM-MD5 instead of LOGIN. I don't see any options to override this behavior in config/*. Am I getting cut by the bleeding edge (new IMAP Class)? :) "MSG: Could not retrieve namespace information from IMAP server."