Issue 6509 in k9mail: CRAM-MD5 broken in 5.0

[k9m...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Product-k9mail

New issue 6509 by bb00200: CRAM-MD5 broken in 5.0
https://code.google.com/p/k9mail/issues/detail?id=6509

[b]What's going wrong?[/b]
Cannot authenticate to my server over IMAP when using K9 5.0.


[b]What steps will reproduce the problem?[/b]
1. Attempt to connect to a server supporting CRAM-MD5 authentication


[b]What do you expect to have happen?[/b]
Connection to succeed. Mail to be sent/received.


[b]What do you see instead?[/b]
K9 claims server does NOT support CRAM-MD5 and closes the connection.


[b]What version of K-9 are you using?[/b]
5.0


[b]What is your device and what version of Android are you using?[/b]
Nexus 5 running CM11 M9.


[b]Is your email account a POP account, Exchange Account or an IMAP
account?[/b]
IMAP with supported authentication methods CRAM-MD5, CRAM-SHA1, CRAM-SHA256.


[b]What else should we know?[/b]
Tried rebooting phone same result. Used Titanium backup to restore 4.804
and mail instantly works again.



--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[k9m...@googlecode.com]

Comment #1 on issue 6509 by jsteele...@gmail.com: CRAM-MD5 broken in 5.0
https://code.google.com/p/k9mail/issues/detail?id=6509

Is this the exact message?

"Server doesn't support encrypted passwords using CRAM-MD5."

This occurs when the authentication method configured in K-9 Mail
is "Encrypted password" (which used to be called "CRAM_MD5") but the server
doesn't profess to
support CRAM_MD5 in its CAPABILITY response. K-9 Mail no longer attempts
to authenticate using methods that are not in the server's CAPABILITY
response (this is the same behavior as in Thunderbird).

A debug log would help diagnose the problem. Knowing the type of IMAP
server would also help with tracking this issue.

[k9m...@googlecode.com]

Comment #2 on issue 6509 by bb00200: CRAM-MD5 broken in 5.0
https://code.google.com/p/k9mail/issues/detail?id=6509

You're correct! To think I had my courier capability strings incorrect all
these years. I apparently removed *all* auth methods from the capability
string. /facepalm

Spent the last 30 minutes pouring over my email configs. Looks like the
only thing I messed up at some point in the past. Odd how everything has
been working using cram-md5 until today when k9 updated to 5.0. Oh, well
everything is correct now. Sorry about the invalid bug report.

[k9m...@googlecode.com]

Updates:
Status: Done

Comment #3 on issue 6509 by cketti: CRAM-MD5 broken in 5.0
https://code.google.com/p/k9mail/issues/detail?id=6509

(No comment was entered for this change.)