- dovecot - dovecot.org

doveadm search when using solr problems
by Ricardo Branco 26 Apr '16

26 Apr '16

Is there a way when using doveadm to search a users mailbox to disable using solr plugin (without changing config file). We have found that solr does not work well with certain search types and reverting to non solr searching works much better.

2 3

Possible to use Doveadm for a time range deletion
by Kenneth Ulrich 26 Apr '16

26 Apr '16

Hello All, I was wondering if it s possible to remove emails between a time range. For example, End Users have emails dating back to Aug 2000. He would like all emails deleted between the time stamp of 07/2014 to 07/2015 yet keep any emails outside of this area. I've ran into some similar examples, but nothing definite.

2 1

Strange search behavior
by Cornelius Charlie 26 Apr '16

26 Apr '16

Hello, I experienced a strange behavior in the way dovecot is performing searches, I only experienced this exact issue with the flag "seen". If I perform this command: UID SORT (SIZE) UTF-8 FLAGGED SEEN Dovecot return every seen messages even if the message is not "flagged'. This is only happening when there is no unseen messages in the mailbox, if there is at least one, this is working properly. Any though ? Thanks.

3 4

push-notification plugin and imap-metadata permissions
by Giovanni S. Fois 26 Apr '16

26 Apr '16

Ultra short version: Why cant I set the following mailbox metadata key? /private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify Let me explain the context: I'm using the Dovecot version 2.23.1, but the same happens for the 2.2.22 The push-notification plugin is supposed to send out a notification whenever a mailbox get a new email message. In order to tell if a mailbox is enabled to send out the notification, the plugin looks out for the following mailbox metadata key: /private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify If the key is set then everything is OK and the notification is sent, otherwise the action is skipped. If I try to setup the metadata key by hand (telnet as the user over the imap port): setmetadata INBOX (/private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify "user=myuser(a)mydomain.com") I get the error message: "Internal mailbox attributes cannot be accessed" Digging in the Dovecot 2.2.22 sources i found that: This string is from lib-imap-storage/imap-metadata.c - line 36 - Dovecot 2.2.22 The message is triggered by the following condition - same file - line 125 - Dovecot 2.2.22 if (strncmp(*key_r, MAILBOX_ATTRIBUTE_PREFIX_DOVECOT_PVT, strlen(MAILBOX_ATTRIBUTE_PREFIX_DOVECOT_PVT)) == 0) { So the path pvt/server appears to be forbidden. But, in the file lib-storage/mailbox-attribute.h we can read the following comment: /* User can get/set all non-pvt/ attributes and also pvt/server/ (but not pvt/server/pvt/) attributes. */ And, after said comment there is the definition of the macro MAILBOX_ATTRIBUTE_KEY_IS_USER_ACCESSIBLE(key) which has the same basic function of the condition in imap-metadata.c , but in this case the same imap key is seen as accessible. Now my questions: Can we use a negated version of MAILBOX_ATTRIBUTE_KEY_IS_USER_ACCESSIBLE(key) in imap-metadata? How can the push-notification plugin work out-of-the-box without changes and recompilation? Thank you for your valuable time and forgive me if I'm posing a dumb question. Best wishes, Giovanni S. Fois

4 6

Kernel panic in dovecot-ee-lmtp on Debian 8
by Tobi 26 Apr '16

26 Apr '16

