[Dovecot] How to handle "Waiting for authentication process..."
Sometimes, when dovecot authentication processes are busy, dovecot write reply "Waiting for authentication process to respond.." to client. Roundcube webmail do not understand it and invalidate user session. My question is what is a good practise to handle this situation by client software? One Roundcube user proposes to detect such response then wait a moment and try again. Is there any standard for this? How long should we wait? More info here: http://trac.roundcube.net/ticket/1487450 -- Aleksander 'A.L.E.C' Machniak LAN Management System Developer [http://lms.org.pl] Roundcube Webmail Developer [http://roundcube.net] --------------------------------------------------- PGP: 19359DC1 @@ GG: 2275252 @@ WWW: http://alec.pl
On 8.12.2010, at 8.59, A.L.E.C wrote:
Sometimes, when dovecot authentication processes are busy, dovecot write reply "Waiting for authentication process to respond.." to client. Roundcube webmail do not understand it and invalidate user session.
That's an untagged reply. What kind of an authentication do you have anyway that causes this to be an actual problem?
My question is what is a good practise to handle this situation by client software? One Roundcube user proposes to detect such response then wait a moment and try again. Is there any standard for this? How long should we wait?
That is not an authentication failure. It's sent only when the authentication itself isn't immediately available.
More info here: http://trac.roundcube.net/ticket/1487450
I don't see an actual problem here. Just ignore all untagged replies until the client gets the tagged reply to the command it sent. It seems more like an IMAP client is freaking out when it sees an untagged reply that it\s not expecting.
On 08.12.2010 10:07, Timo Sirainen wrote:
I don't see an actual problem here. Just ignore all untagged replies until the client gets the tagged reply to the command it sent. It seems more like an IMAP client is freaking out when it sees an untagged reply that it\s not expecting.
Arghhh, I see. We've got a bug in the code. After sending AUTHENTICATE command we're reading only one line of response and we're checking if it starts with '+' character. If not, we assume that authentication was not successful. This doesn't happen when SASL-IR is used. Thanks. -- Aleksander 'A.L.E.C' Machniak LAN Management System Developer [http://lms.org.pl] Roundcube Webmail Developer [http://roundcube.net] --------------------------------------------------- PGP: 19359DC1 @@ GG: 2275252 @@ WWW: http://alec.pl
participants (2)
-
A.L.E.C
-
Timo Sirainen