[Dovecot] Inactivity, Thunderbird -> bad password

[Peter Veerman]

>>>>> I'm running dovecot rc13 now on sparc64, freebsd 6.1-STABLE
>>>>>
>>>>> When i'm connected with my 5 accounts to my dovecot imap over ssl/tls
>>>>> server i get the following message in my logs:
>>>>> Nov 18 15:25:47 Info: imap-login: Disconnected: Inactivity: rip=x.x.x.x,
>>>>> lip=x.x.x.x, TLS
>>>>> My client (thunderbird) then re-requests my password for only one of the
>>>>> 5 accounts.
>>>>>     
>>>>>         
>>>>>           
>>>> Try if this patch helps:
>>>>
>>>> http://dovecot.org/list/dovecot-cvs/2006-November/006895.html
>>>>
>>>> Can't really think of anything else. It means that from Dovecot's point
>>>> of view the client didn't send authentication command at all.
>>>>       
>>>>         
>>> It didn't help :( the only difference because of the patch is that i
>>> don't get the inactivity error anymor in the logs,
>>>  instead of that I _only_ get the following message:
>>>
>>> Nov 19 12:18:10 Info: IMAP(user at domain): Disconnected
>>>     
>>>       
>> This means that the login succeeded, and the client just disconnected.
>>
>>   
>>     
>>> For the sake of clarity; this and the previous error happens after being
>>> logged in for quite a while (about 25 minutes) on randomly one of my
>>> five imap mailboxes.
>>>     
>>>       
>> Might as well be Thunderbird doing something broken..
>>   
>>     
> After restarting both Dovecot and Thunderbird the error already has not
> occurred anymore for 3 hours already, while the error popped up every 25
> minutes or so... I think it is safe to say though that the patch solved
> the problem.
>
> Timo: Thanx!
>
>   
Okay :(

The problem remained. I had to -not- use Thunderbird for a long time in
order for dovecot to put the Inactivity and Disconnected in IDLE
messages. And again one of my accounts randomly suddenly asks for its
password.
(It occurs happens with dovecot only and not with Courier-IMAP so
although thunderbird might be the problem there is a way to solve it.)

In my logs I see:
Nov 19 17:22:13 Info: IMAP(userA at domain): Disconnected
Nov 19 17:22:13 Info: IMAP(userB at domain): Disconnected
Nov 19 17:22:13 Info: IMAP(userC at domain): Disconnected
Nov 19 17:32:10 Info: imap-login: Disconnected: Inactivity:
rip=88.211.149.123, lip=62.45.54.4, TLS
Nov 19 17:32:13 Info: IMAP(userA at domain): Disconnected in IDLE
Nov 19 17:32:13 Info: IMAP(userC at domain): Disconnected in IDLE
Nov 19 17:32:13 Info: IMAP(userB at domain): Disconnected in IDLE
Nov 19 17:32:13 Info: IMAP(userD at domain): Disconnected in IDLE
Nov 19 17:32:13 Info: IMAP(userE at domain): Disconnected
Nov 19 17:32:13 Info: IMAP(userD at domain): Disconnected in IDLE
Nov 19 17:32:13 Info: IMAP(userF at domain): Disconnected
Nov 19 17:32:13 Info: IMAP(userF at domain): Disconnected in IDLE
Nov 19 17:32:13 Info: IMAP(userA at domain): Disconnected in IDLE
Nov 19 17:32:13 Info: IMAP(userB at 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?

Peter