Hi list I just realized that that I don not receive all mails in my mailbox (running dovecot-ee 2.2.23.1-1 on Debian 8). On my frontend servers (running postfix) the queue fills up with mails that cannot be delivered via lmtp to my backend servers. The error message on the frontend is "lost connection with backend while sending data" When I checked the logs on the backend server I found upon every delivery attempt kernel panics Apr 25 12:33:36 mbox1 dovecot: lmtp(REDACTED): Panic: epoll_ctl(del, 18) failed: Bad file descriptor Apr 25 12:33:36 mbox1 dovecot: lmtp(REDACTED): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x85dee) [0x7faa19225dee] -> /usr/lib/dovecot/libdovecot.so.0(+0x85edc) [0x7faa19225edc] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7faa191ca5be] -> /usr/lib/dovecot/libdovecot.so.0(+0x9afc1) [0x7faa1923afc1] -> /usr/lib/dovecot/libdovecot.so.0(+0x994af) [0x7faa192394af] -> /usr/lib/dovecot/libdovecot.so.0(+0xa5eda) [0x7faa19245eda] -> /usr/lib/dovecot/libdovecot.so.0(+0xa4566) [0x7faa19244566] -> /usr/lib/dovecot/libdovecot.so.0(o_stream_destroy+0xe) [0x7faa192446ee] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x7e44b) [0x7faa17d3a44b] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x7ea14) [0x7faa17d3aa14] -> /usr/lib/dovecot/libdovecot.so.0(+0xa6d88) [0x7faa19246d88] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7faa19239c6c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x101) [0x7faa1923b0d1] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7faa19239cf5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7faa19239e98] -> /usr/lib/dovecot/libdovecot-sieve.so.0(program_client_run+0xe8) [0x7faa17d3b308] -> /usr/lib/dovecot/modules/sieve/lib90_sieve_extprograms_plugin.so(+0x45b8) [0x7faa15d855b8] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_interpreter_continue+0x7c) [0x7faa17cfa2ac] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_interpreter_run+0x2b) [0x7faa17cfa4cb] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x519e0) [0x7faa17d0d9e0] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_execute+0x47) [0x7faa17d0e567] -> /usr/lib/dovecot/modules/lib90_sieve_plugin.so(+0x3b6b) [0x7faa17f73b6b] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x49) [0x7faa197e5849] -> dovecot/lmtp() [0x4064b3] -> dovecot/lmtp() [0x406cb4] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7faa19239c6c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x101) [0x7faa1923b0d1] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7faa19239cf5] Apr 25 12:33:36 mbox1 dovecot: lmtp(REDACTED): Fatal: master: service(lmtp): child 32081 killed with signal 6 (core dumps disabled) the weird thing is that this is not concerning all incoming mails. From time to time the frontends can deliver messages to my backends. I just tested it with a mail from work. It arrived via a frontend that has other mails in queue that could not be delivered so far. Does anyone have an idea where I could look for the root cause of this panic messages? Thanks a lot tobi

4 5

doveadm-server segfaults when searching or expunging with the -A flag
by Burak Seydioglu 26 Apr '16

26 Apr '16

