- dovecot - dovecot.org

Sharing or not sharing the INBOX
by Stephane Magnier 13 Aug '21

13 Aug '21

Hi, I am using Dovecot and Sendmail ( as lmtp server ) I would like to consider having some users using there emails and having their "private Ibox" ( I would say as a normal use ) and some users sharing their Inbox 1) Should I consider using and configure 2 different email servers ? ( one sharing the inbox of any users, the other one, not sharing the inbox...) or I can have this config with the same email server ? 2) if so, how to tell Dovecot to get for user1 and user2 the same Inbox and (user3 and user4) Not sharing their inbox ? - ... like private emails and a tech support, which should share the same folder 3) or Can I say : User1 -> User 4 have private emails Inbox.. but user3 and user4 are also sharing the same folder /var/spool/mail/support/ for example I should admit that I don't know where to go :-( Thanks for your help

1 1

dovecot 2.3.16 fail one test on s390x, alpine linux
by Milan P. Stanić 13 Aug '21

13 Aug '21

Hi, I'm trying to upgrade dovecot from version 2.3.15 to 2.3.16 for alpine linux. Build and 'make check' pass on all alpine architectures except on s390x which is big-endian while all other are little-endian. here is the part from CI build log which fails: ------------ mail cache size corruption ........................................... : ok 0 / 10 tests failed test-mail-cache-fields.c:50: Assert failed: cache_field.last_used == priv->field.last_used && cache_field.decision == priv->field.decision test-mail-cache-fields.c:65: Assert failed: cache_field.last_used == priv->field.last_used && cache_field.decision == priv->field.decision test-mail-cache-fields.c:94: Assert failed: cache_field.last_used == priv->field.last_used && cache_field.decision == priv->field.decision mail cache fields read-write ......................................... : FAILED 1 / 1 tests failed make[3]: *** [Makefile:1279: check-local] Error 1 make[3]: Leaving directory '/builds/alpine/aports/main/dovecot/src/dovecot-2.3.16/src/lib-index' make[2]: *** [Makefile:1049: check-am] Error 2 make[2]: Target 'check' not remade because of errors. make[2]: Leaving directory '/builds/alpine/aports/main/dovecot/src/dovecot-2.3.16/src/lib-index' Making check in lib-storage ------------ Full log is here: https://gitlab.alpinelinux.org/alpine/aports/-/jobs/459182/raw -- Kind regards

3 8

Dovecot (>= 2.3.15) is not properly replicating Expunge commands running in a containerised environment
by A. Schulze 12 Aug '21

12 Aug '21

