v2.2.36 release candidate released

[John van der Kamp]

Thanks, that fixes it for me.

 
John

 
From: dovecot [mailto:dovecot-bounces at dovecot.org] On Behalf Of Timo Sirainen
Sent: Thursday, 3 May, 2018 13:52
To: John van der Kamp <jkamp at amazon.nl>
Cc: Dovecot Mailing List <dovecot at dovecot.org>
Subject: Re: v2.2.36 release candidate released

 
On 2 May 2018, at 12.52, John van der Kamp <jkamp at amazon.nl <mailto:jkamp at amazon.nl> > wrote:

 
There seems to be a problem with new user directories and the imapc backend. On a test setup I get the following error in the log:

May 02 10:09:58 imap(user1 at domain.com <mailto:user1 at domain.com> ): Error: Couldn't create mailbox list lock /tmp/tmp0Y5TMn/dovecot1/users/user1 at domain.com <mailto:tmp/tmp0Y5TMn/dovecot1/users/user1 at domain.com> /imapc/mailboxes.lock: file_create_locked(/tmp/tmp0Y5TMn/dovecot1/users/user1 at domain.com <mailto:tmp/tmp0Y5TMn/dovecot1/users/user1 at domain.com> /imapc/mailboxes.lock) failed: safe_mkstemp(/tmp/tmp0Y5TMn/dovecot1/users/user1 at domain.com <mailto:tmp/tmp0Y5TMn/dovecot1/users/user1 at domain.com> /imapc/mailboxes.lock) failed: No such file or directory

The 'imapc' part in the user directory is not there (yet), and so the mailboxes.lock file cannot be created. A [SERVERBUG] Internal error occurred is returned to the client.
This may have already been broken in an earlier release.
Older releases don't seem to have the mailbox lock at this point, so they don't return an error when the imapc directory is not there yet.

 
Should be fixed by https://github.com/dovecot/core/commit/27366c1b4258a8b3becfb1c3e30b0d3aa8798daa

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dovecot.org/pipermail/dovecot/attachments/20180503/ae6a50ab/attachment.html>