Hello, I have an openldap backend that contains a large number of users and serves passdb and userdb requests. I was trying to work around the pop3 deletion issue that I had reported earlier (http://www.dovecot.org/list/dovecot/2016-April/103973.html) with the pop3_deleted_flag setting so I updated my configuration and created some background jobs to expunge deleted emails. However, doveadm-server segfaults when running search or expunge commands with the -A flag: doveadm search mailbox INBOX KEYWORD '$Pop3Deleted' -A doveadm expunge mailbox INBOX KEYWORD '$Pop3Deleted' -A ###################################### gdb /usr/libexec/dovecot/doveadm-server /var/crash/core-doveadm-server-11-0-0-2589-1461628665 #0 o_stream_cork (stream=0x0) at ostream.c:141 #1 0x0000000000430193 in server_connection_output (conn=0xfe10e0) at server-connection.c:126 #2 0x00007fcde9fc80c7 in plain_flush_callback (sstream=0xfdacf0) at ostream-openssl.c:180 #3 0x00007fcdeb6f9929 in stream_send_io (fstream=0xfe65e0) at ostream-file.c:482 #4 0x00007fcdeb6ebceb in io_loop_call_io (io=0xfdb110) at ioloop.c:564 #5 0x00007fcdeb6ed2e7 in io_loop_handler_run_internal (ioloop=<value optimized out>) at ioloop-epoll.c:220 #6 0x00007fcdeb6ebd95 in io_loop_handler_run (ioloop=0xfdf4b0) at ioloop.c:612 #7 0x00007fcdeb6ebf38 in io_loop_run (ioloop=0xfdf4b0) at ioloop.c:588 #8 0x000000000041f542 in dsync_connect_tcp (ctx=0xfc7d70, mail_set=<value optimized out>, target=<value optimized out>, ssl=true, error_r=0x7ffde6127020) at doveadm-dsync.c:806 #9 0x000000000041ff95 in parse_location (_ctx=0xfc7d70, service_user=<value optimized out>, error_r=0x7ffde6127020) at doveadm-dsync.c:837 #10 cmd_dsync_prerun (_ctx=0xfc7d70, service_user=<value optimized out>, error_r=0x7ffde6127020) at doveadm-dsync.c:903 #11 0x00000000004205f2 in doveadm_mail_next_user (ctx=0xfc7d70, cctx=<value optimized out>, error_r=0x7ffde6127020) at doveadm-mail.c:383 #12 0x000000000043151f in doveadm_mail_cmd_server_run (conn=0xfc3950) at client-connection.c:183 #13 doveadm_cmd_handle (conn=0xfc3950) at client-connection.c:266 #14 client_handle_command (conn=0xfc3950) at client-connection.c:330 #15 client_connection_input (conn=0xfc3950) at client-connection.c:444 #16 0x00007fcdeb6ebceb in io_loop_call_io (io=0xfc34f0) at ioloop.c:564 #17 0x00007fcdeb6ed2e7 in io_loop_handler_run_internal (ioloop=<value optimized out>) at ioloop-epoll.c:220 #18 0x00007fcdeb6ebd95 in io_loop_handler_run (ioloop=0xf90780) at ioloop.c:612 #19 0x00007fcdeb6ebf38 in io_loop_run (ioloop=0xf90780) at ioloop.c:588 #20 0x00007fcdeb684753 in master_service_run (service=0xf90620, callback=<value optimized out>) at master-service.c:640 #21 0x0000000000433897 in main (argc=1, argv=0xf903a0) at main.c:126 ###################################### Dovecot version ###################################### dovecot --version 2.2.23 (806d709) ###################################### doveconf -n ###################################### # 2.2.23 (806d709): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-573.22.1.el6.x86_64 x86_64 CentOS release 6.7 (Final) auth_debug = yes auth_mechanisms = plain login auth_verbose = yes base_dir = /var/run/dovecot/ disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it first_valid_uid = 89 last_valid_uid = 89 login_greeting = Dovecot ready on mda01.dc1.domain.com. login_trusted_networks = 127.0.0.1 mail_debug = yes mail_gid = 89 mail_plugins = " notify replication" mail_uid = 89 mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/conf.d/dovecot-ldap-passdb.conf.ext driver = ldap } plugin { mail_replica = tcps:mdareplica:12345 } pop3_deleted_flag = $POP3Deleted protocols = pop3 lmtp replication_full_sync_interval = 3 hours replication_max_conns = 20 service aggregator { fifo_listener replication-notify-fifo { group = postfix mode = 0640 user = postfix } unix_listener replication-notify { group = postfix mode = 0640 user = postfix } } service auth { unix_listener auth { mode = 0660 } } service doveadm { inet_listener { port = 12345 ssl = yes } } service lmtp { process_min_avail = 10 unix_listener lmtp { group = postfix mode = 0640 user = postfix } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { group = postfix mode = 0640 user = postfix } } ssl_cert = </etc/pki/tls/certs/dovecot.crt ssl_client_ca_file = /etc/pki/tls/CA/dovecot.bundle ssl_key = </etc/pki/tls/private/dovecot.key ssl_prefer_server_ciphers = yes userdb { driver = prefetch } userdb { args = /etc/dovecot/conf.d/dovecot-ldap-userdb.conf.ext driver = ldap } protocol lmtp { mail_plugins = " notify replication" } ###################################### LDAP configuration ###################################### cat /etc/dovecot/conf.d/dovecot-ldap-userdb.conf.ext hosts = localhost dn = cn=dovecot,dc=csi,dc=domain,dc=com dnpass = xxx ldap_version = 3 base = ou=instances,dc=csi,dc=domain,dc=com deref = never scope = subtree user_attrs = \ =home=/glide/mail/spool/%{ldap:uid}, \ =mail=maildir:/glide/mail/spool/%{ldap:maildrop} user_filter = (&(objectClass=mailUser)(uid=%n)) iterate_attrs = uid=user iterate_filter = (objectClass=mailUser) cat /etc/dovecot/conf.d/dovecot-ldap-passdb.conf.ext hosts = localhost dn = cn=dovecot,dc=csi,dc=domain,dc=com dnpass = xxx ldap_version = 3 base = ou=instances,dc=csi,dc=domain,dc=com deref = never scope = subtree pass_attrs = uid=user,userPassword=password, \ =userdb_home=/glide/mail/spool/%{ldap:uid}, \ =userdb_mail=maildir:/glide/mail/spool/%{ldap:maildrop} pass_filter = (&(objectClass=inetLocalMailRecipient)(uid=%n)) ###################################### Only interesting thing from the debug logs is a prefetch related entry: ###################################### Apr 25 17:31:22 mda01 dovecot: auth: Debug: master in: USER#01119118#011dev13654#011service=doveadm Apr 25 17:31:22 mda01 dovecot: auth: Debug: prefetch(dev13654): passdb didn't return userdb entries, trying the next userdb Apr 25 17:31:22 mda01 dovecot: auth: Debug: ldap(dev13654): user search: base=ou=instances,dc=csi,dc=domain,dc=com scope=subtree filter=(&(objectClass=mailUser)(uid=dev13654)) fields=uid,maildrop Apr 25 17:31:22 mda01 dovecot: auth: Debug: ldap(dev13654): result: uid=dev13654 maildrop=dev13654/maildir/; maildrop,uid unused Apr 25 17:31:22 mda01 dovecot: auth: Debug: ldap(dev13654): result: uid=dev13654 maildrop=dev13654/maildir/ Apr 25 17:31:22 mda01 dovecot: auth: Debug: userdb out: USER#01119118#011dev13654#011home=/glide/mail/spool/dev13654#011mail=maildir:/glide/mail/spool/dev13654/maildir/ ######################################

1 0

doveadm backup 2.2.23 ignores -u, but reads USER environment?
by Heiko Schlittermann 26 Apr '16

26 Apr '16

Hi, during a migration (cyrus -> dovecot) we ran into trouble¹ using 'doveadm backup' with 2.2.9. So I built 2.2.22 and 2.2.23, but they expose quite different behaviour. 2.2.22 seems to work at least partially, but 2.2.23 complains about a non existing user (root?). The command I'm running is: doveadm -o pop3_uidl_format=%v.%u \ -o imapc_master_user=cyrus -o imapc_password=* -o imapc_host=* \ -o mail_fsync=never \ -o imapc_ssl_verify=no -o imapc_ssl=imaps -o imapc_port=993 \ backup -f -u heiko -R imapc: Using 2.2.9 or 2.2.22 it works, using 2.2.23 "-u …" is ignored and I've to pass the user via the USER environment. But according to the manpage of doveadm-sync -u user/mask Run the command only for the given user. It's also possible to use '*' and '?' wildcards (e.g. -u *(a)example.org) When neither the -A option, nor the -F file option, nor the -u user was specified, the command will be executed with the environment of the currently logged in user. Interestingly enough -u 'heiko*' works fine, even with USER=root. So the environment doesn't seem to override -u … always. Maybe an important side note: the user 'heiko' doesn't exist as a local system user, he is known via LDAP only. And for e.g. 'doveadm quota -u heiko' it works as expected, even with 2.2.23. ¹) solved meanwhile by using -o mail_plugins= as the quota plugin seems to crash 'doveadm backup' Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --------------- key ID: F69376CE - ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -

1 0

Setting up replication?
by Knute Johnson 25 Apr '16

25 Apr '16

I'm trying to set up replication between two servers and I've hit a snag. I have two users and am using mbox files. If anybody has a sample config file for a simple system like mine I would really be grateful to see it. Thanks, The error I'm getting is: Mar 23 14:07:31 knute2 dovecot: doveadm(192.168.3.100,nobody): Error: user nobody: Initialization failed: Namespace '': mkdir(/nonexistent/mail) failed: Permission denied (euid=65534(nobody) egid=65534(nogroup)) Mar 23 14:07:31 knute2 dovecot: doveadm(192.168.3.100,nobody): Error: dsync-server: User init failed Mar 23 14:07:31 knute2 dovecot: doveadm(nobody): Error: sync: Failed to start dsync-server command: 75 knute@knute2:/etc/dovecot/conf.d $ sudo doveadm user '*' nobody knute penny I don't know why the user 'nobody' shows up here? nobody is in the /etc/passwd file but he has no group. knute@knute2:/ $ cat /etc/passwd | grep nobody nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin ----------------------- I created a separate config file as suggested in Peer Heinlein's book. knute@knute2:/etc/dovecot/conf.d $ cat 12-replication.conf mail_plugins = $mail_plugins notify replication service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 } } service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0666 } } service doveadm { inet_listener { port = 30303 } } #doveadm_port = 30303 doveadm_password = secret plugin { mail_replica = tcp:knute2.frazmtn.com:30303 } replication_dsync_parameters = -d -N -l 30 -U --------------------- knute@knute2:/etc/dovecot/conf.d $ dovecot -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 4.1.19-v7+ armv7l Debian 8.0 doveadm_password = secret mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_plugins = " notify replication" namespace { inbox = yes location = mailbox { special_use = \Drafts name = Drafts } mailbox { special_use = \Junk name = Junk } mailbox { special_use = \Sent name = Sent } mailbox { special_use = \Sent name = Sent Messages } mailbox { auto = subscribe special_use = \Trash name = Trash } prefix = name = inbox } passdb { driver = pam } plugin { mail_replica = tcp:knute3.frazmtn.com:30303 } protocols = " imap" service { fifo_listener { mode = 0666 path = replication-notify-fifo } unix_listener { mode = 0666 path = replication-notify } name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service { inet_listener { port = 30303 name = } name = doveadm } service imap { inet_listener { port = 0 name = imaps } name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service { inet_listener { port = 0 name = pop3 } inet_listener { port = 0 name = pop3s } name = pop3-login } service login/pop3 { name = pop3 } service { process_min_avail = 1 unix_listener { mode = 0600 path = replicator-doveadm } name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { driver = passwd } protocol lmtp { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol lda { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol imap { mail_max_userip_connections = 32 service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } -- Knute Johnson

5 10

Moving to as new server
by Jerry 25 Apr '16

25 Apr '16

I will shortly have to replace the OS on my machine. For various reasons, I will not be able to use a program like “imapsync” to transfer my documents to a new server. All of the mail folders on my present PC are stored under “/var/mail/vmail”. If I copied all of the folders under “vmail” and moved them to the new PC, would Dovecot be able to access them normally? Dovecot would not be running while I moved the files. Thanks

3 2

expunging messages doesn't update maildirsize
by WJCarpenter 24 Apr '16

24 Apr '16

This might be something that everybody thinks of as a well-known fact, but I've been searching around quite a bit without finding anything definitive. Maybe I just have the wrong idea of what's supposed to be going on. I'm using maildir+ quotas. For arriving mail, it works as I expect: new lines are appended to maildirsize to reflect the size of the new messages. But I also expected that mail that is deleted (and expunged, yes totally gone from the disk drive, verified from the command line) would lead to some kind of update to maildirsize or maybe even a complete recalculation. But that does not happen on my system (dovecot 2.2.9 on a Ubuntu variant). Now, I know that I can run "doveadm" from a cron job or whatever to have the maildirsize info recomputed. I also know that the maildirsize file will be recreated when it gets larger than 4k. That's all fine. But I don't see why I should have to have this out-of-band cron job, and I don't see why my users should have to wait if their maildirsize file doesn't tip over the magical 4k mark (which is a lot of individual messages being recorded). Is it by design that dovecot doesn't update maildirsize immediately when messages are expunged? If yes, why?

1 1