On Sun, Jul 7, 2013 at 4:10 PM, Axel Luttgens <AxelLuttgens@swing.be> wrote:
Hello Dotan,
Note that md5sum calculates a hash similar to the one used by dovecot's MD5-PLAIN scheme:
$ doveadm pw -s PLAIN-MD5 -p 12345 {PLAIN-MD5}827ccb0eea8a706c4c34a16891f84e7bShouldn't that password match the md5sum check?
As a result: no... ;-)
I see! I've tried a few formats to verify the MD5 hash, but none produced the expected results. In any case, I've gotten that part of Dovecot working now that I've discovered that most of the information online is for Dovecot 1. However the Dovecot 2 wiki is terrific and it pulled me through.
[...] $ telnet mail.someDomain.com 143 Trying x.x.x.x... Connected to mail.someDomain.com. Escape character is '^]'.
- OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN] Dovecot ready. a login user 12345 [...]
I doubt this is a valid attempt:
- unless I'm wrong, the command should be authenticate (not login)
No, it does seem that 'login' is the right command. I've got it working now.
- the server doesn't seem to be configured for making use of digest-md5
You may find an example of such an authentication near the end of http://tools.ietf.org/html/rfc2831. You might also have a look at http://wiki2.dovecot.org/Authentication/Mechanisms/DigestMD5.
Thank you, that was indeed part of the issue!
-- Dotan Cohen