January 2026 - dovecot

BUG-Report: mysql: SSL support not compiled in (remove ssl_client_ca_file and ssl_client_ca_dir settings) second attempt!
by Klaus Tachtler 13 Jan '26

13 Jan '26

Hello everyone, Problem info: An error occurs, while trying to establish a TLS/SSL secured connection to a database (mariadb), which has the ability to accept TLS/SSL connections. Analysis from Archlinux Gitlab Issue, which could be found under following link by - Toolybird: https://gitlab.archlinux.org/archlinux/packaging/packages/dovecot/-/issues/… > Thanks for reporting. It would appear to be some kind of (upstream?) > bug in the autofoo. The error message can be traced back to > HAVE_MYSQL_SSL being undefined when it should be defined. This is > reflected in log: https://reproducible.archlinux.org/api/v0/builds/946041/log > It took quite some debugging, but adding the following hack before the > autoreconf call appears to make it work: > checking for mysql_ssl_set in -llibmariadb... no > sed -i 's/mysql_driver="libmariadb"/mysql_driver="mariadb"/' m4/ > want_mysql.m4 > After that it now shows: > checking for mysql_ssl_set in -lmariadb... yes Steps to reproduce: 1. Configure dovecot 2.4.2-4 as described below 2. Restart dovecot 2.4.2-4 3. Try send an email (echo "Test-E-Mail" | /usr/sbin/sendmail root) 4. Determine error messages inside dovecot 2.4.2-4-Log > 01 Dec 22 04:57:38 server dovecot[842]: auth: Error: > mysql(db.idmz.tachtler.net): mysql: SSL support not compiled in > (remove ssl_client_ca_file and ssl_client_ca_dir settings) > 02 Dec 22 04:57:38 server dovecot[842]: auth-worker: Error: > mysql(db.idmz.tachtler.net): mysql: SSL support not compiled in > (remove ssl_client_ca_file and ssl_client_ca_dir settings) Additional info: OS version: Archlinux package version(s): dovecot 2.4.2-4 necessary config file part: > 45 sql_driver = mysql > 46 > 47 mysql db.idmz.tachtler.net { > 48 host = db.idmz.tachtler.net > 49 port = 3306 > 50 user = postfixuser > 51 password = geheim > 52 dbname = postfix > 53 ssl = yes > 54 ssl_client_ca_file = /etc/dovecot/ssl/certs/CAcert.pem > 55 ssl_client_cert_file = > /etc/dovecot/ssl/certs/client.idmz.tachtler.net.pem > 56 ssl_client_key_file = > /etc/dovecot/ssl/private/client.idmz.tachtler.net.key.pem > 57 ssl_cipher_list = DHE-RSA-AES256-SHA > 58 } WITHOUT the following line, a database connections is possible and works as expected: > 53 ssl = yes > 54 ssl_client_ca_file = /etc/dovecot/ssl/certs/CAcert.pem > 55 ssl_client_cert_file = > /etc/dovecot/ssl/certs/client.idmz.tachtler.net.pem > 56 ssl_client_key_file = > /etc/dovecot/ssl/private/client.idmz.tachtler.net.key.pem > 57 ssl_cipher_list = DHE-RSA-AES256-SHA Thanky you in advance for your help! Klaus Tachtler. -- --------------------------------------- e-Mail : klaus(a)tachtler.net Homepage: https://www.tachtler.net DokuWiki: https://dokuwiki.tachtler.net ---------------------------------------

1 0

Re: Panic: file imap-sieve-storage.c: line 216 (imap_sieve_add_mailbox_event): assertion failed: (ismt->src_box == NULL || ismt->src_box == src_box)
by Stephen Callaghan 12 Jan '26

12 Jan '26

