On Sun, 2006-11-19 at 19:30 +0100, Peter Veerman wrote:
Nov 19 17:32:10 Info: imap-login: Disconnected: Inactivity: rip=88.211.149.123, lip=62.45.54.4, TLS
So at least the TLS handshake gets finished.
Nov 19 17:32:13 Info: IMAP(userA@domain): Disconnected in IDLE Nov 19 17:32:13 Info: IMAP(userC@domain): Disconnected in IDLE Nov 19 17:32:13 Info: IMAP(userB@domain): Disconnected in IDLE Nov 19 17:32:13 Info: IMAP(userD@domain): Disconnected in IDLE Nov 19 17:32:13 Info: IMAP(userE@domain): Disconnected Nov 19 17:32:13 Info: IMAP(userD@domain): Disconnected in IDLE Nov 19 17:32:13 Info: IMAP(userF@domain): Disconnected Nov 19 17:32:13 Info: IMAP(userF@domain): Disconnected in IDLE Nov 19 17:32:13 Info: IMAP(userA@domain): Disconnected in IDLE Nov 19 17:32:13 Info: IMAP(userB@domain): Disconnected in IDLE
But after these problems the next line is also in my logs when after these messages another user tries to authenticate: Nov 19 17:35:09 Info: auth-worker(default): mysql: Connected to localhost (postfix)
Could it be that the mysql username-password backend times out and takes it time to reconnect to mysql and in the meantime an account gets the "you have got a wrong password" response?
Maybe.. Set auth_debug=yes and see what happens around the time it logs inactivity?