- dovecot - dovecot.org

Public NameSpace using sdbox with INDEXPVT for per-user-seen flags does not take into account the dovecot-shared file flag
by Panayiotis Fafakos 29 Mar '21

29 Mar '21

Dear Timo, we have successfully used *dovecot-shared* file flag in *Maildir **Public *NameSpaces with private index files, to have per-user-seen flags for some but not all *mailboxes *under public folders. This was actually done on older dovecot versions (i.e *dovecot v2.2.33.2*) , using a *location* setting in *dovecot.conf* like: location = maildir:/var/vmail/PublicFolders:LAYOUT=fs:DIRNAME=privDirMailFolder:INDEX=~/Maildir/public We try to use similar *location* setting using *sdbox* storage in *dovecot v2.3.4.1*, like below: location = sdbox:/var/vmail/PublicFolders:LAYOUT=fs:DIRNAME=dbox-MailFolder:INDEXPVT=~/Maildir/public but the *dovecot-shared *file flag seems to be ignored. As a result all mailboxes under public folders use the per-user-seen flags setting as set in the location setting, regardless of the existence of the dovecot-shared file flag or not. Is there any setting to use so that only some mailboxes under public folders use per-user-seen flags? Thank you in advance for your support, Panos Fafakos.

2 2

Dovecot 2.3.14 - Invalid mailbox name: Name must not have '/' character
by Juergen Edner 27 Mar '21

27 Mar '21

Hi, after upgrading from Dovecot v2.3.13 to v2.3.14 I realized that shared sub-folders, e.g. "Lieferanten/Rechnungen", cannot be accessed anymore, although the underlying configuration hasn't been changed at all. If I try to access such a folder using e.g. Thunderbird the error "Invalid mailbox name: Name must not have '/' character." is shown instead of opening the folder. Now I wonder if this is a bug or feature or what need to be done to get the previous function back. In the change notes of the latest Dovecot version I found the following point, which might be the root cause of the problem: * If BROKENCHAR or listescape plugin is used, the escaped folder names may be slightly different from before in some situations. This is unlikely to cause issues, although caching clients may redownload the folders. These are my shared folder configuration parameters: namespace { location = maildir:/home/imapshared:INDEXPVT=~/.imapmail/shared prefix = "#Shared/" separator = / subscriptions = no type = shared } protocol imap { mail_max_userip_connections = 15 mail_plugins = " listescape" } I also checked how the shared folders are returned with both Dovecot version and cannot find any difference in the naming, except that the v2.3.13 correctly labels one folder as "\HasChildren", which v2.3.14 doesn't?! v2.3.13: a list "#Shared/" "*" * LIST (\HasChildren) "/" #Shared/Lieferanten * LIST (\HasNoChildren) "/" #Shared/Lieferanten/Rechnungen v2.3.14: a list "#Shared/" "*" * LIST (\HasNoChildren) "/" #Shared/Lieferanten * LIST (\HasNoChildren) "/" #Shared/Lieferanten/Rechnungen Any help/hint is highly appreciated. Thanks Juergen --

1 0

Dovecot 2.3.14 - Invalid mailbox name: Name must not have '/' character
by Jürgen Edner 27 Mar '21

27 Mar '21

Hi, after upgrading from Dovecot v2.3.13 to v2.3.14 I realized that shared sub-folders, e.g. "Lieferanten/Rechnungen", cannot be accessed anymore, although the underlying configuration hasn't been changed at all. If I try to access such a folder using e.g. Thunderbird the error "Invalid mailbox name: Name must not have '/' character." is shown instead of opening the folder. Now I wonder if this is a bug or feature or what need to be done to get the previous function back. In the change notes of the latest Dovecot version I found the following point, which might be the root cause of the problem: * If BROKENCHAR or listescape plugin is used, the escaped folder names may be slightly different from before in some situations. This is unlikely to cause issues, although caching clients may redownload the folders. These are my shared folder configuration parameters: namespace { location = maildir:/home/imapshared:INDEXPVT=~/.imapmail/shared prefix = "#Shared/" separator = / subscriptions = no type = shared } protocol imap { mail_max_userip_connections = 15 mail_plugins = " listescape" } I also checked how the shared folders are returned with both Dovecot version and cannot find any difference in the naming, except that the v2.3.13 correctly labels one folder as "\HasChildren", which v2.3.14 doesn't?! v2.3.13: a list "#Shared/" "*" * LIST (\HasChildren) "/" #Shared/Lieferanten * LIST (\HasNoChildren) "/" #Shared/Lieferanten/Rechnungen v2.3.14: a list "#Shared/" "*" * LIST (\HasNoChildren) "/" #Shared/Lieferanten * LIST (\HasNoChildren) "/" #Shared/Lieferanten/Rechnungen Any help/hint is highly appreciated. Thanks Juergen --

1 0

dsync error: Can't sync mailbox tmp: Mailbox isn't selectable
by Hagen Bauer 27 Mar '21

27 Mar '21

Hi, I am trying to use dsync to migrate from mbox to Maildir with dovecot --version 2.2.27 () The configuration seems to be working and some of the mailbox can be mirrored via dsync -u username mirror mbox:/home/username/mail:INBOX=/var/mail/username I have trouble with one user where I get the error. dsync(username2): Error: Can't sync mailbox tmp: Mailbox isn't selectable Any ideas where to look for hints? Regards Hagen Bauer

2 2

ssl_verify_client_cert=yes does not require a client certificate
by Hristo Venev 27 Mar '21

27 Mar '21

Hello, I am trying to set up LMTP over TLS. I have set ssl_verify_client_cert: protocol lmtp { ssl_ca = </etc/cert/mail/ca.pem ssl_cert = </etc/cert/mail/host.pem ssl_key = </etc/cert/mail/host.key ssl_verify_client_cert = yes } However, clients can still connect without presenting a valid certificate. In openssl_iostream_set() the flags given to SSL_set_verify() are SSL_VERIFY_PEER | SSL_VERIFY_CLIENT_ONCE. For a certificate to be required, the SSL_VERIFY_FAIL_IF_NO_PEER_CERT flag also needs to be set: diff --git a/src/lib-ssl-iostream/iostream-openssl.c b/src/lib-ssl-iostream/iostream-openssl.c index 5d11526f1..d8df96398 100644 --- a/src/lib-ssl-iostream/iostream-openssl.c +++ b/src/lib-ssl-iostream/iostream-openssl.c @@ -235,7 +235,7 @@ openssl_iostream_set(struct ssl_iostream *ssl_io, if (ssl_io->ctx->client_ctx) verify_flags = SSL_VERIFY_NONE; else - verify_flags = SSL_VERIFY_PEER | SSL_VERIFY_CLIENT_ONCE; + verify_flags = SSL_VERIFY_PEER | SSL_VERIFY_CLIENT_ONCE | SSL_VERIFY_FAIL_IF_NO_PEER_CERT; SSL_set_verify(ssl_io->ssl, verify_flags, openssl_iostream_verify_client_cert); }

2 2

Strange error on multiple recipent email - permission denied
by Salatiel Filho 27 Mar '21

27 Mar '21

Hi, I am doing some tests with dovecot to replace cyrusimapd, but after the most simple configuration I am getting some strange errors on log. This is the output of dovecot -n: #davecot -n disable_plaintext_auth = no ( just for testing ) first_valid_uid = 1000 mail_location = mbox:/var/spool/mail/%n mail_privileged_group = mail 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 { driver = pam } protocols = imap lmtp ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_cipher_list = PROFILE=SYSTEM ssl_key = # hidden, use -P to show it userdb { driver = passwd } I have also chmod a+rwxt on /var/spool/mail and set. Now here is the strange behavior. I have 2 users created, user1 and user2. At first , there are no files on /var/spool/mail as expected. Now I send one email to user1@mydomain and I can receive just fine and there are no errors on logs. Mar 27 00:32:20 mx2 dovecot[1473]: lmtp(1504): Connect from local Mar 27 00:32:20 mx2 sendmail[1503]: STARTTLS=client, relay=localhost, version=TLSv1.3, verify=FAIL, cipher=TLS_AES_256_GCM_SHA384, bits=256/256 Mar 27 00:32:20 mx2 dovecot[1473]: lmtp(user1)<1504><hzMPOBR9XmDgBQAAUY4zkw>: lmtp-server: conn unix:pid=1503,uid=0 [1]: rcpt user1: msgid=<CAGmni9qUfh_EntW-mMvdTK=bCc3QVQ+74f8X3BzBa5Z0dYi+-g(a)mail.gmail.com>: saved mail to INBOX Mar 27 00:32:20 mx2 sendmail[1503]: 12R0WKV0001502: to=<user1(a)mydomain.here>, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=32320, relay=localhost, dsn=2.0.0, stat=Sent Mar 27 00:32:20 mx2 sendmail[1503]: 12R0WKV0001502: done; delay=00:00:00, ntries=1 Mar 27 00:32:20 mx2 dovecot[1473]: lmtp(1504): Disconnect from local: Client has quit the connection (state=READY) Now I send one email to user2@mydomain and I can receive just fine and there are no errors on logs. Mar 27 00:33:45 mx2 dovecot[1473]: lmtp(1510): Connect from local Mar 27 00:33:46 mx2 sendmail[1509]: STARTTLS=client, relay=localhost, version=TLSv1.3, verify=FAIL, cipher=TLS_AES_256_GCM_SHA384, bits=256/256 Mar 27 00:33:46 mx2 dovecot[1473]: lmtp(user2)<1510><IUlGAWp9XmDmBQAAUY4zkw>: lmtp-server: conn unix:pid=1509,uid=0 [1]: rcpt user2: msgid=<CAGmni9qDHgDw=M6XPMk_eWb+02OJmCMarVe8sc_B4rNYUGMfGw(a)mail.gmail.com>: saved mail to INBOX Mar 27 00:33:46 mx2 sendmail[1509]: 12R0XjKj001508: to=<user2(a)mydomain.here>, delay=00:00:01, xdelay=00:00:01, mailer=local, pri=32318, relay=localhost, dsn=2.0.0, stat=Sent Mar 27 00:33:46 mx2 sendmail[1509]: 12R0XjKj001508: done; delay=00:00:01, ntries=1 Mar 27 00:33:46 mx2 dovecot[1473]: lmtp(1510): Disconnect from local: Client has quit the connection (state=READY) The problem starts if I send one email to user1 AND user2 ( user2 can be in TO or CC ) Mar 27 00:35:04 mx2 dovecot[1473]: lmtp(user2)<1518><AxH4Nbh9XmDuBQAAUY4zkw>: lmtp-server: conn unix:pid=1517,uid=0 [1]: rcpt user2: msgid=<CAGmni9oqid6pAEWPynAq9to-u0YdxE2o65wS34aeevnEWLj=AA(a)mail.gmail.com>: saved mail to INBOX Mar 27 00:35:04 mx2 dovecot[1473]: lmtp(user1)<1518><AxH4Nbh9XmDuBQAAUY4zkw:2>: Error: lmtp-server: conn unix:pid=1517,uid=0 [1]: rcpt user2: stat(/var/spool/mail/user2/.imap/INBOX/dovecot.index.log) failed: Permission denied (euid=1003(user1) egid=1003(user1) missing +x perm: /var/spool/mail/user2, dir owned by 1004:1004 mode=0700) Mar 27 00:35:04 mx2 dovecot[1473]: lmtp(user1)<1518><AxH4Nbh9XmDuBQAAUY4zkw:2>: Error: lmtp-server: conn unix:pid=1517,uid=0 [1]: rcpt user2: open(/var/spool/mail/user2/.imap/INBOX/dovecot.index) failed: Permission denied (euid=1003(user1) egid=1003(user1) missing +x perm: /var/spool/mail/user2, dir owned by 1004:1004 mode=0700) Mar 27 00:35:04 mx2 dovecot[1473]: lmtp(user1)<1518><AxH4Nbh9XmDuBQAAUY4zkw:2>: lmtp-server: conn unix:pid=1517,uid=0 [1]: rcpt user1: msgid=<CAGmni9oqid6pAEWPynAq9to-u0YdxE2o65wS34aeevnEWLj=AA(a)mail.gmail.com>: saved mail to INBOX Mar 27 00:35:04 mx2 sendmail[1517]: 12R0Z4h0001516: to=<user2(a)mydomain.here>,<user1(a)mydomain.here>, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=62302, relay=localhost, dsn=2.0.0, stat=Sent Mar 27 00:35:04 mx2 sendmail[1517]: 12R0Z4h0001516: done; delay=00:00:00, ntries=1 Mar 27 00:35:04 mx2 dovecot[1473]: lmtp(1518): Disconnect from local: Client has quit the connection (state=READY) Although I can receive the email, there's an ERROR log in maillog. It appears user1 wants to open the user2 index file. Any ideas why ? Thank you very much!