Hello *, migrating a mailbox setup for several tens of thousands of customers to Docker containers running on Debian VMs, we are currently observing Expunge commands not being replicated properly between two Dovecot containers. Delivering a new message into someones' inbox is replicated instantly via dsync (using TLS). However, expunging a message from the very same inbox via > doveadm expunge -u [users' email address] mailbox '*' header Message-ID [MID of the message in question] is not replicated, since a > doveadm fetch -u [users' email address] text header Message-ID [MID of the message in question] still returns the mail on the replica. Sometimes, a > doveadm replicator replicate [users' email address] fixes this, but mostly, it does not. While doing all of this, these messages are logged by Dovecot: > doveadm: Info: copy from INBOX: box=INBOX, uid=13, msgid=<[MID of the message in question]>, size=1793 > doveadm: Info: expunge: box=INBOX, uid=12, msgid=<[MID of the message in question]>, size=1793 > doveadm: Error: dsync(x): I/O has stalled, no activity for 600 seconds (last sent=handshake, last recv=handshake) > doveadm: Error: Timeout during state=slave_recv_last_common > doveadm: Error: dsync(x): I/O has stalled, no activity for 600 seconds (last sent=mailbox_delete, last recv=mailbox_delete) > doveadm: Error: Timeout during state=slave_recv_mailbox > doveadm: Error: dsync(SSL x): I/O has stalled, no activity for 600 seconds (version not received) > doveadm: Error: Timeout during state=slave_recv_handshake Unfortunately, these errors do not seem to be reproducible very well - the underlying behaviour however is. Setting > replication_sync_timeout = 2s , as mentioned in https://doc.dovecot.org/settings/plugin/replication-plugin/ (the "s" seems to be bogus, though, as Dovecot complains about an invalid timeframe given) results in these messages: > doveadm(x): Error: doveadm client disconnected before handshake: Connection closed > replicator: Panic: data stack: Out of memory when allocating 268435496 bytes > replicator: Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(backtrace_append+0x3d) [0x7ff8f55343dd] -> /usr/local/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7ff8f55344fe] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xfcc6b) [0x7ff8f5540c6b] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xfcd01) [0x7ff8f5540d01] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x533e7) [0x7ff8f54973e7] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x52dcb) [0x7ff8f5496dcb] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xf6625) [0x7ff8f553a625] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x11c248) [0x7ff8f5560248] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xf2655) [0x7ff8f5536655] -> /usr/local/lib/dovecot/libdovecot.so.0(buffer_write+0x67) [0x7ff8f5536867] -> dovecot/replicator(replicator_queue_push+0xe9) [0x5619b1b81a39] -> dovecot/replicator(+0x61f8) [0x5619b1b811f8] -> dovecot/replicator(+0x58ef) [0x5619b1b808ef] -> dovecot/replicator(+0x5ab2) [0x5619b1b80ab2] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7ff8f5556b99] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x131) [0x7ff8f5558101] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7ff8f5556c3c] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7ff8f5556db0] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7ff8f54cb7b3] -> dovecot/replicator(main+0x18f) [0x5619b1b7fc4f] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7ff8f52a309b] -> dovecot/replicator(_start+0x2a) [0x5619b1b7fd0a] > replicator: Fatal: master: service(replicator): child 175 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set /proc/sys/fs/suid_dumpable to 2) Not having observed this behaviour on physical or virtual Linux machines, we are pretty much out of ideas on what to do. https://dovecot.org/pipermail/dovecot/2019-November/117467.html sounds like being a related issue. Thank you in advance for any hints and replies. root@x:/# doveconf -n # 2.3.15 (0503334ab1): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.15 (e6a84e31) # OS: Linux 4.9.0-16-amd64 x86_64 Debian 10.10 # Hostname: x auth_cache_negative_ttl = 1 mins auth_cache_size = 10 k auth_master_user_separator = "#" auth_mechanisms = plain login auth_verbose_passwords = sha1 doveadm_password = # hidden, use -P to show it doveadm_port = 12345 first_valid_uid = 8 imap_hibernate_timeout = 1 mins imap_id_log = * lmtp_save_to_detail_mailbox = yes log_path = /dev/stderr log_timestamp = login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c session=<%{session}> %k mail_access_groups = dovecot mail_attribute_dict = file:%h/Maildir/dovecot-attributes mail_gid = mail mail_location = maildir:~/Maildir/ mail_plugins = acl quota mail_log notify replication mail_uid = 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 vacation-seconds passdb { args = /etc/dovecot/conf.d/ldap-searches/ldap.conf driver = ldap } plugin { acl = vfile acl_defaults_from_inbox = yes acl_shared_dict = file:/data/acl_shared_dict/acl_shared_dict mail_replica = tcps:x sieve_extensions = +vacation-seconds sieve_vacation_min_period = 1m } pop3_uidl_format = %f postmaster_address = x protocols = imap lmtp pop3 sieve replication_dsync_parameters = -d -N -l 60 -U service aggregator { fifo_listener replication-notify-fifo { group = mail mode = 0666 user = mail } unix_listener replication-notify { group = mail mode = 0666 user = mail } } service auth-worker { user = $default_internal_user } service auth { unix_listener /socket/dovecot/x/sasl-server { group = postfix mode = 0660 user = postfix } } service doveadm { inet_listener { port = 12345 ssl = yes } } service imap-hibernate { unix_listener imap-hibernate { user = mail } } service imap { unix_listener imap-master { group = dovecot mode = 0660 } } service lmtp { inet_listener { port = 24 ssl = yes } unix_listener /socket/dovecot/x/lmtp-server { mode = 0600 user = postfix } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { group = mail mode = 0600 user = mail } } ssl_cert = </acme/live/x/cert+intermediate.pem ssl_cipher_list = ECDHE+AESGCM:ECDHE+CHACHA20 ssl_client_ca_dir = /etc/ssl/certs/ ssl_client_cert = </acme/live/x/cert+intermediate.pem ssl_client_key = # hidden, use -P to show it ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_options = no_ticket ssl_prefer_server_ciphers = yes userdb { driver = prefetch } userdb { args = /etc/dovecot/conf.d/ldap-searches/ldap.conf driver = ldap } userdb { args = /etc/dovecot/conf.d/ldap-searches/ldap-catchall.conf driver = ldap } verbose_proctitle = yes protocol imap { imap_metadata = yes mail_plugins = acl quota mail_log notify replication fts fts_squat imap_acl imap_quota mail_log notify } protocol lmtp { mail_plugins = acl quota mail_log notify replication sieve notify mail_log ssl = required ssl_ca = </etc/ssl/certs/ca-certificates.crt ssl_min_protocol = TLSv1.3 ssl_verify_client_cert = yes }