Having a similar issue: 2.4.2 (0962ed2104) via docker. Causing constant core dumping and my client keeps retrying blocking everything up. Any suggestions on how to identify the cause of the problem? S. Jan 09 19:22:13 imap(SNIP)<555><rn1EcflH+ILwCwUB>: Panic: file imap-sieve-storage.c: line 216 (imap_sieve_add_mailbox_event): assertion failed: (ismt->src_box == NULL || ismt->src_box == src_box) Jan 09 19:22:13 imap(SNIP)<555><rn1EcflH+ILwCwUB>: Error: Raw backtrace: #1 [unw_get_proc_name() failed: -10] -> #2 [unw_get_proc_name() failed: -10] -> #3 [unw_get_proc_name() failed: -10] -> #4 i_panic[0x7f13c0e8b7dd] -> #5 [unw_get_proc_name() failed: -10] -> #6 [unw_get_proc_name() failed: -10] -> #7 [unw_get_proc_name() failed: -10] -> #8 mailbox_save_alloc[0x7f13c11baf52] -> #9 [unw_get_proc_name() failed: -10] -> #10 [unw_get_proc_name() failed: -10] -> #11 cmd_move[0x5572105ab0ca] -> #12 command_exec[0x5572105c33f4] -> #13 [unw_get_proc_name() failed: -10] -> #14 [unw_get_proc_name() failed: -10] -> #15 [unw_get_proc_name() failed: -10] -> #16 [unw_get_proc_name() failed: -10] -> #17 client_handle_input[0x5572105c060c] -> #18 client_input[0x5572105c0847] -> #19 io_loop_call_io[0x7f13c0eb9798] -> #20 io_loop_handler_run_internal[0x7f13c0ebd48a] -> #21 io_loop_handler_run[0x7f13c0eb9aea] -> #22 io_loop_run[0x7f13c0eb9963] -> #23 master_service_run[0x7f13c0d7264b] -> #24 main[0x5572105db2a4] -> #25 [unw_get_proc_name() failed: -10] -> #26 __libc_start_main[0x7f13c0ae4ce0] -> #27 _start[0x5572105a62f0] Jan 09 19:22:13 imap(SNIP)<555><rn1EcflH+ILwCwUB>: Fatal: master: service(imap): child 555 killed with signal 6 (core dumped) Having a similar issue: 2.4.2 (0962ed2104) via docker. Causing constant core dumping and my client keeps retrying blocking everything up. Any suggestions on how to identify the cause of the problem? S. Jan 09 19:22:13 imap(SNIP)<555><rn1EcflH+ILwCwUB>: Panic: file imap-sieve-storage.c: line 216 (imap_sieve_add_mailbox_event): assertion failed: (ismt->src_box == NULL || ismt->src_box == src_box) Jan 09 19:22:13 imap(SNIP)<555><rn1EcflH+ILwCwUB>: Error: Raw backtrace: #1 [unw_get_proc_name() failed: -10] -> #2 [unw_get_proc_name() failed: -10] -> #3 [unw_get_proc_name() failed: -10] -> #4 i_panic[0x7f13c0e8b7dd] -> #5 [unw_get_proc_name() failed: -10] -> #6 [unw_get_proc_name() failed: -10] -> #7 [unw_get_proc_name() failed: -10] -> #8 mailbox_save_alloc[0x7f13c11baf52] -> #9 [unw_get_proc_name() failed: -10] -> #10 [unw_get_proc_name() failed: -10] -> #11 cmd_move[0x5572105ab0ca] -> #12 command_exec[0x5572105c33f4] -> #13 [unw_get_proc_name() failed: -10] -> #14 [unw_get_proc_name() failed: -10] -> #15 [unw_get_proc_name() failed: -10] -> #16 [unw_get_proc_name() failed: -10] -> #17 client_handle_input[0x5572105c060c] -> #18 client_input[0x5572105c0847] -> #19 io_loop_call_io[0x7f13c0eb9798] -> #20 io_loop_handler_run_internal[0x7f13c0ebd48a] -> #21 io_loop_handler_run[0x7f13c0eb9aea] -> #22 io_loop_run[0x7f13c0eb9963] -> #23 master_service_run[0x7f13c0d7264b] -> #24 main[0x5572105db2a4] -> #25 [unw_get_proc_name() failed: -10] -> #26 __libc_start_main[0x7f13c0ae4ce0] -> #27 _start[0x5572105a62f0] Jan 09 19:22:13 imap(SNIP)<555><rn1EcflH+ILwCwUB>: Fatal: master: service(imap): child 555 killed with signal 6 (core dumped)