1 0

How to dimension hardware when using replication?
by Michael Westerburg 25 Mar '21

25 Mar '21

Hello Postmaster, for a decade we have been using Dovecot successfully as IMAP server at Augsburg University. Now we face the decision to switch from separated SAN storage to mirrored SAN storage by means of the usual combination of dovecot director and dovecot replicator (CentOS 7, Dovecot 2.2.36). Dovecot director runs on four virtual machines (4 cores, 4 GB memory). The replicated storage is handled by two HP servers with 2 Xeon(R) CPU E5-2620 (6 cores) and 32 GM memory. The network relies on 2 x 1 GBit Ethernet bond and two redundant 4 GBit SAN-fabrics. Our concerns, (1) is this equipment suitable? We are talking here about 25.000 mail accounts (LDAP) with 7 TB mail storage (mdbox) and in peak periods 10.000 parallel Dovecot processes and (2) what are adequate settings for director_user_expire, replication_max_conns and replication_full_sync_interval? Loosing mails is unacceptable as well as users stumbling upon mails with the recent flag set which were read and deleted yesterday. Who is using dovecot director and replicator and is willing to share settings and operational experience? Thanks in advance ++ Michael Westerburg -- Dr. Michael Westerburg Universität Augsburg Rechenzentrum 86135 Augsburg Telefon 0821/598-2004 Telefax 0821/598-2028 michael.westerburg(a)rz.uni-augsburg.de https://www.rz.uni-augsburg.de

1 0

Backtrace on UID SORT and UID SEARCH
by Pedro Ribeiro 25 Mar '21

25 Mar '21

Hello, I'm seeing a few backtraces like this ones in our daily log file. It always seem to happen during UID SEARCH or UID SORT I've already increased some process memory limits in the past and I'm currently using: default_vsz_limit = 512 M Is this some bug or I just need to increase this memory limit or some specific of a process? Using Dovecot 2.3.13 on Gentoo Linux amd64 Build options: ioloop=epoll notify=inotify openssl io_block_size=8192 SQL drivers: mysql Passdb: checkpassword passwd passwd-file shadow sql Userdb: checkpassword passwd prefetch passwd-file sql > Error: Raw backtrace: > /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x3d) [0x7efd24b8c04d] > /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7efd24b8c15e] > /usr/lib64/dovecot/libdovecot.so.0(+0xf4fcb) [0x7efd24b97fcb] > /usr/lib64/dovecot/libdovecot.so.0(+0xf5061) [0x7efd24b98061] > /usr/lib64/dovecot/libdovecot.so.0(+0x4e25b) [0x7efd24af125b] > /usr/lib64/dovecot/libdovecot.so.0(+0x4fcf1) [0x7efd24af2cf1] > /usr/lib64/dovecot/libdovecot.so.0(i_stream_read+0x2a) [0x7efd24ba3e3a] > /usr/lib64/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) > [0x7efd24ba477d] > /usr/lib64/dovecot/libdovecot.so.0(message_parse_header_next+0x69) > [0x7efd24b766b9] > /usr/lib64/dovecot/libdovecot.so.0(+0xd613a) [0x7efd24b7913a] > /usr/lib64/dovecot/libdovecot.so.0(+0xd62bf) [0x7efd24b792bf] > /usr/lib64/dovecot/libdovecot.so.0(message_parser_parse_next_block+0x44) > [0x7efd24b78894] > /usr/lib64/dovecot/libdovecot.so.0(message_search_msg+0xa0) > [0x7efd24b7acd0] > /usr/lib64/dovecot/libdovecot-storage.so.0(+0xcec2e) [0x7efd24f2ec2e] > /usr/lib64/dovecot/libdovecot-storage.so.0(+0x517c9) [0x7efd24eb17c9] > /usr/lib64/dovecot/libdovecot-storage.so.0(mail_search_args_foreach+0x45) > [0x7efd24eb27f5] > /usr/lib64/dovecot/libdovecot-storage.so.0(+0xcf96b) [0x7efd24f2f96b] > /usr/lib64/dovecot/libdovecot-storage.so.0(+0xd0d29) [0x7efd24f30d29] > /usr/lib64/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x61) > [0x7efd24f313b1] > /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x20) > [0x7efd24ebc240] > dovecot/imap [someuser2@ourdom 2001:1234::fb8 UID SORT](+0x26e97) > [0x564e1e21de97] > dovecot/imap [someuser2@ourdom 2001:1234::fb8 UID > SORT](imap_search_start+0xdc) [0x564e1e21e70c] > dovecot/imap [someuser2@ourdom 2001:1234::fb8 UID > SORT](cmd_sort+0x24b) [0x564e1e21058b] > dovecot/imap [someuser2@ourdom 2001:1234::fb8 UID > SORT](command_exec+0x64) [0x564e1e216d74] > dovecot/imap [someuser2@ourdom 2001:1234::fb8 UID SORT](+0x1deaf) > [0x564e1e214eaf] > dovecot/imap [someuser2@ourdom 2001:1234::fb8 UID SORT](+0x1df62) > [0x564e1e214f62] > dovecot/imap [someuser2@ourdom 2001:1234::fb8 UID SORT](+0x1e133) > [0x564e1e215133] > dovecot/imap [someuser2@ourdom 2001:1234::fb8 UID > SORT](client_handle_input+0x1ad) [0x564e1e21532d] > dovecot/imap [someuser2@ourdom 2001:1234::fb8 UID > SORT](client_input+0x72) [0x564e1e2157e2] > /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7efd24bad989] > Error: Raw backtrace: > /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x3d) [0x7f3c6b7b104d] > /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f3c6b7b115e] > /usr/lib64/dovecot/libdovecot.so.0(+0xf4fcb) [0x7f3c6b7bcfcb] > /usr/lib64/dovecot/libdovecot.so.0(+0xf5061) [0x7f3c6b7bd061] > /usr/lib64/dovecot/libdovecot.so.0(+0x4e25b) [0x7f3c6b71625b] > /usr/lib64/dovecot/libdovecot.so.0(+0x4fcf1) [0x7f3c6b717cf1] > /usr/lib64/dovecot/libdovecot.so.0(i_stream_read+0x2a) [0x7f3c6b7c8e3a] > /usr/lib64/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) > [0x7f3c6b7c977d] > /usr/lib64/dovecot/libdovecot.so.0(message_parse_header_next+0x69) > [0x7f3c6b79b6b9] > /usr/lib64/dovecot/libdovecot.so.0(+0xd613a) [0x7f3c6b79e13a] > /usr/lib64/dovecot/libdovecot.so.0(+0xd62bf) [0x7f3c6b79e2bf] > /usr/lib64/dovecot/libdovecot.so.0(message_parser_parse_next_block+0x44) > [0x7f3c6b79d894] > /usr/lib64/dovecot/libdovecot.so.0(message_search_msg+0xa0) > [0x7f3c6b79fcd0] > /usr/lib64/dovecot/libdovecot-storage.so.0(+0xcec2e) [0x7f3c6bb53c2e] > /usr/lib64/dovecot/libdovecot-storage.so.0(+0x517c9) [0x7f3c6bad67c9] > /usr/lib64/dovecot/libdovecot-storage.so.0(mail_search_args_foreach+0x45) > [0x7f3c6bad77f5] > /usr/lib64/dovecot/libdovecot-storage.so.0(+0xcf96b) [0x7f3c6bb5496b] > /usr/lib64/dovecot/libdovecot-storage.so.0(+0xd0d29) [0x7f3c6bb55d29] > /usr/lib64/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x10d) > [0x7f3c6bb5645d] > /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x20) > [0x7f3c6bae1240] > dovecot/imap [someuser@ourdom 192.168.166.58 UID SEARCH](+0x26e97) > [0x563bbf06de97] > dovecot/imap [someuser@ourdom 192.168.166.58 UID > SEARCH](command_exec+0x64) [0x563bbf066d74] > dovecot/imap [someuser@ourdom 192.168.166.58 UID SEARCH](+0x265e2) > [0x563bbf06d5e2] > /usr/lib64/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0x123) > [0x7f3c6b7d27b3] > /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xc7) > [0x7f3c6b7d3ed7] > /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x50) > [0x7f3c6b7d2a30] > /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7f3c6b7d2ba0] > /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) > [0x7f3c6b74a393] > dovecot/imap [someuser@ourdom 192.168.166.58 UID SEARCH](main+0x459) > [0x563bbf0571a9] > /lib64/libc.so.6(__libc_start_main+0xeb) [0x7f3c6b33182b] regards! -- Best regards, =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Pedro Ribeiro Politécnico de Lisboa, Serviços da Presidência Departamento de Sistemas de Informação e Comunicações Phone: +351 210 464 700 (general) / VoIP: 80100 Helpdesk: helpdesk(a)net.ipl.pt / https://www.net.ipl.pt =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

2 1

doveadm REST API: Delete home
by Patrick Ben Koetter 24 Mar '21

24 Mar '21

Hi! How can I remove a users mail home directory using the REST API? I'm trying to purge a users mailbox including the users $HOME, but it seems I'm on the wrong way. If I send a mailbox delete I end up with "Error: Can't delete INBOX: INBOX can't be deleted.", which kind of makes sense. Should I be using https://doc.dovecot.org/admin_manual/doveadm_http_api/#doveadm-fs-delete instead? TIA, p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

