On 13.7.2004, at 16:07, Christian Balzer wrote:
Ah, ok. The abortion was probably because of that, but the error message about locking was because another session was trying to access the same mailbox at the same time.
Right. Well, sort of. That lock persists for minutes, certainly longer than 30 seconds. Unless the client realizes that it has been cut off and retries again and again and thus keeps the lock active basically all the time. Alas, if it was dovecot which did cut the connection, shouldn't it have also released the lock at the same time? Or was/is that shortcoming part of the bug?
It should have released the lock and the process should have died. So I'm not exactly sure why the error message would come, unless the client actually did try to create many connections at the same time. Luckily this can't happen with 1.0-tests anymore.