2 1

Lazy expunge does not work as previously after upgrade from Dovecot 2.3 to 2.4.1
by Peter Milesson 11 Jan '26

11 Jan '26

Hi folks, I upgraded an IMAP server from Dovecot 2.3 to 2.4.1 (Debian 13). I have used the lazy expunge plugin for many years, and after upgrade, it was impossible to get it working as previously. After many trials I got it working sort of, but not as previously. The mail location and driver is the following: mail_home = /data/vmail/%{user | username} mail_driver = sdbox mail_path = ~/dbox Previously I had the following structure ~/dbox (user's mailboxes) ~/expunged (user's expunged emails) After upgrade I had to resort to store expunged messages in the inbox namespace in the hidden folder .EXPUNGED, instead of in a separate structure under ~/expunged. This is something I sincerely dislike, as I want expunged messages separate. Now, when messages are expunged, Dovecot no longer obeys the structure of the mailboxes, and puts all expunged messages in the .EXPUNGED folder. Previously the structure of the ~/expunged folder was a copy of the inbox namespace, but now it is just a large garbage bag. This is really a breaking change, and very unfortunate. I had a retention period of 90 days for expunged messages, mainly as a forensic tool. It has been of great help in correcting users that do not follow company guidelines, and opened insecure/infected archives, even if it's strictly prohibited. It has also rescued whole folder structures with sub folders on several occasions, when the users have inadvertently deleted a main folder, and then emptied trash. Now all expunged messages are stored in one big mess, which is much harder to analyze, and I assume, almost impossible to recover to the original state, if that would be needed. I would like to ask, if it is at all possible to get the equivalent of the previous behavior, and in that case, what the configuration would look like. Any help would be very appreciated. Best regards, Peter

1 0

mail-crypt transition from Dovecot 2.3 to 2.4
by m＠maltris.org 11 Jan '26

11 Jan '26

In Dovecot 2.3 I had used the following query: password_query = \ SELECT USER.user, USER.host, \ SECRET.password, SECRET.public_key AS mail_crypt_global_public_key, SECRET.private_key AS mail_crypt_global_private_key \ FROM USER \ WHERE USER.user = '%Lu' This worked fine, enabling encryption and decryption properly. For Dovecot 2.4 this does not work anymore. Example from LMTP: Dec 11 15:02:59 lmtp(975838): Info: lmtp-server: conn unix:pid=975905,uid=113 [1]: rcpt user(a)test.de: <Ti6aNxPPOmne4w4APAc66w>: Failed to send message to <user(a)test.de> at server:24: 451 4.2.0 <user(a)test.de> get_public_key(INBOX) failed: mailbox_attribute_get(INBOX, /shared/vendor/vendor.dovecot/pvt/crypt/active) failed: Mailbox attributes not enabled (1/1 at 12 ms) I tried to adapt it to Dovecot 2.4 per the documentation, ending up with this: query = \ SELECT \ USER.user, USER.host, \ SECRET.password, \ concat('inline:', SECRET.public_key) AS crypt_global_public_key_file, \ 'main' AS crypt_global_private_key, \ concat('inline:', SECRET.private_key) AS 'crypt_global_private_key/main/crypt_private_key_file' \ FROM USER \ WHERE USER.user = '%{user | lower}' Still the error message: get_public_key(INBOX) failed: mailbox_attribute_get(INBOX, /shared/vendor/vendor.dovecot/pvt/crypt/active) failed: Mailbox attributes not enabled Additionally I tried without the "inline:" prefix, because without, doveadm mailbox cryptokey list would return a "no such file or directory error" trying to treat the key as a filename. With the "inline:" prefix it returns nothing except a warning: Warning: mailbox cryptokey list: Nothing was matched. Use -U or specify mask? What is the right way to proceed here?

2 2

Created DokuWiki entries for the migration from Dovecot 2.3 to 2.4.
by Klaus Tachtler 10 Jan '26

10 Jan '26