1 1

Panic: lib-sql: Too many bind args
by Joseph D Wagner 12 Aug '21

12 Aug '21

From /etc/dovecot/dovecot.conf: mail_attribute_dict = proxy::attr dict { attr = pgsql:/etc/dovecot/dovecot-attr-sql.conf.ext } From /etc/dovecot/dovecot-attr-sql.conf.ext: map { pattern = $key table = attributes fields { attr_name = $key } username_field = username value_field = attr_value } From /var/log/maillog: dovecot[51153]: dict(51395): Panic: lib-sql: Too many bind args (2) for statement: SELECT attr_name FROM attributes WHERE attr_name LIKE AND username = ? dovecot[51153]: dict(51395): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xf8cab) [0x7f4c92274cab] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf8d47) [0x7f4c92274d47] -> /usr/lib64/dovecot/libdovecot.so.0(+0x55c1d) [0x7f4c921d1c1d] -> dovecot/dict(+0x649a) [0x55921892349a] -> dovecot/dict(sql_statement_query+0x3e) [0x55921892a14e] -> dovecot/dict(+0xa296) [0x559218927296] -> /usr/lib64/dovecot/libdovecot.so.0(dict_iterate+0x23) [0x7f4c92238a23] -> dovecot/dict(+0x7860) [0x559218924860] -> dovecot/dict(+0x808c) [0x55921892508c] -> dovecot/dict(+0x8200) [0x559218925200] -> dovecot/dict(dict_command_input+0xee) [0x55921892534e] -> dovecot/dict(+0x6b9b) [0x559218923b9b] -> /usr/lib64/dovecot/libdovecot.so.0(connection_input_default+0x1b2) [0x7f4c9226fd42] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x73) [0x7f4c9228c413] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x135) [0x7f4c9228dac5] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x50) [0x7f4c9228c4c0] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x48) [0x7f4c9228c628] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x17) [0x7f4c92203fd7] -> dovecot/dict(main+0x185) [0x559218923895] -> /lib64/libc.so.6(__libc_start_main+0xf3) [0x7f4c91dda493] -> dovecot/dict(_start+0x2e) [0x5592189238ee] Joseph D Wagner

2 3

ACL's using SQL Backend
by Joseph D Wagner 11 Aug '21

11 Aug '21

I don't want to use vfile as the acl backend. I want to use sql, but it seems to be sparsely documented. Would this work? create table acls ( acl_name varchar(255) not null, username varchar(320) not null default '', acl_value varchar not null, constraint acls_pk primary key (acl_name, username) ); map { pattern = $key table = acls fields { acl_name = $key } username_field = username value_field = acl_value } Thanks. Joseph D. Wagner

1 0

Get Director vhostCount
by William Edwards 11 Aug '21

11 Aug '21

Hi, I would like to monitor each mail server's amount of available vhosts, so I can take action when a certain threshold is reached (e.g. adding mail servers). I'm using Dovecot 2.3.4.1 with Director. My first idea was to use the Doveadm HTTP API, but the 'directorStatus' command doesn't return the 'vhostCount' attribute (although the 'directorAdd' and 'directorUpdate' commands take it as input). My second idea was to directly connect to the 'director-admin' socket and look at the output of 'HOST-LIST'. I can find all the information I need in doveadm-connection.c, but I'm not getting the impression that we're meant to interact with the socket directly. I can't find protocol documentation, and the error message "doveadm not compatible with this server (mixed old and new binaries?)" when passing faulty input gives me the impression that the socket is only meant to be used by Dovecot directly. My third idea is to parse 'doveadm director status', but in that case I'd like to know if that output is likely to change in the future. New major versions aside, of course. Or, if anyone else has a better idea, which could very well be the case, I'd love to hear how people monitor this in the real world. TIA. -- With kind regards, William Edwards

1 1

JWT local validation
by Tomas Habarta 11 Aug '21

11 Aug '21

