- dovecot - dovecot.org

[Dovecot] reproducible dsync backup panic (dovecot 2.2.7)
by Peter Benko 20 Dec '13

20 Dec '13

Hi all, I'm receiving a reproducible dsync backup panic for some of my users. The error message is as follows: dsync-remote(user@<removed>): Panic: file dsync-brain-mailbox-tree-sync.c: line 111 (dsync_brain_mailbox_tree_sync_change): assertion failed: (brain->no_backup_overwrite) dsync-remote(user@<removed>): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x69b70) [0x7f922dad9b70] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f922dad9c4a] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f922da94725] -> /usr/bin/dsync(dsync_brain_mailbox_tree_sync_change+0x382) [0x42f912] -> /usr/bin/dsync(dsync_brain_recv_mailbox_tree_deletes+0x10b) [0x42f4db] -> /usr/bin/dsync(dsync_brain_run+0x305) [0x42c6f5] -> /usr/bin/dsync() [0x42cbe8] -> /usr/bin/dsync() [0x43e040] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7f922daea066] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xd7) [0x7f922daeaf07] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f922dae9b78] -> /usr/bin/dsync() [0x4297f9] -> /usr/bin/dsync() [0x4133cd] -> /usr/bin/dsync(doveadm_mail_try_run+0x251) [0x414091] -> /usr/bin/dsync(main+0x3c8) [0x412f78] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f922d704ead] -> /usr/bin/dsync() [0x413191] dsync-local(user@<removed>): Error: read(<remote-mail-server>) failed: EOF dsync-local(user@<removed>): Error: Remote command returned error 134 The command I'm using to back up individual user's mail is something like: sudo -u vmail dsync -v -u user(a)server.com -R backup ssh -i sshid-file login(a)server.com sudo -u vmail dsync -v -u user(a)server.com I use the above command at the backup server. The error started to appear a few weeks after we started using the new mail system. First it appeared for a single user, now it appears for some more users as well. It is deterministic and reproducible. Any ideas? I included the relevant part of my config below. Best regards, Peter ------------------------------------------------------------------- # 2.2.7 (5c876ed0c3e0): /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.2 auth_master_user_separator = * auth_mechanisms = plain login hostname = <removed> listen = * login_greeting = $hostname IMAP server mail_attachment_dir = /mail/mailboxes/%d/_attachments_ mail_attachment_fs = sis-queue $mail_attachment_dir/queue:posix mail_attachment_min_size = 16 k mail_location = mdbox:~ mail_plugins = " zlib acl" mdbox_rotate_interval = 5 days mdbox_rotate_size = 5 M namespace { inbox = yes location = prefix = separator = / type = private } namespace { list = children location = mdbox:/mail/mailboxes/%%d/%%n:INDEX=/mail/mailboxes/%%d/%%n prefix = Accounts/%%n/ separator = / subscriptions = no type = shared } passdb { args = /mail/config/dovecot/passwd driver = passwd-file } passdb { args = /mail/config/dovecot/passwd-master driver = passwd-file master = yes pass = yes } plugin { acl = vfile acl_defaults_from_inbox = yes acl_shared_dict = file:/mail/mailboxes/%d/shared-mailboxes.db zlib_save = gz zlib_save_level = 6 } postmaster_address = postmaster@<removed> protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } syslog_facility = local6 userdb { args = uid=vmail gid=vmail master_user=%u home=/mail/mailboxes/%d/%n driver = static } protocol imap { mail_plugins = " zlib acl imap_acl" }

2 1

[Dovecot] auth failures
by Andreas Schulze 19 Dec '13

19 Dec '13

Hello, last week and today our dovecot pop3 server stopped responding. Without any other logentries dovecot start to log only this: Dec 12 09:14:12 mbox1 dovecot: auth: Error: ldap(testuser,192.0.2.110,<FBZH7lHtAQAK/FCj>): ldap_search(base=ou=accounts,dc=example,dc=de filter=(&(|(uid=testuser)(mail=testuser))(!(state=blocked)))) failed: Operations error For every pop3 Session, ~2000 per Minute ..., over 10 Minutes I send dovecot a SIGTERM. After dovecot was started again, all was fine again. # doveconf -n http://postmaster.datev.de/tmp/dovecot.conf The LDAP-Server itself did resond to queries in the same timeframe. I know this because the MTA on the same host was able to deliver messages into mailboxes. Any hints? Thanks Andreas -- Andreas Schulze Internetdienste | P252 DATEV eG 90329 Nürnberg | Telefon +49 911 319-0 | Telefax +49 911 319-3196 E-Mail info @datev.de | Internet www.datev.de Sitz: 90429 Nürnberg, Paumgartnerstr. 6-14 | Registergericht Nürnberg, GenReg Nr.70 Vorstand Prof. Dieter Kempf (Vorsitzender) Dipl.-Kfm. Wolfgang Stegmann (stellvertretender Vorsitzender) Dipl.-Kfm. Michael Leistenschneider Dipl.-Kfm. Dr. Robert Mayr Jörg Rabe v. Pappenheim Dipl.-Vw. Eckhard Schwarzer Vorsitzender des Aufsichtsrates: Reinhard Verholen