1 0

Don't count namespace space in quota
by Pedro Ribeiro 24 Mar '21

24 Mar '21

Hello everyone! I'm trying to figure a solution for this scenario. I have the Dovecot IMAP using MDBOX (SIS) storage for the daily usage email. For long term storage I'm preparing a namespace with MBOX storage. I'm not using the altstorage logic because as far as I know it needs to have the same format as the base one and for archival I prefer to have the attachments inside the messages in an old/well known format supported by near any email software. The problem at the moment is with quotas. If the user has 5GB in his mailboxes and the long term "historico" namespace has another 5GB, the storage used becomes 10GB and I want the users to only see their "active" usage (5GB). I have that space to be ignored (as defined in the wiki and dovecot documentation - my quota_rule5 ) but it doesn't seem to influence the usage reported by IMAP. What am I doing wrong? If I put the "historico"namespace with disabled = yes and do a "doveadm quota recalc" the values become correct but I need the namespace available so the users can recover their old messages if needed. The relevant settings (AFAIK) I'm using are: plugin { quota = dict:FileQuota:ns=:file:%h/dovecot-quota quota2 = dirsize:HistQuota:ns=@HISTORICO/ quota_clone_dict = proxy::quota quota_grace = 10%% quota_rule = *:storage=24G quota_rule2 = Trash:storage=+128M quota_rule3 = Junk:storage=+64M quota_rule4 = INBOX:storage=+128M quota_rule5 = ns=@HISTORICO:ignore } namespace historico { disabled = no hidden = no ignore_on_failure = yes inbox = no list = no location = mbox:/mnt/mail-hist/historic/%d/%-2.2n/%n:SUBSCRIPTIONS=.imap/dovecot-subscriptions:LAYOUT=maildir++ order = 0 prefix = @HISTORICO/ separator = / subscriptions = yes type = private } namespace inbox { disabled = no hidden = no ignore_on_failure = no inbox = yes list = yes location = order = 0 prefix = separator = / subscriptions = yes type = private } userdb { args = /etc/dovecot/dovecot-sql.conf.ext auth_verbose = default default_fields = home=/data/domains/%d/%-2.2n/%n lport=%{lport} driver = sql } best regards to all the Dovecot community, stay safe! -- Best regards, =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Pedro Ribeiro Politécnico de Lisboa, Serviços da Presidência Departamento de Sistemas de Informação e Comunicações Phone: +351 210 464 700 (general) / VoIP: 80100 Helpdesk: helpdesk(a)net.ipl.pt / https://www.net.ipl.pt =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

2 2

Custom sql queries in acl-plugin
by Matthias Kneer 23 Mar '21

23 Mar '21

Hi, I would like to allow users to use any known "alias" of another user to grant permissions to their mailboxes. Here's the scenario: A user, with an internal name "example@12345" and an alias "test(a)example.org". The domain "12345" is only used internally to separate the customers into different directories, therefore "anotheruser" only knows the address "test(a)example.org" grants folder permissions to "test(a)example.org". This results in the following: +-------------------------+--------------------------------------------+-------+ | from_user | to_user | dummy | +-------------------------+--------------------------------------------+-------+ | anotheruser@12345 | test(a)example.org | 1 | +-------------------------+--------------------------------------------+-------+ But since the actual username is "example@12345" the proper directory can't be found. I would like to achieve the following outcome, with the same user inputs: +-------------------------+--------------------------------------------+-------+ | from_user | to_user | dummy | +-------------------------+--------------------------------------------+-------+ | anotheruser@12345 | example@12345 | 1 | +-------------------------+--------------------------------------------+-------+ Is it possible to populate the to_user column with a more dynamic sql lookup instead of the dict lookup? Thanks in advance, Matthias

1 0

prevent INBOX rename
by mj 22 Mar '21

22 Mar '21

Hi, One of our users managed to rename her INOX folder to ' ' (space) This caused a new INBOX directory to be created, and all older emails to become 'invisible' to her. My question: Is there a (dovecot config) way to prevent this from happening? We cannot image any scenario where we would like a user to be able to rename INBOX. > imap(username)<12135><bsJbjpO9gN7AV48G>: Mailbox renamed: INBOX -> Debian buster, dovecot 2.3.4.1 Thanks!

1 0

feature request: maintain folder structure with expunged email
by Marc 22 Mar '21

22 Mar '21

Currently when I am expunging messages, the expunged (to be purged messages) are counted / listed at INBOX. Say for instance that a user would accidentally delete the mailbox 2014. The whole folder structure below it would be lost. If someone creates a folder structure, this folder structure has important added value. I have my doubts on this design discarding of mailboxes like this. I think the use of mailboxes/folder structures is not valued enough. If you have a lot of email and put these emails in folders, the folder structure is part of the important information. Currently this 'important information' is lost with expunging. I can understand that it maybe quite an effort to implement preserving this information. But using the doveadm import to restore a lot of emails, is really not an option. I assume that also restoring email from a specific folder does not work. Say I delete foldera, folderb and folderc. How can I get back folderb. [@]# mailbox-ls.sh testtest size listing mailboxes of rittest: Archive msgs=0 vsize=0B Archive/2011 msgs=0 vsize=0B Archive/2012 msgs=0 vsize=0B Archive/2013 msgs=8 vsize=7.4KiB Archive/2014 msgs=0 vsize=0B Archive/2015 msgs=0 vsize=0B Archive/2016 msgs=0 vsize=0B Archive/2017 msgs=1214 vsize=103MiB Archive/2018 msgs=70 vsize=5.9MiB Archive/2019 msgs=221 vsize=18MiB Archive/Archive msgs=1 vsize=2.4KiB Archive/INBOX msgs=0 vsize=0B Drafts msgs=9 vsize=16MiB delmsgs=0 delvsize=0B INBOX msgs=51 vsize=107MiB delmsgs=3 delvsize=18MiB INBOX/test2 msgs=1 vsize=5.8MiB delmsgs=0 delvsize=0B Junk msgs=2 vsize=2.0KiB delmsgs=0 delvsize=0B RESTORED msgs=0 vsize=0B delmsgs=0 delvsize=0B RESTORED/INBOX msgs=3 vsize=18MiB delmsgs=0 delvsize=0B Sent msgs=17 vsize=7.3KiB delmsgs=0 delvsize=0B test1 msgs=3 vsize=12MiB delmsgs=0 delvsize=0B test3 msgs=0 vsize=0B delmsgs=0 delvsize=0B Trash msgs=0 vsize=0B delmsgs=0 delvsize=0B Feature request: maintain folder/mailbox structure with expunging.

2 2

Is it possible to use per user keys with mail-crypt-plugin when using passwd-file backend?
by Davy Landman 21 Mar '21

21 Mar '21

I've been reading quite a bit of discussions, the manual and a few often linked posts about mail-crypt-plugin, but most of them seem to assume a sql db backing. But if you are using a passwd file userdb, is it possible to make the per-user-key mode of the mail-crypt-plugin work? I like the trick of passing in the key via an extra calculated/virtual column in the query (even allows for hashing the password for example). But I cannot see how this can work with the passwd backing? Any pointers would be appreciated. Kind regards, Davy (Why so focussed on passwd files? I'm using the docker-mailserver setup that takes care of a lot of messy setup, so I rather not redo that just so that I can switch to a db for storing the user details of maybe 2 to 3 users)

2 2

FW: imapsieve rules not matching at all?
by dovecot＠steve.wattlink.net 20 Mar '21

20 Mar '21

