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): Error: Couldn't create mailbox list lock /tmp/tmp0Y5TMn/dovecot1/users/user1 at domain.com/imapc/mailboxes.lock: file_create_locked(/tmp/tmp0Y5TMn/dovecot1/users/user1 at domain.com/imapc/mailboxes.lock) failed: safe_mkstemp(/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. Client commands to reproduce: a LOGIN username password b CREATE INBOX/folder John -----Original Message----- From: dovecot [mailto:dovecot-bounces at dovecot.org] On Behalf Of Timo Sirainen Sent: Monday, 30 April, 2018 16:11 To: dovecot-news at dovecot.org; Dovecot Mailing List <dovecot at dovecot.org> Subject: v2.2.36 release candidate released https://dovecot.org/releases/2.2/rc/dovecot-2.2.36.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.36.rc1.tar.gz.sig v2.2.36 is hopefully going to be the last v2.2.x release. Please test this RC well, so we'll have a good final release! v2.3.2 is still going to take a couple of months before it's ready. * login-proxy: If ssl_require_crl=no, allow revoked certificates. Also don't do CRL checks for incoming client certificates. * stats plugin: Don't temporarily enable PR_SET_DUMPABLE while opening /proc/self/io. This may still cause security problems if the process is ptrace()d at the same time. Instead, open it while still running as root. + doveadm: Added mailbox cache decision&remove commands. See doveadm-mailbox(1) man page for details. + doveadm: Added rebuild attachments command for rebuilding $HasAttachment or $HasNoAttachment flags for matching mails. See doveadm-rebuild(1) man page for details. - dsync: Lock file generation failed if home directory didn't exist - Snippet generation for HTML mails didn't ignore &entities inside blockquotes, producing strange looking snippets. - imapc: Fix assert-crash if getting disconnected and after reconnection all mails in the selected mailbox are gone. - pop3c: Handle unexpected server disconnections without assert-crash - fts: If mails contained NUL characters, the text around it wasn't indexed. - Obsolete dovecot.index.cache offsets were sometimes used. Trying to fetch a field that was just added to cache file may not have always found it.
On 2 May 2018, at 12.52, John van der Kamp <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): Error: Couldn't create mailbox list lock /tmp/tmp0Y5TMn/dovecot1/users/user1 at domain.com/imapc/mailboxes.lock: file_create_locked(/tmp/tmp0Y5TMn/dovecot1/users/user1 at domain.com/imapc/mailboxes.lock) failed: safe_mkstemp(/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 <https://github.com/dovecot/core/commit/27366c1b4258a8b3becfb1c3e30b0d3aa8798daa> -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20180503/47707615/attachment.html>
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>