------- You are receiving this mail because: -------
You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=1512
--- Comment #4 from Mildred Ki'Lya <mildred-bug.exim@???> 2014-07-31 07:28:52 ---
Here is a link to the auth protocol for both dovecot 1 and dovecot 2:
http://wiki1.dovecot.org/Authentication%20Protocol
http://wiki2.dovecot.org/Design/AuthProtocol
Both are showing the client speaking first in the handshake (but both are for
version 1.1 of the protocol and not 1.0). In any case, I don't think it could
break anything. If dovecot isn't expecting the client to talk until it finished
its own handshake, the request should be buffered. File sockets are buffered,
right?
Also, please note that I have another setup with exim 4.80 and dovecot 2.1.17
and authentication is working well in that case. I wouldn't be so sure that
dovecot changed its implementation. I'd think that there is something specific
in the configuration that makes this setup fail (for some unknown reason).
Also, I took the $auth1 in the PLAIN mechanism from
http://wiki2.dovecot.org/HowTo/EximAndDovecotSASL (and my other server
configuration, the one that is working). I'm currently trying with $auth2 but I
wouldn't hold my breath.
I also raised the issue at dovecot mailing lists. I'll try to find with them
what causes dovecot to behave differently. But them, maybe exim implementation
could be made a little bit more robust.
See:
http://dovecot.org/pipermail/dovecot/2014-July/097274.html
--
Configure bugmail:
http://bugs.exim.org/userprefs.cgi?tab=email