Greetings! I feel like this has been beaten to death, but my searches on the web (and about 10 hours spent over the last two days) haven't revealed what's going on. Basically, it's the usual "I'd like to auto-learn spam/ham based on moves to/from a folder" problem. But in my debugging, I don't see any evidence that the static rules are matching, so the scripts aren't running, which makes me think I'm missing something obvious. Below I list doveconf -n output, and some log snippets. In my experiments, I've tried removing the report-spam.sieve and report-ham.sieve scripts, and absolutely nothing changed, which is why I think the rules aren't being tried. The requisite doveconf -n output: - - - -8< - - - - # 2.3.13 (89f716dc2): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: FreeBSD 12.2-RELEASE-p1 amd64 # Hostname: mhv3 lock_method = dotlock mail_attribute_dict = file:%h/Maildir/dovecot-attributes mail_debug = yes mail_location = maildir:~/Maildir 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 index ihave duplicate mime foreverypart extracttext vnd.dovecot.debug vnd.dovecot.environment imapsieve vnd.dovecot.imapsieve vnd.dovecot.pipe vnd.dovecot.execute 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 { driver = pam } plugin { imapsieve_mailbox1_before = file:/usr/local/etc/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY APPEND imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/usr/local/etc/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * imapsieve_url = sieve://127.0.0.1:4190 sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /usr/local/etc/dovecot/sieve/common.sieve sieve_default = /usr/local/etc/dovecot/sieve/default.sieve sieve_default_name = SystemDefault sieve_execute_bin_dir = /usr/local/etc/dovecot/sieve/bin sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment +vnd.dovecot.execute +vnd.dovecot.debug sieve_filter_bin_dir = /usr/local/etc/dovecot/sieve/bin sieve_global = /usr/local/etc/dovecot/sieve sieve_pipe_bin_dir = /usr/local/etc/dovecot/sieve/bin sieve_plugins = sieve_imapsieve sieve_extprograms sieve_trace_addresses = no sieve_trace_debug = yes sieve_trace_dir = /var/log/dovecot/trace sieve_trace_level = matching } protocols = imap lmtp sieve service imap-login { inet_listener imap { address = 127.0.0.1 } } service managesieve-login { inet_listener sieve { port = 4190 } } ssl_cert = </etc/ssl/services/dovecot.cert ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd } protocol lda { mail_plugins = " sieve" } protocol imap { imap_metadata = yes mail_max_userip_connections = 30 mail_plugins = " imap_sieve" } - - - ->8 - - - - I see that the static rule ought to have matched, but it didn't? - - - - 8<- - - - Mar 19 16:21:47 mhv3 dovecot[47532]: imap(steve)<47539><CdLa+uu9iNkYgsde>: Debug: sieve: Pigeonhole version 0.5.13 (cdd19fe3) initializing Mar 19 16:21:47 mhv3 dovecot[47532]: imap(steve)<47539><CdLa+uu9iNkYgsde>: Debug: sieve: Sieve imapsieve plugin for Pigeonhole version 0.5.13 (cdd19fe3) loaded Mar 19 16:21:47 mhv3 dovecot[47532]: imap(steve)<47539><CdLa+uu9iNkYgsde>: Debug: sieve: Sieve Extprograms plugin for Pigeonhole version 0.5.13 (cdd19fe3) loaded Mar 19 16:21:47 mhv3 dovecot[47532]: imap(steve)<47539><CdLa+uu9iNkYgsde>: Debug: imapsieve: Static mailbox rule [1]: mailbox=`Spam' from=`*' causes=(COPY APPEND) => before=`file:/usr/local/etc/dovecot/sieve/report-spam.sieve' after=(none) Mar 19 16:21:47 mhv3 dovecot[47532]: imap(steve)<47539><CdLa+uu9iNkYgsde>: Debug: imapsieve: Static mailbox rule [2]: mailbox=`*' from=`Spam' causes=(COPY) => before=`file:/usr/local/etc/dovecot/sieve/report-ham.sieve' after=(none) Mar 19 16:21:47 mhv3 dovecot[47532]: imap(steve)<47539><CdLa+uu9iNkYgsde>: Debug: Mailbox Spam: Mailbox opened because: SELECT Mar 19 16:21:48 mhv3 dovecot[47532]: imap(steve)<47541><ROnt+uu9idkYgsde>: Debug: Loading modules from directory: /usr/local/lib/dovecot Mar 19 16:21:48 mhv3 dovecot[47532]: imap(steve)<47541><ROnt+uu9idkYgsde>: Debug: Module loaded: /usr/local/lib/dovecot/lib95_imap_sieve_plugin.so Mar 19 16:21:48 mhv3 dovecot[47532]: imap(steve)<47541><ROnt+uu9idkYgsde>: Debug: Effective uid=1001, gid=1000, home=/home/steve Mar 19 16:21:48 mhv3 dovecot[47532]: imap(steve)<47541><ROnt+uu9idkYgsde>: Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/Maildir Mar 19 16:21:48 mhv3 dovecot[47532]: imap(steve)<47541><ROnt+uu9idkYgsde>: Debug: maildir++: root=/home/steve/Maildir, index=, indexpvt=, control=, inbox=/home/steve/Maildir, alt= Mar 19 16:21:48 mhv3 dovecot[47532]: imap(steve)<47541><ROnt+uu9idkYgsde>: Debug: Mailbox INBOX: Mailbox opened because: SELECT Mar 19 16:21:48 mhv3 dovecot[47532]: imap(steve)<47541><ROnt+uu9idkYgsde>: Debug: imapsieve: mailbox INBOX: APPEND event Mar 19 16:21:48 mhv3 dovecot[47532]: imap(steve)<47541><ROnt+uu9idkYgsde>: Debug: imapsieve: mailbox INBOX: Mailbox attribute /shared/imapsieve/script not found Mar 19 16:21:48 mhv3 dovecot[47532]: imap(steve)<47541><ROnt+uu9idkYgsde>: Debug: imapsieve: mailbox INBOX: Server attribute /shared/imapsieve/script not found Mar 19 16:21:48 mhv3 dovecot[47532]: imap(steve)<47541><ROnt+uu9idkYgsde>: Debug: sieve: Pigeonhole version 0.5.13 (cdd19fe3) initializing Mar 19 16:21:48 mhv3 dovecot[47532]: imap(steve)<47541><ROnt+uu9idkYgsde>: Debug: sieve: Sieve imapsieve plugin for Pigeonhole version 0.5.13 (cdd19fe3) loaded Mar 19 16:21:48 mhv3 dovecot[47532]: imap(steve)<47541><ROnt+uu9idkYgsde>: Debug: sieve: Sieve Extprograms plugin for Pigeonhole version 0.5.13 (cdd19fe3) loaded Mar 19 16:21:48 mhv3 dovecot[47532]: imap(steve)<47541><ROnt+uu9idkYgsde>: Debug: imapsieve: Static mailbox rule [1]: mailbox=`Spam' from=`*' causes=(COPY APPEND) => before=`file:/usr/local/etc/dovecot/sieve/report-spam.sieve' after=(none) Mar 19 16:21:48 mhv3 dovecot[47532]: imap(steve)<47541><ROnt+uu9idkYgsde>: Debug: imapsieve: Static mailbox rule [2]: mailbox=`*' from=`Spam' causes=(COPY) => before=`file:/usr/local/etc/dovecot/sieve/report-ham.sieve' after=(none) Mar 19 16:21:49 mhv3 dovecot[47532]: imap(steve)<47541><ROnt+uu9idkYgsde>: Debug: Mailbox INBOX: Mailbox opened because: SELECT Mar 19 16:21:54 mhv3 dovecot[47532]: imap(steve)<47541><ROnt+uu9idkYgsde>: Debug: Mailbox INBOX: UID 77131: Opened mail because: prefetch Mar 19 16:21:54 mhv3 dovecot[47532]: imap(steve)<47541><ROnt+uu9idkYgsde>: Debug: Mailbox INBOX: UID 77131: Opened mail because: access Mar 19 16:21:54 mhv3 dovecot[47532]: imap(steve)<47541><ROnt+uu9idkYgsde>: Debug: Mailbox INBOX: UID 77131: Opened mail because: full mail - - - ->8 - - - - Thanks for clues, -- Steve Watt KD6GGD PP-ASEL-IA factories.words.yappy Don't let your schooling get in the way of your education.

6 10

Error mailbox: Sync failed
by Elise 19 Mar '21

19 Mar '21

Dear team, Lately I get these messages randomly in my logfile: imap(elise)<68480><3asBXUG9A9hSsH9H>: Error: Mailbox INBOX: Sync failed for mbox: UID inserted in the middle of mailbox (186165 > 186164, seq=4, idx_msgs=4): 1 Time(s) I use IMAP for Outlook 2019 and Thunderbird clients simoultanious icw Dovecot 2.3.13 Can you tell me how to solve this issue? thanks. /elise

1 1

bug: some table header(?) output goes to stderr instead of stdout
by Marc 19 Mar '21

19 Mar '21

[@ sbin]# doveadm -f table -o mail_location=mdbox_deleted:/home/popusers/testtest/mdbox:INDEX=/home/popindex/testtest/index fetch -u testtest 'guid' mailbox INBOX 2> /dev/null 3c967f33b8aea671f3551db1ea8e33e9 6fa01ccc103a7009c7b940657dbcd72c ba955a6d6218950f42e5b0ee0a33a916 [@ sbin]# doveadm -f table -o mail_location=mdbox_deleted:/home/popusers/testtest/mdbox:INDEX=/home/popindex/testtest/index fetch -u testtest 'guid' mailbox INBOX guid 3c967f33b8aea671f3551db1ea8e33e9 6fa01ccc103a7009c7b940657dbcd72c ba955a6d6218950f42e5b0ee0a33a916

3 4

bug(?): trailing tab/whitespace in output
by Marc 19 Mar '21

19 Mar '21

doveadm -v -f table search -u testtest mailbox Archive/2011 guid 1de6d8632073c49f272bed211b71a8b6 returns this (echo ".$guid.") .1de6d8632073c49f272bed211b71a8b6 .

1 0

feature request: doveadm purge taking guid argument
by Marc 18 Mar '21

18 Mar '21

Hi Timo, What about giving doveadm purge an argument to delete a specific message guid? Is that a lot of work?

1 0

Some questions about code in lib-storage/index/maildir
by songliny 18 Mar '21

18 Mar '21