Hello, I have a working setup with Roundcube using OAuth2 -- introspection works without any problem, unfortunately local validation does not as tokens are missing "typ" header (seems that one is indeed optional per RFC7519 and therefore not present in the implementation in place). Is there any parameter to assert the token type or any other workaround to make local validation work as it currently fails with: oauth2 failed: Local validation failed: Cannot find 'typ' field. dovecot v2.3.15 Roundcube 1.5beta CentOS 8 Thanks, regards Tomas

2 3

Test for implicit keep within a sieve script
by Eric Durand 11 Aug '21

11 Aug '21

Hi folks, Is there a good way to test for an implicit keep in a sieve script ? At the end of my sieve script, if a message still has an implicit keep, it will end up in my inbox, and I would like to push a notification. Right now I am doing this with an ad-hoc variable that is essentially emulating the implicit keep, is there a better way to do this ? Thanks! Eric

2 1

pigeonhole-0.5.16 compilation error?
by Sylvain Robitaille 11 Aug '21

11 Aug '21

Hello Dovecot folks ... In response to the recent announcement of Dovecot-2.3.16 and pigeonhole-0.5.16, we decided to update our installation (full disclosure: this is really an update from dovecot-1.2.x in progress; we're working on a development system where we already had dovecot-2.3.x installed and running). The update of dovecot itself (compiled from source), to version 2.3.16 was quite uneventful, and I can report that it's working. We're seeing some behaviour with indexing that will need attention, but I suspect that that's a matter of configuration, and is completely unrelated to what I'm reporting. More disclosure: we've never used nor compiled pigeonhole on our systems before. We've been using procmail for decades, but are now looking into potentially switching to sieve, and as I understand it, that means installing pigeonhole. I downloaded dovecot-2.3-pigeonhole-0.5.16 at the same time that I downloaded dovecot-2.3.16, a few days ago. My build-time configure and make for pigeonhole is relatively simple, but fails to build: ./configure --prefix=/local/pkg/pigeonhole-0.5.16/root \ --sbindir=/local/pkg/pigeonhole-0.5.16/root/bin \ --localstatedir=/var \ --mandir=/local/pkg/pigeonhole-0.5.16/root/man \ --with-dovecot=/local/pkg/dovecot-CURRENT/root/lib/dovecot make -j2 "/local/pkg/dovecot-CURRENT/root/lib/dovecot" is correct for us, if I understand the installation instructions correctly: -rw-r--r-- 1 root root 1324 Aug 3 14:03 /local/pkg/dovecot-CURRENT/root/lib/dovecot/dovecot-config The make fails, while compiling sieve-extprograms-common.c: sieve-extprograms-common.c: In function ‘sieve_extprogram_run’: sieve-extprograms-common.c:639:7: error: ‘PROGRAM_CLIENT_EXIT_STATUS_INTERNAL_FAILURE’ undeclared (first use in this function) case PROGRAM_CLIENT_EXIT_STATUS_INTERNAL_FAILURE: ^ sieve-extprograms-common.c:639:7: note: each undeclared identifier is reported only once for each function it appears in sieve-extprograms-common.c:641:7: error: ‘PROGRAM_CLIENT_EXIT_STATUS_FAILURE’ undeclared (first use in this function) case PROGRAM_CLIENT_EXIT_STATUS_FAILURE: ^ sieve-extprograms-common.c:643:7: error: ‘PROGRAM_CLIENT_EXIT_STATUS_SUCCESS’ undeclared (first use in this function) case PROGRAM_CLIENT_EXIT_STATUS_SUCCESS: ^ I decided to check against dovecot-2.3-pigeonhole-0.5.15, figuring that problems compiling that version likely would have been reported already, and sure enough I find the following difference in this file: --- ./dovecot-2.3-pigeonhole-0.5.15/src/plugins/sieve-extprograms/sieve-extprograms-common.c 2021-06-14 09:41:29.000000000 -0400 +++ ./dovecot-2.3-pigeonhole-0.5.16/src/plugins/sieve-extprograms/sieve-extprograms-common.c 2021-08-06 05:26:46.000000000 -0400 @@ -635,6 +635,14 @@ int sieve_extprogram_set_input_mail int sieve_extprogram_run(struct sieve_extprogram *sprog) { - return program_client_run(sprog->program_client); + switch (program_client_run(sprog->program_client)) { + case PROGRAM_CLIENT_EXIT_STATUS_INTERNAL_FAILURE: + return -1; + case PROGRAM_CLIENT_EXIT_STATUS_FAILURE: + return 0; + case PROGRAM_CLIENT_EXIT_STATUS_SUCCESS: + return 1; + } + i_unreached(); } ... and no mention of these PROGRAM_CLIENT_EXIT_STATUS_* constants anywhere else in the code, in either version. Have I stumbled onto an omission in the packaged sources, or is there some other package missing on my system, or is there perhaps even some other explanation for what I'm seeing? I've checked the mailing list archive and found no mention of anyone else having the same (or similar) problem, so I do think it's possible that I'm just missing something ... Thanks in advance for any insight folks might be able to give me ... -- ---------------------------------------------------------------------- Sylvain Robitaille syl(a)encs.concordia.ca Systems analyst / AITS Concordia University Faculty of Engineering and Computer Science Montreal, Quebec, Canada ----------------------------------------------------------------------

1 1

GSSAPI mail home mapping problem
by Lucas Castro 10 Aug '21

10 Aug '21

Hello, I'm trying to map authenticated kerberos users to mail_location, The problem when I set mail_home = /var/mail/virtual/domain1.zw.loca/%n works fine. But if mail_home is set as /var/mail/virtual/%d/%n I get Apr 12 19:53:18 postfix10 dovecot: imap-login: Login: user=<user0>, method=GSSAPI, rip=172.16.0.44, lip=10.16.0.220, mpid=2428, session=<iPA4Yc6/lJCsEAAs> Apr 12 19:53:18 postfix10 dovecot: imap(user0(a)domain1.zw.local =login_user=user0)<2428><iPA4Yc6/lJCsEAAs>: Debug: Added userdb setting: plugin/=yes Apr 12 19:53:18 postfix10 dovecot: imap(user0(a)domain1.zw.local =login_user=user0)<2428><iPA4Yc6/lJCsEAAs>: Debug: Effective uid=5000, gid=5000, home=/var/mail/virtual/domain1.zw.local =login_user=user0/user0 Right here, I can't figure out why login_user=user0/user0 Apr 12 19:53:18 postfix10 dovecot: imap(user0(a)domain1.zw.local =login_user=user0)<2428><iPA4Yc6/lJCsEAAs>: Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/mail Now login_user=user0 Apr 12 19:53:18 postfix10 dovecot: imap(user0(a)domain1.zw.local =login_user=user0)<2428><iPA4Yc6/lJCsEAAs>: Debug: maildir++: root=/var/mail/virtual/domain1.zw.local =login_user=user0/user0/mail, index=, indexpvt=, control=, inbox=/var/mail/virtual/domain1.zw.local =login_user=user0/user0/mail, alt= then login_user=user0/user0/mail Apr 12 19:53:18 postfix10 dovecot: imap(user0(a)domain1.zw.local =login_user=user0)<2428><iPA4Yc6/lJCsEAAs>: Debug: Mailbox INBOX: Mailbox opened because: SELECT doveconf -n # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 5.10.0-7-amd64 x86_64 Debian 10.6 # Hostname: postfix10.zw.local auth_debug = yes auth_gssapi_hostname = $ALL auth_krb5_keytab = /etc/dovecot/imap.keytab auth_mechanisms = gssapi auth_verbose = yes disable_plaintext_auth = no import_environment = TZ KRB5CCNAME=/etc/dovecot/imap.ticket KRB5_KTNAME=/etc/dovecot/imap.keytab mail_debug = yes mail_gid = 5000 mail_home = /var/mail/virtual/%d/%n mail_location = maildir:~/mail mail_privileged_group = mail mail_uid = 5000 namespace inbox { disabled = no inbox = yes list = 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 = type = private } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocols = " imap lmtp pop3" service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl = no ssl_cert = </etc/dovecot/private/dovecot.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } userdb { driver = prefetch } protocol lmtp { postmaster_address = postmaster(a)zw.local } egrep -v "^$|^#" /etc/dovecot/dovecot-ldap.conf.ext uris = ldap://ldap10.zw.local auth_bind = yes sasl_bind = yes sasl_mech = gssapi sasl_realm = zw.local debug_level = -1 ldap_version = 3 base = dc=zw,dc=local user_attrs = \ =user=%{ldap:mail} \ =login_user=%{ldap:uid} user_filter = (uid=%n) pass_attrs = \ =user=%{ldap:uid},\ =k5principals=%{ldap:krbPrincipalName} pass_filter = (&(objectClass=krbPrincipalAux)(uid=%n)) -- Lucas Castro

1 1