Hello everyone, Over the past few weeks, I have migrated from Dovecot 2.3 to 2.4 and documented this in my DokuWiki. I do not claim that this is complete, nor is it an all-encompassing description. It includes a configuration for Dovecot 2.3 and the respective migration to Dovecot 2.4. I implemented the following configurations: Dovecot ArchLinux Dovecot ArchLinux - SSL/TLS Dovecot ArchLinux - SASL Dovecot ArchLinux - Quotas Dovecot ArchLinux - Mail-Log-Schreibung Dovecot ArchLinux - Zlib-Komprimierung Dovecot ArchLinux - SQL Dovecot ArchLinux - SQL - Quota: SQL Dovecot ArchLinux - Sieve (Pigeonhole) Dovecot ArchLinux - Shares Dovecot ArchLinux - Master-User The DokuWiki entries are in German, but I think the code examples speak for themselves, and if necessary, a translation program can also be used. The Dokuwiki and my implementations can be accessed at the following link: https://dokuwiki.tachtler.net/doku.php?id=index#imap-server_dovecot_imap-se… The documentation was created using the Archlinux operating system, but can certainly be ported to other Linux distributions. I hope someone else might find my notes useful too? Best regards, Klaus Tachtler. -- --------------------------------------- e-Mail : klaus(a)tachtler.net Homepage: https://www.tachtler.net DokuWiki: https://dokuwiki.tachtler.net ---------------------------------------

3 3

Problems building from source under Trixie
by William Silverstein 09 Jan '26

09 Jan '26