Hi, Recently, I have read some code in dovecot 2.3.13. And I have 2 questions about some lines of code in lib-storage/index/maildir Firstly, in the function, maildir_scan_dir, from lib-storage/index/maildir/maildir-sync.c around line 575 (https://github.com/dovecot/core/blob/6986a435e31dfe5bcd14985534b76b3c735f78…) I would like to know that after successfully stat the cur directory, does it assign the max value between st.st_mtime and start_time intensionally to new_check_time? Or maybe should it assign the value to the cur_check_time. if (stat(ctx->cur_dir, &st) == 0) { ctx->mbox->maildir_hdr.new_check_time = I_MAX(st.st_mtime, start_time); ctx->mbox->maildir_hdr.cur_mtime = st.st_mtime; ctx->mbox->maildir_hdr.cur_mtime_nsecs = ST_MTIME_NSEC(st); } Secondly, in the function, maildir_uidlist_sync_next_uid, from lib-storage/index/maildir/maildir-uidlist.c (https://github.com/dovecot/core/blob/6986a435e31dfe5bcd14985534b76b3c735f78… rc/lib-storage/index/maildir/maildir-uidlist.c#L1760) Is it ok to remove MAILDIR_UIDLIST_REC_FLAG_NEW_DIR flag from the record for the record that is not found in ctx->files just like the behavior (https://github.com/dovecot/core/blob/6986a435e31dfe5bcd14985534b76b3c735f78… the function, maildir_uidlist_sync_next_partial (https://github.com/dovecot/core/blob/6986a435e31dfe5bcd14985534b76b3c735f78…) from the same file? I think when it gets to the function, maildir_uidlist_sync_next_uid, the mail file have already been moved to cur directory. And maybe it is ok to remove MAILDIR_UIDLIST_REC_FLAG_NEW_DIR flag from the record. That is, is it ok to add this line rec->flags &= ENUM_NEGATE(MAILDIR_UIDLIST_REC_FLAG_NEW_DIR); just before rec->flags = (rec->flags | flags) & ENUM_NEGATE(MAILDIR_UIDLIST_REC_FLAG_NONSYNCED); in maildir_uidlist_sync_next_uid? Thank you in advance to he lp me get more understanding to these questions, Sony

1 0

dovecot director and keepalived
by Steven Varco 18 Mar '21

18 Mar '21

Hi All I’m trying to establish a dovecot HA setup with two loadbalancers, running keepalived for sharing a virtual public IP. On the same machines I’m running a dovecot director which proxies the requests to two underlying mail servers (on seperate machines). Now I’m hitting the issue with the way director determines his „Self IP“ by trying to bind to all configured director_servers IPs, taking the first one possible. However this approach only works, when the sysctl setting is: net.ipv4.ip_nonlocal_bind=0 On the other side keepalived needs net.ipv4.ip_nonlocal_bind=1 in order to bind the VIP. The last topic on that is dating back to 2016 (https://dovecot.org/pipermail/dovecot/2016-August/105191.html) with references to 2012 (https://www.dovecot.org/list/dovecot/2012-November/087033.html) and no solution posted so far. After five more years :D, I’m asking myself if we finally have a solution for that, or if my approach of achieving clustered director servers is potentially wrong? Other possible solutions I could think about: - Configure each director as „independent“ by setting only one IP in director_servers. => With this aporach you would loose the user to mailserver mapping, although only in a a case of a failover on the loadbalancer, which might can be neglected (or are there any other fallbacks?) - Only have director running on the currently active loadblancer node and stopped on the passive loadblancer node (would possibly have the same effects as above). - Putting director on seperated intermediate machines and proxing the requests through haproxy on the keepalived servers (keepalived -> haproxy -> director -> IMAP => Besides the disadvantage of having another bunch of servers in the chain, also some special configuration on the directory servers might be neccessary to assure director works neatly with haproxy. So 2021, what is the „correct“ (best practive) way of having a reduntant HA setup for dovecot? This means a MUA connects to one public IP and gets connected to (preferably the same) IMAP Server, no matter which machine in the whole chain might be down? PS: Using just multiple A records on the mail domain name (round-robin), while working perfectly for SMTP is not accepatbl for IMAP IMHO, as in case of a failure every second request from the client (MUA) would fail and most MUAs are not automatially reconnecting again in that case. thanks, Steven -- https://steven.varco.ch/

7 10

best practice purging only moved messages
by Marc 18 Mar '21

18 Mar '21

If I move a message from the 'inbox' namespace to my 'archive' namespace. The message is expunged at the 'inbox' namespace and added to the 'archive' namespace. What is the best way to only purge messages that have been moved. (I do not want to purge emails that have been deleted yet)

1 0

How can I migrate mailboxes after changing hierarchy separator?
by Popkornium18 17 Mar '21

17 Mar '21

Hi, I had a common problem (folders can't contain dots) and the obvious solution seems to be changing the hierarchy separator and using the listescape plugin. My question is: Do I need to take any extra steps after changing the separator to migrate my existing mailboxes? If so, which? I tried just simply renaming the folders and doing a `doveadm force-resync` but that did not work as intended. Afterwards I wasn't able to subscribe to any of my folders, so I guess that isn't the way to go. Kind regards Simon

1 0

inconsistency in reporting from mdbox_deleted
by Marc 17 Mar '21

17 Mar '21

This reports all folders, ok [@ testtest]# doveadm -o mail_location=mdbox_deleted:/home/mail-archive/testtest/Archive:INDEX=/home/archiveindex/testtest/index mailbox status -u testtest 'messages vsize' '*' 2011 messages=0 vsize=0 2012 messages=0 vsize=0 2013 messages=0 vsize=0 2014 messages=0 vsize=0 2015 messages=0 vsize=0 2016 messages=0 vsize=0 2017 messages=0 vsize=0 2018 messages=0 vsize=0 2019 messages=0 vsize=0 doveadm(testtest): Error: Mailbox Archive: Failed to lookup mailbox status: Mailbox doesn't exist: Archive INBOX messages=15 vsize=12066832 This gets folder INBOX, ok [@ testtest]# doveadm -o mail_location=mdbox_deleted:/home/mail-archive/testtest/Archive:INDEX=/home/archiveindex/testtest/index mailbox status -u testtest 'messages vsize' 'INBOX' INBOX messages=15 vsize=12066832 This reports error that a folder does not exist, ok [@ testtest]# doveadm -o mail_location=mdbox_deleted:/home/mail-archive/testtest/Archive:INDEX=/home/archiveindex/testtest/index mailbox status -u testtest 'messages vsize' 'asdfasdfasdfasdf' doveadm(testtest): Error: Mailbox asdfasdfasdfasdf: Failed to lookup mailbox status: Mailbox doesn't exist: asdfasdfasdfasdf This query for Archive/2012 reports same as for 2012(?), by design, I guess ok [@ testtest]# doveadm -o mail_location=mdbox_deleted:/home/mail-archive/testtest/Archive:INDEX=/home/archiveindex/testtest/index mailbox status -u testtest 'messages vsize' 'Archive/2012' Archive/2012 messages=0 vsize=0 This reports 0?, This should either report the folder does not exist, or it should report the same as getting the INBOX, like previous result [@ testtest]# doveadm -o mail_location=mdbox_deleted:/home/mail-archive/testtest/Archive:INDEX=/home/archiveindex/testtest/index mailbox status -u testtest 'messages vsize' 'Archive/INBOX' Archive/INBOX messages=0 vsize=0

1 0

feature request: prevent linking of email
by Marc 17 Mar '21

17 Mar '21

What I have been doing wrong with testing expunged emails, is working with linked copies of emails. Although thunderbird copies the message, it looks like the message is NOT copied but linked. If I drag 3 emails from my desktop to a folder INBOX/test4 and copy 1 message from INBOX to INBOX/test4. I have 4 messages in this folder. I now shift+del this folder. The expunged messages listing gives me the expected 3 messages doveadm -o mail_location=mdbox_deleted:/home/popusers/testtest/mdbox:INDEX=/home/popindex/testtest/index mailbox status -u testtest 'messages vsize' '*' Sent messages=0 vsize=0 Drafts messages=0 vsize=0 INBOX/test2 messages=0 vsize=0 Junk messages=0 vsize=0 Trash messages=0 vsize=0 test3 messages=0 vsize=0 test1 messages=0 vsize=0 RESTORED messages=0 vsize=0 INBOX messages=3 vsize=18079344 Lets recover these: doveadm -v import -u testtest 'mdbox_deleted:/home/popusers/testtest/mdbox:INDEX=/home/popindex/testtest/index' RESTORED ALL Now I have 3 messages back, as expected. From an end users perspective if you delete a folder with 4 emails, you want your restored backup to have 4 emails, not 3 because one is already somewhere else in your folder/mailbox structure. The reason for copying an email to a different folder is that it is important. You do not want to loose it, and you want to be able to find it there. It is wrong to assume that a user will notice that these emails are missing and should look for them elsewhere. Say you have folder for a court case, and you copy emails there relevant for the court case. How can you ever know after a restore that a few email are missing from the folder, and which ones. I think it is bad this email is currently 'lost'. I rather have an option in dovecot that disables this hidden 'deduplication' feature. I think this should be the default setting also. This current deduplication feature also is hazardous because if this one copy of the email gets corrupted on the storage, you have no copies left. That is exactly the opposite of what user wants to accomplish with creating a copy. Feature request: disable this automatic linking of emails between mailboxes. Feature request: set this as a default.

2 3

Ability to put dovecot version in received header
by Kamil Jońca 17 Mar '21

17 Mar '21

I know that some time ago there was a discussion and this is conscious decision to remove dovecot version from headers during lmtp delievery. But is it possible to restore it as an option? -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html

3 3

Latest dovecot does not work with latest MUA (thunderbird)
by lja＠koti 17 Mar '21

17 Mar '21

Hi, Latest dovecot does not work with latest thunderbird. It does not react to sent emails. They are put to maildir by postfix a-ok. The version of thunderbird that works ok: 68.12.1 Distro: Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal $ dovecot -n # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.9.0-rc5 x86_64 Ubuntu 20.04.2 LTS # Hostname: superman.sillywalk.org auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = plain debug_log_path = /var/log/dovecot-debug.log info_log_path = /var/log/dovecot-info.log log_path = /var/log/dovecot.log mail_debug = yes mail_location = maildir:~/Maildir/ 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 { driver = pam } protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = mail mode = 0660 user = postfix } } ssl_cert = </etc/letsencrypt/live/lja.fi/fullchain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd } protocol imap { imap_metadata = yes } local_name paxsudos.fi { ssl_cert = </etc/letsencrypt/live/somethingB.fi/fullchain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it } local_name paxsudos.com { ssl_cert = </etc/letsencrypt/live/somethingB.com/fullchain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it } local_name lja.fi { ssl_cert = </etc/letsencrypt/live/somethingA.fi/fullchain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it } -- <https://paxsudos.com/> ,-- Information -------------------------------------------------------- ------ --- -- - | Lauri Jakku | Contact: | Phone: +358 40 220 3910 | Address: Puusepänkatu 1 A 3, 90130 Oulu, Finland '--------------- -------- ----- ----- ------- ---- --- -- Firmani, Paxsudos IT, kautta olen jättämässä oman, vaikka pienen, jäljen ympäristötekoina, että tulevaisuudessakin voimme nauttia luonnosta. Ympäristö ja luonto on sellaista joita otamme itsestäänselvyyksinä, tuon takia on käymässä niin että havahdumme kun on tilanne erittäin huono. We offset our carbon footprint via Ecologi <https://ecologi.com/paxsudosit> ,-- Virus scan done for content -------------------------------------------------------- ------ --- -- - | Known viruses: 10722370 | Engine version: 0.102.4 | Scanned directories: 0 | Scanned files: 1 | Infected files: 0 | Data scanned: 0.01 MB | Data read: 0.01 MB (ratio 1.00:1) | Time: 16.864 sec (0 m 16 s) '--------------- -------- ----- ----- ------- ---- --- --

5 9

feature request: doveadm -Dv purge
by Marc 17 Mar '21

17 Mar '21

Maybe list emails being purged

1 0

how to search expunged messages
by Marc 16 Mar '21

16 Mar '21

Is there an equivalent for expunged messages of this: doveadm search -u testtest mailbox '*' DELETED

2 2

another try listing expunged mail, now only tested with dovecot cli
by Marc 16 Mar '21

16 Mar '21

testing with expunging messages with subject "delete me" this is the correct commend to list expunged messages? [@ testtest]# doveadm -o mail_location=mdbox_deleted:/home/popusers/testtest/mdbox:INDEX=/home/popindex/testtest/index mailbox status -u testtest 'messages vsize' '*' Sent messages=0 vsize=0 Drafts messages=0 vsize=0 INBOX/test2 messages=0 vsize=0 Junk messages=0 vsize=0 Trash messages=0 vsize=0 test3 messages=0 vsize=0 test1 messages=0 vsize=0 INBOX messages=0 vsize=0 We have a few messages with subject 'delete me' in the inbox namespace [@ ~]# doveadm search -u testtest mailbox test1 subject 'delete me' | wc -l 4 [@ ~]# doveadm search -u testtest mailbox INBOX/test2 subject 'delete me' | wc -l 2 [@ ~]# doveadm search -u testtest mailbox test3 subject 'delete me' | wc -l 8 Disk space used [@ testtest]# du -s -k /home/popusers/testtest/mdbox/storage/ 135356 /home/popusers/testtest/mdbox/storage/ Ok lets expunge some emails [@ testtest]# doveadm expunge -u testtest mailbox test1 subject 'delete me' doveadm(testtest): Info: expunge: box=test1, msgid=<202011052050.0A5Ko7Jc005461(a)web01.xxxxxx.xxxx> doveadm(testtest): Info: expunge: box=test1, msgid=<202011052050.0A5Ko7Jc005461(a)web01.xxxxxx.xxxx> doveadm(testtest): Info: expunge: box=test1, msgid=<202011052050.0A5Ko7Jc005461(a)web01.xxxxxx.xxxx> doveadm(testtest): Info: expunge: box=test1, msgid=<202011052050.0A5Ko7Jc005461(a)web01.xxxxxx.xxxx> [@ testtest]# doveadm expunge -u testtest mailbox INBOX/test2 subject 'delete me' doveadm(testtest): Info: expunge: box=INBOX/test2, msgid=<202011052050.0A5Ko7Jc005461(a)web01.xxxxxx.xxxx> doveadm(testtest): Info: expunge: box=INBOX/test2, msgid=<202011052050.0A5Ko7Jc005461(a)web01.xxxxxx.xxxx> [@ testtest]# doveadm expunge -u testtest mailbox test3 subject 'delete me' doveadm(testtest): Info: expunge: box=test3, msgid=<202011052050.0A5Ko7Jc005461(a)web01.xxxxxx.xxxx> doveadm(testtest): Info: expunge: box=test3, msgid=<202011052050.0A5Ko7Jc005461(a)web01.xxxxxx.xxxx> doveadm(testtest): Info: expunge: box=test3, msgid=<202011052050.0A5Ko7Jc005461(a)web01.xxxxxx.xxxx> doveadm(testtest): Info: expunge: box=test3, msgid=<202011052050.0A5Ko7Jc005461(a)web01.xxxxxx.xxxx> doveadm(testtest): Info: expunge: box=test3, msgid=<202011052050.0A5Ko7Jc005461(a)web01.xxxxxx.xxxx> doveadm(testtest): Info: expunge: box=test3, msgid=<202011052050.0A5Ko7Jc005461(a)web01.xxxxxx.xxxx> doveadm(testtest): Info: expunge: box=test3, msgid=<202011052050.0A5Ko7Jc005461(a)web01.xxxxxx.xxxx> doveadm(testtest): Info: expunge: box=test3, msgid=<202011052050.0A5Ko7Jc005461(a)web01.xxxxxx.xxxx> Looks like the correct amount of messages are deleted [@ testtest]# du -s -k /home/popusers/testtest/mdbox/storage/ 135356 /home/popusers/testtest/mdbox/storage/ Lets check the expunged mail, again still everywhere 0 [@ testtest]# doveadm -o mail_location=mdbox_deleted:/home/popusers/testtest/mdbox:INDEX=/home/popindex/testtest/index mailbox status -u testtest 'messages vsize' '*' Sent messages=0 vsize=0 Drafts messages=0 vsize=0 INBOX/test2 messages=0 vsize=0 Junk messages=0 vsize=0 Trash messages=0 vsize=0 test3 messages=0 vsize=0 test1 messages=0 vsize=0 INBOX messages=0 vsize=0 This does not return any messages, so they were expunged. [@ testtest]# doveadm search -u testtest mailbox test3 subject 'delete me' How can I get the amount of messages expunged in the folders? I do not get it.

1 1

"younger" - filter on virtual INBOX
by Josef Haider 16 Mar '21

16 Mar '21

Hello, I think I have run into an issue which has been posted to this list in 2018 already: > Hello Rob, > > Do you by chance have a virtual/All folder which holds all your > messages? If so, could I see that configuration? > > Thanks. > Dave. > > > On 2/27/18, Rob Hoelz <rob+dovecot at hoelz.ro <https://dovecot.org/mailman/listinfo/dovecot>> wrote: > >/Hi list, />//>/I just encountered a problem while using dovecot's Virtual plugin with />/2.3.0. I managed to solve the issue, />/but I wanted to bring it to the attention of others on the list to > see if />/there exists a better solution, if />/I found a bug, or if it's just a matter of updating documentation. />//>/I have a virtual folder to get the most recent two weeks of mails; it > looks />/something like this: />//>>/INBOX />>/all younger 1209600 />//>/I made this folder back in October. Lately, I started to notice that the />/virtual folder had a surprising amount />/of mail in it - I don't get 1,000 e-mails per week! After some doveadm />/commands, I realized that e-mails from />/October were still present in my virtual folder! Updating the />/dovecot-virtual would clear away e-mails older than />/two weeks (I needed to actually introduce a change, even if it was just />/whitespace - just touching the file didn't />/update things), and removing the dovecot index file also cleared things />/away. In then end, I ended up just telling />/dovecot to disable on-disk indexes for that folder. />//>/I created this folder based on the examples on />/https://wiki.dovecot.org/Plugins/Virtual > <https://wiki.dovecot.org/Plugins/Virtual> - I'm wondering if I found > a bug />/or if that page should be changed to recommend disabling on-disk indexes />/when using certain search query filters such as />/"younger". If the latter, I can always make the change - just let me > know! />//>/-Rob /> Unfortunately, that thread died, so I'm trying my luck now... I am trying to have mail from several shared mailboxes show up in a user's INBOX if they are unread or younger than 24h, using the filter "or (unseen) (all younger 86400)". This works when forcing dovecot to regenerate index files, as mentioned above, by adding spaces to the virtual Inbox config file. Otherwise, mail older than 24h is not removed from the virtual INBOX. Any help would be greatly appreciated :) namespace configuration: namespace lists { list = children location = maildir:/var/mail/lists:CONTROL=~/Maildir/lists:INDEX=~/Maildir/lists prefix = lists. separator = . subscriptions = no type = public } namespace real { hidden = yes list = no location = prefix = RealMails. separator = . } namespace vimap { hidden = yes list = no location = virtual:/var/mail/virtual/vimap:INDEX=~/Maildir/vimap prefix = vimap. separator = . } /var/mail/virtual/vimap: !RealMails all lists.* or (unseen) (all younger 86400) dovecot version: # 2.3.4.1 (f79e8e7e4) # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-14-amd64 x86_64 Debian 10.8 -Joe

1 0

dovecot.map.index corrupted: Unexpectedly lost INBOX uid=1 map_uid=4726
by Marc 15 Mar '21

15 Mar '21

I had in my archive namespace[1] an INBOX folder and did not really get why it was there so I deleted it. Now this command generates map index error (doveadm force-resync does not fix it ;)) [@ ~]# doveadm -o namespace/4archives/location=mdbox_deleted:/home/mail-archive/testtest/mdbox/Archive -o mail_location=mdbox_deleted:/home/mail-archive/testtest/mdbox/Archive:INDEX=/home/archiveindex/testtest/index mailbox status -u testtest 'messages vsize' 'INBOX' doveadm(testtest): Error: mdbox map /home/archiveindex/testtest/index/storage/dovecot.map.index corrupted: Unexpectedly lost INBOX uid=1 map_uid=4726 doveadm(testtest): Error: Mailbox INBOX: Failed to lookup mailbox status: mdbox map /home/archiveindex/testtest/index/storage/dovecot.map.index corrupted: Unexpectedly lost INBOX uid=1 map_uid=4726 [1] namespace 4archives { disabled = no hidden = no ignore_on_failure = no inbox = no list = yes location = mdbox:/home/mail-archive/%u/Archive/:CONTROL=/home/mail-archive/%u/Archive/control:INDEX=/home/archiveindex/%u/index mailbox Archive { auto = create autoexpunge = 0 autoexpunge_max_mails = 0 comment = driver = special_use = \Archive } mailbox "Archived mail" { auto = no autoexpunge = 0 autoexpunge_max_mails = 0 comment = driver = special_use = \Archive } mailbox "Archived messages" { auto = no autoexpunge = 0 autoexpunge_max_mails = 0 comment = driver = special_use = \Archive } ... ... mailbox Archives { auto = no autoexpunge = 0 autoexpunge_max_mails = 0 comment = driver = special_use = \Archive } order = 0 prefix = Archive/ separator = / subscriptions = yes type = private }

1 1

how to reclaim disk space mdbox
by Marc 15 Mar '21

15 Mar '21

When I delete messages in the archive namespace they are copied to the deleted items folder in the inbox namespace. This is 34MB increase is visible however I expected the archive to go down by 34MB. Is diskspace reclaimed automatically or do you need to issue an command? [@ sbin]# du -s -k /home/popusers/testtest /home/mail-archive/testtest 135472 /home/popusers/testtest 358824 /home/mail-archive/testtest [@ sbin]# du -s -k /home/popusers/testtest /home/mail-archive/testtest 169368 /home/popusers/testtest 358824 /home/mail-archive/testtest PS. I have mdbox_rotate_size = 4 M

1 1

Doveadm-Purge dry run
by Marc 15 Mar '21

15 Mar '21

Maybe it is nice to introduce some option to Doveadm-Purge that does not delete anything just logs what it wanted to delete sort of like rsync's -n option.

1 0

archive namespace reports mdbox_deleted: same as mdbox: is that ok?
by Marc 15 Mar '21

15 Mar '21

These commands should generate different output not? [@ ~]# doveadm -o mail_location=mdbox_deleted:/home/mail-archive/testtest/mdbox:INDEX=/home/archiveindex/testtest/index mailbox status -u testtest 'messages vsize' "Archive/2018" Archive/2018 messages=70 vsize=6182960 [@ ~]# doveadm -o mail_location=mdbox:/home/mail-archive/testtest/mdbox:INDEX=/home/archiveindex/testtest/index mailbox status -u testtest 'messages vsize' "Archive/2018" Archive/2018 messages=70 vsize=6182960

2 13

Virtual users @ virtual domains / better documentation?
by justina colmena ~biz 15 Mar '21

15 Mar '21

I have configured postfix so it will deliver mail to virtual mailboxes. For some reason, the mail is not delivered to the virtual mailboxes unless both $virtual_alias_domains and $virtual_alias_maps are left undefined: these directives are apparently for aliasing virtual users "@" virtual domains to "real" unix users on the local system. --%%== # ADDRESS REDIRECTION (VIRTUAL DOMAIN) # # The VIRTUAL_README document gives information about the many forms # of domain hosting that Postfix supports. virtual_mailbox_domains = domain1.example.org domain2.example.com virtual_transport = virtual #virtual_alias_domains = domain1.example.org domain2.example.com virtual_mailbox_base = /var/mail/vhosts virtual_mailbox_maps = hash:/etc/postfix/vmailbox virtual_minimum_uid = 100 virtual_uid_maps = static:5000 virtual_gid_maps = static:5000 #virtual_alias_maps = hash:/etc/postfix/virtual ==%-- If the $virtual_alias_maps directive invalidates virtual mailboxes, then "the usual" aliases (postmaster@, etc.) for the virtual domains would have to be listed in /etc/aliases along with the non-virtual aliases, but this does not work either, and generates a warning when "newaliases" is run. postalias: warning: /etc/aliases, line 99: name must be local So as far as I can tell, no aliasing at all is available for "virtual_mailbox_domains" in postfix I am still unsure how to authenticate the virtual users on postfix. PAM authentication works fine for non-virtual users. The following command gives two options for authentication: cyrus-sasl and dovecot-sasl. # postconf -a cyrus dovecot Postfix also works with cyrus-sasl if the passwords are set in "/etc/sasldb2" via the "saslpasswd2" command, but dovecot doesn't seem to work with cyrus-sasl, and has its own type of sasl authentication. I realize this is not a postfix list, so my real question here is, What do I need in order for dovecot to authenticate the virtual users and allow them to read their mail and obtain authorization to send mail via postfix on the same system?

3 2

understanding refcount=0, where is my deleted message?
by Marc 14 Mar '21

14 Mar '21

I have migrated beginning this year from mbox to mdbox, but I am still struggling with the concept of refcount=0 and where these message stay. This is my test mailbox (shell script uses 'doveadm mailbox status -u') [@ sbin]# mailbox-ls.sh testtest size listing mailboxes of testtest: Archive msgs=0 vsize=0B Archive/2011 msgs=0 vsize=0B Archive/2012 msgs=0 vsize=0B Archive/2013 msgs=0 vsize=0B Archive/2014 msgs=0 vsize=0B Archive/2015 msgs=0 vsize=0B Archive/2016 msgs=0 vsize=0B Archive/2017 msgs=0 vsize=0B Archive/2018 msgs=0 vsize=0B Archive/2019 msgs=3435 vsize=277MiB Archive/Archive msgs=1 vsize=2.4KiB Deleted Messages msgs=0 vsize=0B Drafts msgs=4 vsize=1.1KiB INBOX msgs=1329 vsize=211MiB INBOX/test2 msgs=3 vsize=187KiB Junk msgs=2 vsize=2.0KiB Sent msgs=20 vsize=13KiB Trash msgs=47 vsize=752KiB [@ sbin]# doveadm -o mail_location=mdbox_deleted:/home/popusers/testtest/mdbox:INDEX=/home/popindex/testtest/index mailbox status -u testtest 'messages vsize' '*' Sent messages=0 vsize=0 Drafts messages=0 vsize=0 INBOX/test2 messages=0 vsize=0 Junk messages=0 vsize=0 Deleted Messages messages=0 vsize=0 Trash messages=0 vsize=0 INBOX messages=0 vsize=0 Now I am deleting 1 message from inbox with thunderbird, and I am getting this expected result, 1 message less in inbox, 1 message more in Deleted messages. [root@mail04 sbin]# mailbox-ls.sh testtest size listing mailboxes of testtest: Archive msgs=0 vsize=0B Archive/2011 msgs=0 vsize=0B Archive/2012 msgs=0 vsize=0B Archive/2013 msgs=0 vsize=0B Archive/2014 msgs=0 vsize=0B Archive/2015 msgs=0 vsize=0B Archive/2016 msgs=0 vsize=0B Archive/2017 msgs=0 vsize=0B Archive/2018 msgs=0 vsize=0B Archive/2019 msgs=3435 vsize=277MiB Archive/Archive msgs=1 vsize=2.4KiB Deleted Messages msgs=1 vsize=433B Drafts msgs=4 vsize=1.1KiB INBOX msgs=1328 vsize=211MiB INBOX/test2 msgs=3 vsize=187KiB Junk msgs=2 vsize=2.0KiB Sent msgs=20 vsize=13KiB Trash msgs=47 vsize=752KiB [@ sbin]# doveadm -o mail_location=mdbox_deleted:/home/popusers/testtest/mdbox:INDEX=/home/popindex/testtest/index mailbox status -u testtest 'messages vsize' '*' Sent messages=0 vsize=0 Drafts messages=0 vsize=0 INBOX/test2 messages=0 vsize=0 Junk messages=0 vsize=0 Deleted Messages messages=0 vsize=0 Trash messages=0 vsize=0 INBOX messages=0 vsize=0 Now I right click trash in thunderbird and choose empty trash, and I am getting this expected result, Deleted messages is empty. (Notice Trash stays at the same message count) [@ sbin]# mailbox-ls.sh testtest size listing mailboxes of testtest: Archive msgs=0 vsize=0B Archive/2011 msgs=0 vsize=0B Archive/2012 msgs=0 vsize=0B Archive/2013 msgs=0 vsize=0B Archive/2014 msgs=0 vsize=0B Archive/2015 msgs=0 vsize=0B Archive/2016 msgs=0 vsize=0B Archive/2017 msgs=0 vsize=0B Archive/2018 msgs=0 vsize=0B Archive/2019 msgs=3435 vsize=277MiB Archive/Archive msgs=1 vsize=2.4KiB Deleted Messages msgs=0 vsize=0B Drafts msgs=4 vsize=1.1KiB INBOX msgs=1328 vsize=211MiB INBOX/test2 msgs=3 vsize=187KiB Junk msgs=2 vsize=2.0KiB Sent msgs=20 vsize=13KiB Trash msgs=47 vsize=752KiB So this message should have refcount=0. But where is it, this still shows 0 messages everywhere? [@ sbin]# doveadm -o mail_location=mdbox_deleted:/home/popusers/testtest/mdbox:INDEX=/home/popindex/testtest/index mailbox status -u testtest 'messages vsize' '*' Sent messages=0 vsize=0 Drafts messages=0 vsize=0 INBOX/test2 messages=0 vsize=0 Junk messages=0 vsize=0 Deleted Messages messages=0 vsize=0 Trash messages=0 vsize=0 INBOX messages=0 vsize=0

1 0

Panic: file mdbox-map.c: line 1494 (mdbox_map_get_uid_validity): assertion failed: (map->view != NULL)
by Marc 12 Mar '21

12 Mar '21

Does this mean I have some problems with filesystem uid's? Currently I have only u=rwx, go is nothing. dovecot-2.2.36-6.el7_8.1.x86_64

3 8

auto scaling dovecot server on AWS
by girivasan.rajasekaran＠minfytech.com 10 Mar '21

10 Mar '21

Hello There - I'm trying to setup dovecot server on AWS and would like to understand the approach on the email server sizing? The emails are expected to surge at times seasonally. How do I plan the email server sizing to handle such load? Does this support auto-scaling? Probably I'm missing the basics. Appreciate your help in giving some clarity.

1 0

invalid vsize-hdr
by Christopher Wensink 10 Mar '21

10 Mar '21

Good afternoon everyone, I have one account on our internal dovecot server that keeps throwing the same repeated error: The user is on a Windows 10 computer running the latest version of Thunderbird. Here's the log: -------------------------------------------------------------------------------------------------------------------- Mar 9 13:03:16 mario2 dovecot: imap(pstrangfeld): Error: vsize-hdr has invalid size: 36 Mar 9 13:09:53 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:18:57 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:25:09 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:29:07 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:31:03 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:37:20 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:42:26 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:47:21 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:50:11 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:53:46 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:59:40 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:03:52 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:08:54 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:11:53 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:17:02 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:21:14 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:24:00 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:28:43 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:33:00 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:38:24 mario2 dovecot: imap(user): Connection closed (IDLE running for 0.001 + waiting input for 0.001 secs, 2 B in + 10+10 B out, state=wait-input) in=1578244 out=2878370 Mar 9 14:40:51 mario2 dovecot: imap-login: Login: user=<user>, method=PLAIN, rip=10.5.1.77, lip=10.5.1.17, mpid=97537, TLS, session=<AvLvkCC9w9kKBQFN> Mar 9 14:41:30 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:44:14 mario2 dovecot: imap(user): Connection closed (IDLE running for 0.002 + waiting input for 0.001 secs, 2 B in + 10+10 B out, state=wait-input) in=319541 out=1272761 Mar 9 14:44:14 mario2 dovecot: imap-login: Login: user=<user>, method=PLAIN, rip=10.5.1.77, lip=10.5.1.17, mpid=97671, TLS, session=<85YInSC95NkKBQFN> Mar 9 14:46:37 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 --------------------------------------------------------------- I have tried the following: -Restarting the workstation - Compacting folders in Thunderbird - Repaired the Inbox Folder in Thunderbird - Restarting the dovecot service - Set the connections in Thunderbird Account settings to not check for messages automatically (manual only) - Set the user to own all folders and sub-folders in his home directory on the server I found old message in the archives from 2017 that had the same error but I did not see a posted solution. dovecot --version 2.2.36 (lfl0bfa63) config file: [root@mario2 dovecot]# cat dovecot.conf ## Dovecot configuration file # If you're in a hurry, see http://wiki2.dovecot.org/QuickConfiguration # "doveconf -n" command gives a clean output of the changed settings. Use it # instead of copy&pasting files when posting to the Dovecot mailing list. # '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace " # Most (but not all) settings can be overridden by different protocols and/or # source/destination IPs by placing the settings inside sections, for example: # protocol imap { }, local 127.0.0.1 { }, remote 10.0.0.0/8 { } # Default values are shown for each setting, it's not required to uncomment # those. These are exceptions to this though: No sections (e.g. namespace {}) # or plugin settings are added by default, they're listed only as examples. # Paths are also just examples with the real defaults being based on configure # options. The paths listed here are for configure --prefix=/usr # --sysconfdir=/etc --localstatedir=/var # Protocols we want to be serving. #protocols = imap pop3 lmtp protocols = imap pop3 # A comma separated list of IPs or hosts where to listen in for connections. # "*" listens in all IPv4 interfaces, "::" listens in all IPv6 interfaces. # If you want to specify non-default ports or anything more complex, # edit conf.d/master.conf. #listen = *, :: listen = *, :: # Base directory where to store runtime data. #base_dir = /var/run/dovecot/ # Name of this instance. In multi-instance setup doveadm and other commands # can use -i <instance_name> to select which instance is used (an alternative # to -c <config_path>). The instance name is also added to Dovecot processes # in ps output. #instance_name = dovecot # Greeting message for clients. #login_greeting = Dovecot ready. # Space separated list of trusted network ranges. Connections from these # IPs are allowed to override their IP addresses and ports (for logging and # for authentication checks). disable_plaintext_auth is also ignored for # these networks. Typically you'd specify your IMAP proxy servers here. #login_trusted_networks = login_trusted_networks = 10.5.1.0/24 # Space separated list of login access check sockets (e.g. tcpwrap) #login_access_sockets = # With proxy_maybe=yes if proxy destination matches any of these IPs, don't do # proxying. This isn't necessary normally, but may be useful if the destination # IP is e.g. a load balancer's IP. #auth_proxy_self = # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). #verbose_proctitle = no # Should all processes be killed when Dovecot master process shuts down. # Setting this to "no" means that Dovecot can be upgraded without # forcing existing client connections to close (although that could also be # a problem if the upgrade is e.g. because of a security fix). #shutdown_clients = yes # If non-zero, run mail commands via this many connections to doveadm server, # instead of running them directly in the same process. #doveadm_worker_count = 0 # UNIX socket or host:port used for connecting to doveadm server #doveadm_socket_path = doveadm-server # Space separated list of environment variables that are preserved on Dovecot # startup and passed down to all of its child processes. You can also give # key=value pairs to always set specific settings. #import_environment = TZ ## ## Dictionary server settings ## # Dictionary can be used to store key=value lists. This is used by several # plugins. The dictionary can be accessed either directly or though a # dictionary server. The following dict block maps dictionary names to URIs # when the server is used. These can then be referenced using URIs in format # "proxy::<name>". dict { #quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext #expire = sqlite:/etc/dovecot/dovecot-dict-sql.conf.ext } # Most of the actual configuration gets included below. The filenames are # first sorted by their ASCII value and parsed in that order. The 00-prefixes # in filenames are intended to make it easier to understand the ordering. !include conf.d/*.conf # A config file can also tried to be included without giving an error if # it's not found: !include_try local.conf ----------- I need assistance. I appreciate the help. Chris -- Christopher Wensink IS Administrator Five Star Plastics, Inc 1339 Continental Drive Eau Claire, WI 54701 Office: 715-831-1682 Mobile: 715-563-3112 Fax: 715-831-6075 cwensink(a)five-star-plastics.com www.five-star-plastics.com

6 6

DMARC problems with some emails from the list
by Ángel L. Mateo 09 Mar '21

09 Mar '21

Hello, I'm having problems with some emails from the list, been classified as SPAM in my system because of DMARC failures. I'm not sure but this may be a problem with the list configuration. I attach the log for the failures in the last week. -- 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

3 8

Dovecot v2.3.14 released
by Aki Tuomi 09 Mar '21

09 Mar '21

Hi! We are pleased to release v2.3.14 of Dovecot. IMPORTANT NOTE: We have removed some components from the software, please review changelogs carefully prior upgrading. Please find source tarballs at https://dovecot.org/releases/2.3/dovecot-2.3.14.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.14.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Aki Tuomi Open-Xchange oy --- * Added new aliases for some variables. Usage of the old ones is possible, but discouraged. (These were partially added already to v2.3.13.) See https://doc.dovecot.org/configuration_manual/config_file/config_variables/ for more information. * Optimize imap/pop3/submission/managesieve proxies to use less CPU at the cost of extra memory usage. * Remove autocreate, expire, snarf and mail-filter plugins. * Remove cydir storage driver. * Remove XZ/LZMA write support. Read support will be removed in future release. * doveadm -D: Add timestamps to debug output even when LOG_STDERR_TIMESTAMP environment variable is not set. Timestamp format is taken from log_timestamp setting. * If BROKENCHAR or listescape plugin is used, the escaped folder names may be slightly different from before in some situations. This is unlikely to cause issues, although caching clients may redownload the folders. * imapc: It now enables BROKENCHAR=~ by default to escape remote folder names if necessary. This also means that if there are any '~' characters in the remote folder names, they will be visible as "~7e". * imapc: When using local index files folder names were escaped on filesystem a bit differently. This affects only if there are folder names that actually require escaping, which isn't so common. The old style folders will be automatically deleted from filesystem. * stats: Update exported metrics to be compliant with OpenMetrics standard. + doveadm: Add an optional '-p' parameter to metadata list command. If enabled, "/private", and "/shared" metadata prefixes will be prepended to the keys in the list output. + doveconf: Support environment variables in config files. See https://doc.dovecot.org/configuration_manual/config_file/config_file_syntax… for more details. + indexer-worker: Change indexer to disconnect from indexer-worker after each request. This allows service indexer-worker's service_count & idle_kill settings to work. These can be used to restart indexer-worker processes once in a while to reduce their memory usage. - auth: "nodelay" with various authentication mechanisms such as apop and digest-md5 crashed AUTH process if authentication failed. - auth: Auth lua script generating an error triggered an assertion failure: Panic: file db-lua.c: line 630 (auth_lua_call_password_verify): assertion failed: (lua_gettop(script->L) == 0). - configure: Fix libunwind detection to work on other than x86_64 systems. - doveadm-server: Process could crash if logging was done outside command handling. For example http-client could have done debug logging afterwards, resulting in either segfault or Panic: file http-client.c: line 642 (http_client_context_close): assertion failed: (cctx->clients_list == NULL). - dsync: Folder name escaping with BROKENCHAR didn't work completely correctly. This especially caused problems with dsync-migrations using imapc where some of the remote folder names may not have been accessible. - dsync: doveadm sync + imapc doesn't always sync all mails when doing an incremental sync (-1), which could lead to mail loss when it's used for migration. This happens only when GUIDs aren't used (i.e. imapc without imapc_features=guid-forced). - fts-tika: When tika server returns error, some mails cause Panic: file message-parser.c: line 802 (message_parser_deinit_from_parts): assertion failed: (ctx->nested_parts_count == 0 || i_stream_have_bytes_left(ctx->input)) - lib-imap: imapc parsing illegal BODYSTRUCTUREs with NILs could have resulted in crashes. This exposed that Dovecot was wrongly accepting atoms in "nstring" handling. Changed the IMAP parsing to be more strict about this now. - lib-index: If dovecot.index.cache has corrupted message size, fetching BODY/BODYSTRUCTURE may cause assert-crash: Panic: file index-mail.c: line 1140 (index_mail_parse_body_finish): assertion failed: (mail->data.parts != NULL). - lib-index: Minor error handling and race condition fixes related to rotating dovecot.index.log. These didn't usually cause problems, unless the log files were rotated rapidly. - lib-lua: Lua scripts using coroutines or lua libraries using coroutines (e.g., cqueues) panicked. - Message PREVIEW handled whitespace wrong so first space would get eaten from between words. - FTS and message PREVIEW (snippet) parsed HTML &entities case-sensitively. - lib-mail: When max nested MIME parts were reached, IMAP BODYSTRUCTURE was written in a way that may have caused confusion for IMAP clients and also Dovecot itself when parsing it. The truncated part is now written out using application/octet-stream MIME type. - lib-oauth2: HS512 and HS384 JWT token algorithms crash when you try to use them: Panic: file hmac.c: line 26 (hmac_init): assertion failed: (meth->context_size <= MAC_MAX_CONTEXT_SIZE). - event filters: NOT keyword did not have the correct associativity. NOT a AND b were getting parsed as NOT (a AND b) instead of (NOT a) AND b. - Ignore ECONNRESET when closing socket. This avoids logging useless errors on systems like FreeBSD. - event filters: event filter syntax error may lead to Panic: file event-filter.c: line 137 (event_filter_parse): assertion failed: (state.output == NULL) - lib: timeval_cmp_margin() was broken on 32-bit systems. This could potentially have caused HTTP timeouts to be handled incorrectly. - log: instance_name wasn't used as syslog ident by the log process. - master: After a service reached process_limit and client_limit, it could have taken up to 1 second to realize that more client connections became available. During this time client connections could have been unnecessarily rejected and a warning logged: Warning: service(...): process_limit (...) reached, client connections are being dropped - stats: Crash would occur when generating openmetrics data for metrics using aggregating functions. - stats: Event filters comparing against empty strings crash the stats process.

5 5

start dovecot multiple instances
by Gonzalo Palacios Goicolea 08 Mar '21

08 Mar '21

Hi All, I'm trying to run dovecot with dovecot-director on the same server, using two different instances, but I'n not able to make the two instances start with systemctl (we are using RHEL7) May be I shueld create a /etc/systemd/system/dovecot.service.d/service.conf file and add there any command? Thanks and best regards -- *Gonzalo Palacios Goicolea* U.T de Infraestructura de Equipos Centrales /Tecnologías de la Información/ Universidad Autónoma de Madrid • Campus de Cantoblanco

2 1

director implementation
by Gonzalo Palacios Goicolea 08 Mar '21

08 Mar '21

Hi All, We're going to put into production dovecot-director. As I wrote in a previous message, we have a lot of errors like these: Feb 28 08:50:42 server5 dovecot: imap(user@domain): Error: Index path/Maildir/dovecot.index: Lost log for seq=5 offset=228: Missing middle file seq=5 (between 5..4294967295, we have seqs 4): Log is locked - newer log can't exist (initial_mapped=1, reason=Index mapped) Feb 28 08:50:42 server5 dovecot: imap(user@domain): Warning: fscking index file path/Maildir/dovecot.index Feb 28 08:50:42 server5 dovecot: imap(user@domain): Error: Failed to map transaction log path/Maildir/dovecot.index.log at sync_offset=10328 after locking: pread() failed: Stale file handle Feb 28 08:50:42 server5 dovecot: imap(user@domain): Error: Index path/Maildir/dovecot.index: Lost log for seq=5 offset=228: Missing middle file seq=5 (between 5..4294967295, we have seqs 4): Requested newer log than exists - still after NFS flush: Log inode is unchanged (initial_mapped=1, reason=Index mapped) Feb 28 08:50:45 server5 dovecot: imap(user@domain): Error: Failed to map transaction log path/Maildir/dovecot.index.log at sync_offset=10328 after locking: pread() failed: Stale file handle Feb 28 08:50:45 server5 dovecot: imap(user@domain): Error: Failed to map view for path/Maildir/dovecot.index: Missing middle file seq=5 (between 5..5, we have seqs 4): Requested newer log than exists - still after NFS flush: Log inode is unchanged My doubt is if it's recommended to delete all dovecot.index* files before passing the traffic through de director servers or it's not required. Any information on this way will be appreciated. We've dovecot-2.2.36-8.el7.x86_64 over RHEL7 Thanks and best regards -- *Gonzalo Palacios Goicolea* U.T de Infraestructura de Equipos Centrales /Tecnologías de la Información/ Universidad Autónoma de Madrid • Campus de Cantoblanco <3D"http://www.uam.es/"> Antes de imprimir este correo piense si es necesario.Cuidemos el medioambiente.

2 1

not getting internal errors logged
by Arkadiusz Miśkiewicz 08 Mar '21

08 Mar '21

Hello. dovecot 2.3.13, 2.3.14 web imap client when doing search is getting error induced by me by deleting lucene-indexes folder: UID SEARCH: Internal error occurred. Refer to server log for more information. [2021-03-08 15:08:01] (0.002 + 0.000 + 0.001 secs). but I'm not getting that internal error logged in syslog. Other information like from lmtp, imap logging in, out etc is logged just fine. In my configs log_path info_log_path debug_log_path are not set, so dovecot default syslog is used. Tested log_path = /tmp/file.txt, too but the effect was the same (regular logs logged there, internal errors not logged) stracing dovecot process I see error message only write()n once (to client) but nowhere else (in a strace visible way). Is anything else controlling internal errors logging? Can't find anything in docs. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

1 0

Mailbox configuration questions
by justina colmena ~biz 08 Mar '21

08 Mar '21

I am having subtle problems with IMAP mailbox configuration on certain clients such as KMail and Thunderbird, whereas the previous setup was working on K9Mail (mobile) and Trojitá (desktop). I was using Maildir folders, which were mostly working before, but for some reason I had to create explicitly named namespaces for the flatfile (mbox) Inbox and the Maildir "Home" folders. I also specified an INDEX directory for the inboxes, which I made world-writable and sticky, because of permission problems creating subdirectories in it. KMail always seems to put sent mail into a local "sent-mail" folder, rather than the IMAP Sent folder associated with the sending account. (KMail and Thunderbird have a more POP-oriented architecture for the desktop, whereas Trojitá is exclusively IMAP.) Is there an easier better way to organize some of this stuff? Or how is it "usually" done?

3 2

Re: Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)
by Roland Martinez 05 Mar '21

05 Mar '21

1 0

Where can I contact with this list administrator?
by Ángel L. Mateo 05 Mar '21

05 Mar '21

Hi, I'm having problems with some emails receive from this list. Problems related with DMARC. How can I contact with this list administrator to try to fix it? -- 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

3 2

last login plugins
by Henry 05 Mar '21

05 Mar '21

Anyone kwon the last-login plugins can using Authentication variables such as %m mechanism, %a local_port . we want to record this in DB, thanks

3 21

About TLS variables
by Henry 04 Mar '21

04 Mar '21

Hello, I found the Variable %c only has TLS, Can it be using "TLSv1, TLSv1.1, TLSv1.2, TLSv1.3" instead of only TLS like as dovecot logging, this is really a most meaningful , thanks Variable %cLong name securedDescription “TLS” with established SSL/TLS connections, “TLS handshaking”, or “TLS [handshaking]: error text” if disconnecting due to TLS error. “secured” with localhost connections. Otherwise empty.

2 2