2 1

[Dovecot] External auth
by eechim enorniel 19 Dec '13

19 Dec '13

Hello, I saw a lot of tutorials about setting postfix with dovecot sasl but I would like more. I want to set a SSO system with roundcube on dovecot. I would like to know how to make dovecot work with sasl or saml, not as a provider but as a service plugging on an external provider. I saw there is an EXTERNAL auth mechanism but I didn't find any doc about it. Can you help me ? Thanks.

2 1

[Dovecot] Mailbox with .broken files
by Michael Smith (DF) 19 Dec '13

19 Dec '13

We're using Dovecot 2.2.4 and mdbox storage with compression. I noticed yesterday that at least one of the accounts has unusual files in it's mail/storage directory. This account has approximately 17.5G of compressed mail, across about 750 storage files (m.###) using 8G of storage. Starting on Dec 11, storage files m.409 through m.731 have not only their m.### file, but also a m.###.broken file. At the same time .temp.<unix time>.<unique id>.<hostname> files also started showing up... ... -rw--w---- 1 user123 mail 3225 Dec 12 04:38 m.708 -rw--w---- 1 user123 mail 167106 Dec 12 03:35 m.708.broken -rw--w---- 1 user123 mail 46155 Dec 12 04:38 m.709 -rw--w---- 1 user123 mail 177267 Dec 12 03:40 m.709.broken -rw--w---- 1 user123 mail 20965889 Nov 26 19:22 m.71 -rw--w---- 1 user123 mail 133248 Dec 12 04:38 m.710 -rw--w---- 1 user123 mail 264361 Dec 12 03:40 m.710.broken -rw--w---- 1 user123 mail 103407 Dec 12 04:38 m.711 -rw--w---- 1 user123 mail 627736 Dec 12 03:40 m.711.broken -rw--w---- 1 user123 mail 5132 Dec 12 04:38 m.712 -rw--w---- 1 user123 mail 136244 Dec 12 03:40 m.712.broken -rw--w---- 1 user123 mail 187224 Dec 12 04:38 m.713 -rw--w---- 1 user123 mail 351104 Dec 12 03:45 m.713.broken -rw--w---- 1 user123 mail 435793 Dec 12 04:38 m.714 -rw--w---- 1 user123 mail 566906 Dec 12 03:45 m.714.broken -rw--w---- 1 user123 mail 60916 Dec 12 04:38 m.715 -rw--w---- 1 user123 mail 192028 Dec 12 03:50 m.715.broken -rw--w---- 1 user123 mail 38051 Dec 12 04:38 m.716 -rw--w---- 1 user123 mail 169163 Dec 12 03:50 m.716.broken -rw--w---- 1 user123 mail 226067 Dec 12 04:38 m.717 -rw--w---- 1 user123 mail 389948 Dec 12 04:00 m.717.broken ... -rw--w---- 1 user123 mail 20967506 Dec 2 17:32 m.96 -rw--w---- 1 user123 mail 20967131 Dec 2 18:40 m.97 -rw--w---- 1 user123 mail 20969078 Dec 2 18:38 m.98 -rw--w---- 1 user123 mail 20963978 Dec 2 19:23 m.99 -rw--w---- 1 user123 mail 294968 Dec 11 20:05 .temp.1386813944.P9142Q0M123686.myhost -rw--w---- 1 user123 mail 294968 Dec 11 20:05 .temp.1386813967.P9213Q0M387733.myhost -rw--w---- 1 user123 mail 294968 Dec 11 20:05 .temp.1386813970.P9231Q0M371190.myhost -rw--w---- 1 user123 mail 327736 Dec 11 20:05 .temp.1386813972.P9173Q0M932070.myhost -rw--w---- 1 user123 mail 327736 Dec 11 20:05 .temp.1386813972.P9239Q0M114754.myhost -rw--w---- 1 user123 mail 327736 Dec 11 20:05 .temp.1386813983.P9261Q0M640646.myhost -rw--w---- 1 user123 mail 1048632 Dec 11 20:06 .temp.1386814038.P9515Q0M530600.myhost I'm not really seeing anything that stands out in the maillog during this time. What caused this problem? How concerned should I be about possible lost email? This is a production environment. Below is the dovecot -n output. -- Michael Smith # dovecot -n # 2.2.4: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-279.19.1.el6.x86_64 x86_64 CentOS release 6.3 (Final) auth_debug = yes auth_debug_passwords = yes auth_default_realm = mydomain.com auth_master_user_separator = * auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no dotlock_use_excl = no lda_mailbox_autocreate = yes lock_method = dotlock mail_access_groups = mail mail_debug = yes mail_fsync = always mail_location = mdbox:~/mail:INDEX=~/index mail_plugins = quota zlib mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date mbox_read_locks = dotlock mbox_write_locks = dotlock mdbox_rotate_interval = 1 weeks mdbox_rotate_size = 20 M mmap_disable = yes namespace { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = type = private } passdb { args = /etc/dovecot/dovecot-sql-master.conf.ext driver = sql master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { autosubscribe = Trash autosubscribe2 = Junk autosubscribe3 = Drafts autosubscribe4 = Sent autosubscribe5 = INBOX mail_max_userip_connections = 10 managesieve_max_line_length = 65536 quota = dict:User quota::file:%h/dovecot.quota quota2_rule = Trash:storage=+10%% quota3_rule = Junk:storage=+20%% quota_rule = *:storage=100M:messages=100000 recipient_delimiter = + sieve_before = /var/opt/mail/global.sieve/ zlib_save = gz zlib_save_level = 9 } pop3_reuse_xuidl = yes protocols = imap pop3 sieve lmtp service auth { inet_listener auth { port = 113 } unix_listener auth-userdb { user = nobody } } service lmtp { inet_listener lmtp { port = 24 } process_min_avail = 10 service_count = 1 } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } ssl = no ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lda { mail_plugins = quota zlib sieve } protocol imap { mail_plugins = quota zlib imap_quota } protocol sieve { mail_max_userip_connections = 10 mail_plugins = quota zlib managesieve_max_line_length = 65536 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date } protocol lmtp { mail_plugins = quota zlib sieve }

2 1

Re: [Dovecot] Mailbox with .broken files
by Michael Smith (DF) 19 Dec '13

19 Dec '13

Anyone have any feedback, guidance or suggestions on this? Timo? -----Original Message----- From: Michael Smith (DF) [mailto:msmith@datafoundry.com] Sent: Friday, December 13, 2013 9:49 AM To: 'dovecot(a)dovecot.org' Subject: [Dovecot] Mailbox with .broken files We're using Dovecot 2.2.4 and mdbox storage with compression. I noticed yesterday that at least one of the accounts has unusual files in it's mail/storage directory. This account has approximately 17.5G of compressed mail, across about 750 storage files (m.###) using 8G of storage. Starting on Dec 11, storage files m.409 through m.731 have not only their m.### file, but also a m.###.broken file. At the same time .temp.<unix time>.<unique id>.<hostname> files also started showing up... ... -rw--w---- 1 user123 mail 3225 Dec 12 04:38 m.708 -rw--w---- 1 user123 mail 167106 Dec 12 03:35 m.708.broken -rw--w---- 1 user123 mail 46155 Dec 12 04:38 m.709 -rw--w---- 1 user123 mail 177267 Dec 12 03:40 m.709.broken -rw--w---- 1 user123 mail 20965889 Nov 26 19:22 m.71 -rw--w---- 1 user123 mail 133248 Dec 12 04:38 m.710 -rw--w---- 1 user123 mail 264361 Dec 12 03:40 m.710.broken -rw--w---- 1 user123 mail 103407 Dec 12 04:38 m.711 -rw--w---- 1 user123 mail 627736 Dec 12 03:40 m.711.broken -rw--w---- 1 user123 mail 5132 Dec 12 04:38 m.712 -rw--w---- 1 user123 mail 136244 Dec 12 03:40 m.712.broken -rw--w---- 1 user123 mail 187224 Dec 12 04:38 m.713 -rw--w---- 1 user123 mail 351104 Dec 12 03:45 m.713.broken -rw--w---- 1 user123 mail 435793 Dec 12 04:38 m.714 -rw--w---- 1 user123 mail 566906 Dec 12 03:45 m.714.broken -rw--w---- 1 user123 mail 60916 Dec 12 04:38 m.715 -rw--w---- 1 user123 mail 192028 Dec 12 03:50 m.715.broken -rw--w---- 1 user123 mail 38051 Dec 12 04:38 m.716 -rw--w---- 1 user123 mail 169163 Dec 12 03:50 m.716.broken -rw--w---- 1 user123 mail 226067 Dec 12 04:38 m.717 -rw--w---- 1 user123 mail 389948 Dec 12 04:00 m.717.broken ... -rw--w---- 1 user123 mail 20967506 Dec 2 17:32 m.96 -rw--w---- 1 user123 mail 20967131 Dec 2 18:40 m.97 -rw--w---- 1 user123 mail 20969078 Dec 2 18:38 m.98 -rw--w---- 1 user123 mail 20963978 Dec 2 19:23 m.99 -rw--w---- 1 user123 mail 294968 Dec 11 20:05 .temp.1386813944.P9142Q0M123686.myhost -rw--w---- 1 user123 mail 294968 Dec 11 20:05 .temp.1386813967.P9213Q0M387733.myhost -rw--w---- 1 user123 mail 294968 Dec 11 20:05 .temp.1386813970.P9231Q0M371190.myhost -rw--w---- 1 user123 mail 327736 Dec 11 20:05 .temp.1386813972.P9173Q0M932070.myhost -rw--w---- 1 user123 mail 327736 Dec 11 20:05 .temp.1386813972.P9239Q0M114754.myhost -rw--w---- 1 user123 mail 327736 Dec 11 20:05 .temp.1386813983.P9261Q0M640646.myhost -rw--w---- 1 user123 mail 1048632 Dec 11 20:06 .temp.1386814038.P9515Q0M530600.myhost I'm not really seeing anything that stands out in the maillog during this time. What caused this problem? How concerned should I be about possible lost email? This is a production environment. Below is the dovecot -n output. -- Michael Smith # dovecot -n # 2.2.4: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-279.19.1.el6.x86_64 x86_64 CentOS release 6.3 (Final) auth_debug = yes auth_debug_passwords = yes auth_default_realm = mydomain.com auth_master_user_separator = * auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no dotlock_use_excl = no lda_mailbox_autocreate = yes lock_method = dotlock mail_access_groups = mail mail_debug = yes mail_fsync = always mail_location = mdbox:~/mail:INDEX=~/index mail_plugins = quota zlib mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date mbox_read_locks = dotlock mbox_write_locks = dotlock mdbox_rotate_interval = 1 weeks mdbox_rotate_size = 20 M mmap_disable = yes namespace { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = type = private } passdb { args = /etc/dovecot/dovecot-sql-master.conf.ext driver = sql master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { autosubscribe = Trash autosubscribe2 = Junk autosubscribe3 = Drafts autosubscribe4 = Sent autosubscribe5 = INBOX mail_max_userip_connections = 10 managesieve_max_line_length = 65536 quota = dict:User quota::file:%h/dovecot.quota quota2_rule = Trash:storage=+10%% quota3_rule = Junk:storage=+20%% quota_rule = *:storage=100M:messages=100000 recipient_delimiter = + sieve_before = /var/opt/mail/global.sieve/ zlib_save = gz zlib_save_level = 9 } pop3_reuse_xuidl = yes protocols = imap pop3 sieve lmtp service auth { inet_listener auth { port = 113 } unix_listener auth-userdb { user = nobody } } service lmtp { inet_listener lmtp { port = 24 } process_min_avail = 10 service_count = 1 } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } ssl = no ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lda { mail_plugins = quota zlib sieve } protocol imap { mail_plugins = quota zlib imap_quota } protocol sieve { mail_max_userip_connections = 10 mail_plugins = quota zlib managesieve_max_line_length = 65536 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date } protocol lmtp { mail_plugins = quota zlib sieve }

1 0

[Dovecot] v2.2.9 released
by Timo Sirainen 19 Dec '13

19 Dec '13

http://dovecot.org/releases/2.2/dovecot-2.2.9.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.9.tar.gz.sig + Full text search indexing can now be done automatically after saving/copying mails by setting plugin { fts_autoindex=yes } + replicator: Added replication_dsync_parameters setting to pass "doveadm sync" parameters (for controlling what to replicate). + Added mail-filter plugin + Added liblzma/xz support (zlib_save=xz) - v2.2.8's improved cache file handling exposed several old bugs related to fetching mail headers. - v2.2.7's iostream handling changes were causing some connections to be disconnected before flushing their output (e.g. POP3 logout message wasn't being sent)

7 9

[Dovecot] zlib plugin question
by Przemysław Orzechowski 19 Dec '13

19 Dec '13

Hi Is it possible to compress incoming mails delivered via dovecots LDA when using dovecot --version 1.2.9 or do i have to compress them via cron?

2 2

[Dovecot] problem with password in a changing scenario
by Angel Luis Mateo Martinez 19 Dec '13

19 Dec '13

Hello, I'm having a problem with with password changing. According to http://wiki2.dovecot.org/Authentication/Caching, I understand "normal scenario" and "Using old cached password scenario", but I'm having a problem with the "Early change scenario". I understand that in this case, if in step 4 user tries password Y, then this password is not tried again and login fails. But if the user tries another password Z, then is it test it? Or does it directly fail? I think that it is directly failing. And here is my problem... I am using dovecot with a ldap backend and another pam backend. The first one is users connecting with an email client. The other one applies when the ldap backend fails and it is use for connections from our webmail, which is integrated in our CAS SSO environment (it has running an imap proxy too). Sometimes (the only scenari we were able to reproduce is with users that for some reason has two SSO sessions opened) dovecot receives an invalid CAS ticket, then authentication fails, and no newer tickets are tried until cache is clean. That's why I think that in this scenario another Z password is even tried. Any idea? -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868889150 Fax: 868888337

1 0

[Dovecot] letters local filter duplicated
by John Smith 18 Dec '13

18 Dec '13

two servers with replicated master/master. dovecot.conf = http://pastebin.com/jVnvyWZM with this setup letters processed local filter duplicated. ie when the mail client receives a letter begins processing using rules (filters) to move the letters in a different folder. summarized in this folder is two duplicate letters. if you disable the filter, the message is not duplicated. But does not move to another location. -- Best Regards, Evgeny Senior System Administrator OOO "Vaz Service Hurley"

3 4

[Dovecot] Size detection/replair does not work with zlib
by Roland Rosenfeld 18 Dec '13

18 Dec '13

Hi! Usually dovecot auto detects or repairs the size of a maildir message. So I can place a message named "foo" in the cur directory and dovecot uses it. Now I tried the same with a zlib compressed message but here dovecot doesn't recognize/repair the size of the message. When I access this folder via IMAP the connection is diconnected and in dovecot logs I see the following error messages: Error: Cached message size smaller than expected (805 < 2666) Error: Corrupted index cache file /somedir/dovecot.index.cache: Broken physical size for mail UID 23 Error: read() failed: Input/output error (FETCH for mailbox INBOX UID 23) Disconnected: Internal error occurred. Refer to server log for more information. [2013-12-12 10:54:18] in=321 out=1977 As you can see in the first line, dovecot does know the compressed size of the file (805) as well as the uncompressed size (2666), but it isn't able to repair its index for this. If I modify the setup a little with a standard file naming but with a wrong file size in S-flag (compressed size instead of uncompressed size), the log entries become stranger: Error: Cached message size smaller than expected (805 < 2666) Error: Maildir filename has wrong S value, renamed the file from /somedir/cur/1386772057.M152553P9709.host,S=805:2, to /somedir/cur/1386772057.M152553P9709.host,S=805:2, So here dovecot detects the wrong S value, but instead of fixing it by using the uncompressed size, it renames to the same file name as before... All the above was tested with dovecot 2.1.17. We did a short cross test with 2.2.9 which gives somewhat different error messages, but also isn't able to detect/repair the (uncompressed) file size: Error: Cached message size smaller than expected (805 < 2666) Error: Corrupted index cache file /somedir/dovecot.index.cache: Broken physical size for mail UID 23 Error: read(zlib(/somedir/cur/foo)) failed: Invalid argument We also noticed that on both dovecot versions after trying to access the above file, dovecot.index.cache is always deleted and not rebuild... Is all this intended behavior? It sounds different to the standard behavior of dovecot, that repairs broken folders if possible... Ciao Roland

4 3