I am running Debian Trixie. I try building the, but the configuration fails: I tried building with: ./configure \ --prefix=/usr/local/dovecot \ --with-sql \ --with-mysql \ --without-pam \ --without-pgsql \ --without-sqlite \ --with-solr \ --with-bzlib \ --with-lz4 \ --with-ldap I get configure: error: cannot build with MySQL support: Neither MySQL (mysqlclient) nor MariaDB library (libmariadb) found. But I did install libldb-dev. I also installed libldap2-dev liblz4-dev But when I do: EXPAT_CFLAGS=/usr/include EXPAT_LIBS=/lib/x86_64-linux-gnu \ LZ4_CFLAGS=/usr/include LZ4_LIBS=/usr/lib/x86_64-linux-gnu \ ZLIB_CFLAGS=/usr/include ZLIB_LIBS=/lib/x86_64-linux-gnu \ MARIADB_LIBS=/usr/lib/x86_64-linux-gnu MARIADB_CFLAGS=/usr/include/mariadb \ ./configure \ --prefix=/usr/local/dovecot \ --with-sql \ --with-mysql \ --without-pam \ --without-pgsql \ --without-sqlite \ --with-solr \ --with-bzlib \ --with-lz4 It configures, them fails in the build. I got some LZ4_DEPRECATED("use LZ4_compress_default() instead") LZ4LIB_API int LZ4_compress (const char* src, char* dest, int srcSize); I get a bunch of linker errors: /usr/bin/ld: ./.libs/libcompression.a(istream-lz4.o): in function `i_stream_lz4_read': /usr/local/src/dovecot-2.4.2/src/lib-compression/istream-lz4.c:192:(.text+0x619): undefined reference to `LZ4_decompress_safe' /usr/bin/ld: ./.libs/libcompression.a(istream-zlib.o): in function `i_stream_zlib_init': /usr/local/src/dovecot-2.4.2/src/lib-compression/istream-zlib.c:324:(.text+0x1d): undefined reference to `inflateInit2_' /usr/bin/ld: ./.libs/libcompression.a(istream-zlib.o): in function `i_stream_zlib_close': /usr/local/src/dovecot-2.4.2/src/lib-compression/istream-zlib.c:46:(.text+0xa8): undefined reference to `inflateEnd' /usr/bin/ld: ./.libs/libcompression.a(istream-zlib.o): in function `i_stream_zlib_reset': /usr/local/src/dovecot-2.4.2/src/lib-compression/istream-zlib.c:358:(.text+0x168): undefined reference to `inflateEnd' /usr/bin/ld: /usr/local/src/dovecot-2.4.2/src/lib-compression/istream-zlib.c:358:(.text+0x3a7): undefined reference to `inflateEnd' /usr/bin/ld: ./.libs/libcompression.a(istream-zlib.o): in function `i_stream_zlib_read': /usr/local/src/dovecot-2.4.2/src/lib-compression/istream-zlib.c:264:(.text+0x97f): undefined reference to `inflate' /usr/bin/ld: /usr/local/src/dovecot-2.4.2/src/lib-compression/istream-zlib.c:220:(.text+0xa7f): undefined reference to `inflateEnd' /usr/bin/ld: ./.libs/libcompression.a(ostream-lz4.o): in function `o_stream_lz4_compress': /usr/local/src/dovecot-2.4.2/src/lib-compression/ostream-lz4.c:94:(.text+0x12f): undefined reference to `LZ4_compress' /usr/bin/ld: ./.libs/libcompression.a(ostream-zlib.o): in function `o_stream_zlib_close': /usr/local/src/dovecot-2.4.2/src/lib-compression/ostream-zlib.c:91:(.text+0x1ee): undefined reference to `deflateEnd' /usr/bin/ld: ./.libs/libcompression.a(ostream-zlib.o): in function `o_stream_create_zlib': /usr/local/src/dovecot-2.4.2/src/lib-compression/ostream-zlib.c:412:(.text+0x339): undefined reference to `deflateInit2_' /usr/bin/ld: ./.libs/libcompression.a(ostream-zlib.o): in function `o_stream_zlib_send_flush': /usr/local/src/dovecot-2.4.2/src/lib-compression/ostream-zlib.c:281:(.text+0x577): undefined reference to `deflate' /usr/bin/ld: ./.libs/libcompression.a(ostream-zlib.o): in function `o_stream_zlib_send_chunk': /usr/local/src/dovecot-2.4.2/src/lib-compression/ostream-zlib.c:213:(.text+0x83b): undefined reference to `deflate' Any suggestions? Thanks. -- William G. Silverstein, Esq. 8383 Wilshire Blvd. Suite 630. Beverly Hills, CA 90211

2 1

Error: userdb: client doesn't have lookup permissions for this user
by vwoloszczuk＠tutanota.com 09 Jan '26

09 Jan '26

Hi, I am trying to configure Dovecot 2.4.2 to work as MDA for Postfix 3.10.5, using LMTP and SASL, with virtual users. This is Debian 13. I had Postfix working fine before trying to incorporate Dovecot, and I was also able to get LMTP working with system users (no SASL), but now things are not working. I've followed the guides in the documentation for using Dovecot and Postfix, in particular the following page: https://doc.dovecot.org/2.4.2/howto/sasl/postfix.html I've set up my 'service auth {}' to look like in that page. When I send mail to <user>, I get the following logs and the message is deferred by Postfix: lmtp(119643): Connect from local auth(<user>): Error: userdb: client doesn't have lookup permissions for this user: userdb reply doesn't contain uid (to bypass this check, set: service auth { unix_listener /run/dovecot/auth-userdb { mode=0777 } }) lmtp(<user> <mailto:viktor@woloszcz.uk>)<119643><SRJICIBlYGlb0wEAk6KCeQ>: Error: auth-master: userdb lookup(<user>): Auth USER lookup failed lmtp(119643): Error: lmtp-server: conn unix:pid=119900,uid=101 [3]: rcpt <user>: Failed to lookup user <user>: Internal error occurred. Refer to server log for more information. lmtp(119643): Disconnect from local: Logged out (state=READY) I am using passwd-file passdb '/etc/dovecot/passwd' with entries in the form '<user>:{PLAIN}password'. This file is owned by root and is world-readable.I am not using a userdb but have set 'mail_uid = vmail' and 'mail_gid = vmail' The socket is located at '/var/spool/postfix/dovecot/auth' (i.e. visible to Postfix) and is owned by the postfix user.I've tried changing the permissions of the socket as the error message instructed but this didn't have any effect. I haven't set 'user = doveauth' as in this page:https://doc.dovecot.org/2.4.2/howto/virtual/postfix.html I don't understand what that would do. Please find attached my full dovecot.conf in case it is useful. Thanks in advance, Viktor Hi, I am trying to configure Dovecot 2.4.2 to work as MDA for Postfix 3.10.5, using LMTP and SASL, with virtual users. This is Debian 13. I had Postfix working fine before trying to incorporate Dovecot, and I was also able to get LMTP working with system users (no SASL), but now things are not working. I've followed the guides in the documentation for using Dovecot and Postfix, in particular the following page: [1]https://doc.dovecot.org/2.4.2/howto/sasl/postfix.html I've set up my 'service auth {}' to look like in that page. When I send mail to <user>, I get the following logs and the message is deferred by Postfix: lmtp(119643): Connect from local auth(<user>): Error: userdb: client doesn't have lookup permissions for this user: userdb reply doesn't contain uid (to bypass this check, set: service auth { unix_listener /run/dovecot/auth-userdb { mode=0777 } }) lmtp([2]<user>)<119643><SRJICIBlYGlb0wEAk6KCeQ>: Error: auth-master: userdb lookup(<user>): Auth USER lookup failed lmtp(119643): Error: lmtp-server: conn unix:pid=119900,uid=101 [3]: rcpt <user>: Failed to lookup user <user>: Internal error occurred. Refer to server log for more information. lmtp(119643): Disconnect from local: Logged out (state=READY) I am using passwd-file passdb '/etc/dovecot/passwd' with entries in the form '<user>:{PLAIN}password'. This file is owned by root and is world-readable. I am not using a userdb but have set 'mail_uid = vmail' and 'mail_gid = vmail' The socket is located at '/var/spool/postfix/dovecot/auth' (i.e. visible to Postfix) and is owned by the postfix user. I've tried changing the permissions of the socket as the error message instructed but this didn't have any effect. I haven't set 'user = doveauth' as in this page: [3]https://doc.dovecot.org/2.4.2/howto/virtual/postfix.html I don't understand what that would do. Please find attached my full dovecot.conf in case it is useful. Thanks in advance, Viktor References Visible links 1. https://doc.dovecot.org/2.4.2/howto/sasl/postfix.html 2. mailto:viktor@woloszcz.uk 3. https://doc.dovecot.org/2.4.2/howto/virtual/postfix.html

2 3

how to use dovecot-lda with dovecot.crt?
by Matthias Bodenbinder 09 Jan '26

09 Jan '26

Hi, I have a self signed certificate for dovecot: > [root@rakete] /etc/dovecot > # ll > insgesamt 12K > -rwxr-xr-x 1 root root 1,7K 2026-01-09@09:56 dovecot.conf > -rw-r----- 1 root root 1,4K 2026-01-09@09:54 dovecot.crt > -rw-r----- 1 root root 1,7K 2026-01-09@09:54 dovecot.key in dovecot.conf I have: ssl_server { cert_file = /etc/dovecot/dovecot.crt key_file = /etc/dovecot/dovecot.key } This works fine for the evolution email client. But when I want to use dovecot-lda as part of my getmail6 config I get a permission denied: # getmail --rcfile dogado-rc -n -v getmail version 6.19.10 Copyright (C) 1998-2025 Charles Cazabon and others. Licensed under GPL-2.0. SimpleIMAPSSLRetriever:bodenbinder_de_9@imap.dogado.net:993: Delivery error (command dovecot-lda 1510042 error (89, doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 51: cert_file: open(/etc/dovecot/dovecot.crt) failed: Permission denied)) [INBOX] msg 1/1 (1392 bytes), delivery error (command dovecot-lda 1510042 error (89, doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 51: cert_file: open(/etc/dovecot/dovecot.crt) failed: Permission denied)) 1 messages (1392 bytes) retrieved, 0 skipped dogado-rc has this delivery section: [destination] type = MDA_external path = /usr/lib/dovecot/dovecot-lda arguments = ("-d", "matthias") When I change ownership of the certificate files it works: # chown root:matthias /etc/dovecot/dovecot.crt /etc/dovecot/dovecot.key [root@rakete] /etc/dovecot # ll /etc/dovecot/dovecot.crt /etc/dovecot/dovecot.key -rw-r----- 1 root matthias 1,4K 2026-01-09@09:54 /etc/dovecot/dovecot.crt -rw-r----- 1 root matthias 1,7K 2026-01-09@09:54 /etc/dovecot/dovecot.key If I do not change permissions for dovecot.key I get a similar error for that file too. But can this be the solution? That would mean that I need to give read access to the crt/key file to every user who wants to use dovecot-lda. Is that correct? Matthias

2 2

Republish of dovecot 2.4.2 packages
by Aki Tuomi 08 Jan '26

08 Jan '26

Hi! Due to mistake in RHEL 10 packaging, we have republished packages for 2.4.2. Content is still the same, build number has increased by one. The important change is that there is now pigeonhole package for RHEL 10. You can find the packages at https://repo.dovecot.org/ as usual. Kind regards, Aki Tuomi

1 0

File system errors
by Jyrki Partanen 07 Jan '26

07 Jan '26

I am trying to move from one VPS to another and strange (for me) file system errors arose. On the new VPS the IMAP client can see the Inbox, but not any other mailboxes. I get these errors in the log: Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145495><65K/GptHn8tVnMi0>: Error: open(/home/jyrki/mail/.imap/dovecot.list.index.log) failed: Permission denied (euid=1000(jyrki) egid=1000(jyrki) missing +r perm: /home/jyrki/mail/.imap/dovecot.list.index.log stat(/home/jyrki/mail/.imap/dovecot.list.index.log) failed: Permission denied) Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145495><65K/GptHn8tVnMi0>: Error: Mailbox INBOX: open(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied (euid=1000(jyrki) egid=1000(jyrki) missing +r perm: /home/jyrki/mail/.imap/INBOX/dovecot.index.log stat(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied) Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145495><65K/GptHn8tVnMi0>: Error: Couldn't create mailbox list lock /home/jyrki/mail/.imap/mailboxes.lock: file_create_locked(/home/jyrki/mail/.imap/mailboxes.lock) failed: safe_mkstemp(/home/jyrki/mail/.imap/mailboxes.lock) failed: Permission denied Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145499><nxbBGptHoMtVnMi0>: Error: Mailbox INBOX: open(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied (euid=1000(jyrki) egid=1000(jyrki) missing +r perm: /home/jyrki/mail/.imap/INBOX/dovecot.index.log stat(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied) ...etc... The thing is that the permissions should be OK, the files are not "missing +r perm". Any idea how to fix this? Thanks! I am trying to move from one VPS to another and strange (for me) file system errors arose. On the new VPS the IMAP client can see the Inbox, but not any other mailboxes. I get these errors in the log: Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145495><65K/GptHn8tVnMi0>: Error: open(/home/jyrki/mail/.imap/dovecot.list.index.log) failed: Permission denied (euid=1000(jyrki) egid=1000(jyrki) missing +r perm: /home/jyrki/mail/.imap/dovecot.list.index.log stat(/home/jyrki/mail/.imap/dovecot.list.index.log) failed: Permission denied) Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145495><65K/GptHn8tVnMi0>: Error: Mailbox INBOX: open(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied (euid=1000(jyrki) egid=1000(jyrki) missing +r perm: /home/jyrki/mail/.imap/INBOX/dovecot.index.log stat(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied) Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145495><65K/GptHn8tVnMi0>: Error: Couldn't create mailbox list lock /home/jyrki/mail/.imap/mailboxes.lock: file_create_locked(/home/jyrki/mail/.imap/mailboxes.lock) failed: safe_mkstemp(/home/jyrki/mail/.imap/mailboxes.lock) failed: Permission denied Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145499><nxbBGptHoMtVnMi0>: Error: Mailbox INBOX: open(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied (euid=1000(jyrki) egid=1000(jyrki) missing +r perm: /home/jyrki/mail/.imap/INBOX/dovecot.index.log stat(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied) ...etc... The thing is that the permissions should be OK, the files are not "missing +r perm". Any idea how to fix this? Thanks!

4 4