- dovecot - dovecot.org

Block insecure connections
by Andrea Gabellini 09 Aug '21

09 Aug '21

Hello, I am writing for advice on how to deal with a problem. I have a Dovecot Proxy/Director -> Backend installation, all with version 2.3 Encryption on POP3 / IMAP connections is currently optional. I would like to set it as mandatory but despite the numerous reminders many users have not taken steps to adapt. Setting it as mandatory would mean having too many calls to support. I would therefore like to block the connection to only some of them and slowly reach my target. I can't find how and where to fit in to be able to do such a thing. At first I thought about postlogin, but the user ended up on a proxy and I can't use it. I tried to use the forwarding function on the proxy and postlogin on the backend, but I didn't succeed in the first part. In pseudo code, I would like to do this: if connection is not secured { if user is in my list { block the connection; } } Thanks in advance for any suggestions, Andrea -- __________________________ People says "more memory increases the computerspeed" and they are right: More memory Windows detects, the sooner it crashes. __________________________ TIM San Marino S.p.A. Andrea Gabellini Engineering R&D TIM San Marino S.p.A. - https://www.telecomitalia.sm Via Ventotto Luglio, 212 - Piano -2 47893 - Borgo Maggiore - Republic of San Marino Tel: (+378) 0549 886237 Fax: (+378) 0549 886188 -- Informativa Privacy Questa email ha per destinatari dei contatti presenti negli archivi di TIM San Marino S.p.A.. Tutte le informazioni vengono trattate e tutelate nel rispetto della normativa vigente sulla protezione dei dati personali (Reg. EU 2016/679). Per richiedere informazioni e/o variazioni e/o la cancellazione dei vostri dati presenti nei nostri archivi potete inviare una email a privacy(a)telecomitalia.sm. Avviso di Riservatezza Il contenuto di questa e-mail e degli eventuali allegati e' strettamente confidenziale e destinato alla/e persona/e a cui e' indirizzato. Se avete ricevuto per errore questa e-mail, vi preghiamo di segnalarcelo immediatamente e di cancellarla dal vostro computer. E' fatto divieto di copiare e divulgare il contenuto di questa e-mail. Ogni utilizzo abusivo delle informazioni qui contenute da parte di persone terze o comunque non indicate nella presente e-mail potra' essere perseguito ai sensi di legge.

2 2

doveadm pw
by Doug Hardie 07 Aug '21

07 Aug '21

mail# doveadm pw Enter new password: Retype new password: {CRYPT}$2y$05$oSB6end9V.YumJMzON7lfeOL9N8TXK6jhYqjHOEnPd1NLZ9.QNaTy I thought the default was supposed to be CRAM-MD5. I don't find anywhere I have entered CRYPT. There is one reference to it in auth-passwdfile.conf.ext, but changing that has no effect. Is this a bug, change, or my mistake? Thanks, mail# doveconf -n # 2.3.15 (0503334ab1): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.15 (e6a84e31) # OS: FreeBSD 13.0-RELEASE-p1 amd64 ufs # Hostname: mail auth_mechanisms = plain cram-md5 auth_stats = yes base_dir = /var/run/home_mail/ first_valid_gid = 0 lda_mailbox_autocreate = yes login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k session=<%{session}> port=%a mail_gid = 2222 mail_home = /var/mail/home_mail/%n mail_location = maildir:/var/mail/home_mail/%n/Maildir mail_log_prefix = "%s(%u)[%r]<%{session}>: " mail_uid = 2222 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 namespace inbox { inbox = yes location = mailbox Drafts { autoexpunge = 5 days special_use = \Drafts } mailbox Junk { autoexpunge = 2 days special_use = \Junk } mailbox Sent { autoexpunge = 1 weeks special_use = \Sent } mailbox "Sent Messages" { autoexpunge = 2 days special_use = \Sent } mailbox Trash { autoexpunge = 2 days special_use = \Trash } prefix = } passdb { args = scheme=CRYPT username_format=%n /usr/local/etc/dovecot/users driver = passwd-file } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size from sieve = file:/var/mail/home_mail/%n/sieve;active=/var/mail/home_mail/%n/.dovecot.sieve stats_refresh = 30 secs stats_track_cmds = yes } postmaster_address = doug(a)sermon-archive.info protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } inet_listener imaps2 { port = 998 ssl = yes } } service stats { unix_listener stats-reader { group = vmail mode = 0660 user = vmail } unix_listener stats-writer { group = vmail mode = 0660 user = vmail } } ssl_cert = </etc/ssl/certs/mail.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it syslog_facility = local0 userdb { args = home=/var/mail/home_mail/%d/%n allow_all_users=yes driver = static } verbose_proctitle = yes protocol lda { mail_plugins = " sieve" } protocol imap { mail_plugins = " mail_log notify" } protocol pop3 { mail_plugins = " mail_log notify" } -- Doug

3 3

Dovecot GSSAPI Authentication problem
by Lucas Castro 06 Aug '21

06 Aug '21

Hello, I'm getting problem to setup dovecot imap/pop service authentication through Kerberos. Already read https://wiki.dovecot.org/Authentication/Kerberos. My guess is kerberos is working but something goes wrong after. The keytab and ticket ( for ldap userdb lookup ) -rw------- 1 dovecot dovecot 498 ago 3 20:20 /etc/dovecot/imap.keytab -rw------- 1 dovecot root 1503 ago 4 11:40 /etc/dovecot/imap.ticket dovecot --version 2.3.13 (89f716dc2) the dovecot setting # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 5.10.0-7-amd64 x86_64 Debian 11.0 # Hostname: postfix10.zw.local auth_gssapi_hostname = $ALL auth_krb5_keytab = /etc/dovecot/imap.keytab auth_mechanisms = gssapi auth_username_translation = /@ import_environment = TZ KRB5CCNAME=/etc/dovecot/imap.ticket KRB5_KTNAME=/etc/dovecot/imap.keytab 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 } protocols = " imap lmtp pop3" service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } 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 } protocol lmtp { postmaster_address = postmaster(a)zw.local } When I launch Thunderbird, mail log raise this Aug 4 13:42:23 postfix10 dovecot: auth: Debug: client in: AUTH#0111#011GSSAPI#011service=pop3#011session=Q3GdfL7IvLmsEAAs#011lip=10.16.0.220#011rip=172.16.0.44#011lport=110#011rport=47548 Aug 4 13:42:23 postfix10 dovecot: auth: Debug: gssapi(?,172.16.0.44,<Q3GdfL7IvLmsEAAs>): Using all keytab entries Aug 4 13:42:23 postfix10 dovecot: auth: Debug: client passdb out: CONT#0111#011 Aug 4 13:42:23 postfix10 dovecot: auth: Debug: client in: CONT<hidden> Aug 4 13:42:23 postfix10 dovecot: auth: Debug: gssapi(user0(a)zw.local,172.16.0.44,<Q3GdfL7IvLmsEAAs>): security context state completed. Aug 4 13:42:23 postfix10 dovecot: auth: Debug: client passdb out: CONT#0111#011YIGZBgkqhkiG9xIBAgICAG+BiTCBhqADAgEFoQMCAQ+iejB4oAMCARKicQRvsoco75BA/W0B9tS+UmJnunUg6vIcO5wr0fzZ7iGmCpsz0K2vL/qniGISDIwF9hDXXxs79bljbZE8Yx4dujqVuTPGMtewfhDtNfRNgYGNk/z28sDz7fs/dpIMKF2FAA1m9pFjBupQ1VkGbzMYc77U Aug 4 13:42:23 postfix10 dovecot: auth: Debug: client in: CONT<hidden> Aug 4 13:42:23 postfix10 dovecot: auth: Debug: gssapi(user0(a)zw.local,172.16.0.44,<Q3GdfL7IvLmsEAAs>): Negotiated security layer Aug 4 13:42:23 postfix10 dovecot: auth: Debug: client passdb out: CONT#0111#011BQQF/wAMAAAAAAAAAdf8bQH///86U2L5ErmqfWFYNQA= Aug 4 13:42:23 postfix10 dovecot: auth: Debug: client in: CONT<hidden> Aug 4 13:42:23 postfix10 dovecot: auth: Error: gssapi(user0(a)domain1.zw.local,172.16.0.44,<Q3GdfL7IvLmsEAAs>): All password databases were skipped Aug 4 13:42:23 postfix10 dovecot: auth: Debug: auth(user0(a)domain1.zw.local,172.16.0.44,<Q3GdfL7IvLmsEAAs>): Auth request finished Aug 4 13:42:25 postfix10 dovecot: auth: Debug: client passdb out: FAIL#0111#011user=user0@domain1.zw.local#011code=temp_fail#011original_user=user0@ZW.LOCAL Aug 4 13:42:25 postfix10 dovecot: pop3-login: Debug: Ignoring unknown passdb extra field: original_user Can someone help on this? -- Lucas Castro

2 2

Pigeonhole v0.5.16 released
by Timo Sirainen 06 Aug '21

06 Aug '21

Hi, Pigeonhole release for Dovecot v2.3.16. https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.16.t… <https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.16.t…> https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.16.t… <https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.16.t…> Binary packages in https://repo.dovecot.org/ <https://repo.dovecot.org/> Docker images in https://hub.docker.com/r/dovecot/dovecot <https://hub.docker.com/r/dovecot/dovecot> * .dovecot.sieve.log file now includes year in the header. * Change Sieve script result execution to delay definitive action execution to the end of a successful Sieve script execution session. This is part of an effort to solve problems with the Sieve duplicate test. As a side-effect, some rare temporary-error cases yield different results, in which partial failure is more likely.

1 0

Dovecot Debian repo instructions need updating
by Laura Smith 05 Aug '21

05 Aug '21

Re: https://doc.dovecot.org/installation_guide/dovecot_community_repositories/d… The instructions need updating for two reasons: 1) Keep up to date with Debian releases (https://wiki.debian.org/DebianReleases) i.e. remove reference to 8.0 "Jessie" and replace with 10.0 "Buster". 2) The instructions presented for key handling are not inline with Debian best-practices. As per https://wiki.debian.org/DebianRepository/UseThirdParty: "The key MUST be downloaded over a secure mechanism like HTTPS to a location only writable by root, which SHOULD be /usr/share/keyrings. The key MUST NOT be placed in /etc/apt/trusted.gpg.d or loaded by apt-key add. A sources.list entry SHOULD have the signed-by option set. The signed-by entry MUST point to a file, and not a fingerprint."

2 4

quota_grace
by dovecot＠ptld.com 05 Aug '21

05 Aug '21

There isn't much documentation on quota_grace. How would you disable quota grace? quota_grace = 0 quota_grace = 0% quota_grace = 0m quota_grace = -1 Assuming "0" isn't an "unlimited" setting?

2 1

dovecot + Procmail -> junk emails
by Stephane Magnier 03 Aug '21

03 Aug '21

Hi, Having moved from 'mbox' to 'Maildir', I'm trying to use a way to move a spam email to the Junk folder I declared the junk folder as; namespace inbox { type = private disabled = no ignore_on_failure = no list = yes subscriptions = yes #hidden = no #inbox = yes #prefix = INBOX/ mailbox "Drafts" { auto = subscribe special_use = \Drafts } mailbox "Junk" { auto = subscribe autoexpunge = 12 weeks special_use = \Junk } mailbox "Trash" { auto = no autoexpunge = 12 weeks special_use = \Trash } mailbox "Sent" { auto = subscribe special_use = \Sent } and spamassassin, very basic loadplugin Mail::SpamAssassin::Conf required_hits 5 required_score 5 rewrite_header subject [** SPAM ** ] add_header all Status _YESNO_, score=_SCORE_ required=_REQD_ tests=_TESTS_ autolearn=_AUTOLEARN_ version=_VERSION_ spf_timeout 60 rewrite_header to [Email could be SPAM ] fold_headers 0 #defang_mime 0 report_safe 0 and Procmail.. basic and I used what I found on the webpage : https://wiki.dovecot.org/procmail <https://wiki.dovecot.org/procmail> DELIVER="/usr/lib/dovecot/deliver -d $LOGNAME" SHELL="/bin/bash" SENDMAIL="/usr/sbin/sendmail -oi -t" LOGFILE="/var/log/procmail.log" DEFAULT="/var/spool2/mail/%u :0fw | /bin/spamc -s any ####################################### #:0 #* ^X-Spam-Status: Yes #$DEFAULT ####################################### :0 w * ^X-Spam-Status: Yes | $DELIVER -m Junk # ## deliver to INBOX and stop # deliver to INBOX and stop :0 w | $DELIVER But with this config, a spam email, stay into the Inbox :-( /var/log/procmail.log... doesn't exist Thanks for you help

3 3

Multiple Quota Limit Configurations
by Joseph D Wagner 02 Aug '21

02 Aug '21

Is this a valid quota rule? *:storage=0,messages=0 Or do I need to make them two separate rules? Joseph D Wagner

1 0

Timo - is the v2.3.15 GCC limitation really necessarily or it's just a bug?
by Mart Pirita 02 Aug '21

02 Aug '21

Hello. So far I have successfully built Dovecot until v2.3.14 on Centos 4-6 (yes I know, they are old, but as they are remote servers, distros can't upgraded), and sometimes I have also met compilation issues, but after highlighting them, Timo have fixed the code. Found from similar thread (Dovecot 2.3.15 compilation fails https://dovecot.org/list/dovecot/2021-June/122412.html ) that new GCC is needed. However I can't find such requirement in v2.3.15 change log. As seems that I'm not the only one with compilation issues, then @Timo - can You please fix the code so that also v2.3.15 can compiled on older distros? Compilation options: ./configure --prefix=/usr --with-ssl=openssl --with-ssldir=/etc/ssl --sysconfdir=/etc --with-pam --without-bsdauth --without-sql --without-nss --without-ldap --without-pgsql --without-mysql --without-sqlite --with-rundir=/var/run/dovecot --without-cassandra --without-lucene --without-solr --without-textcat --without-libcap --without-stemmer --disable-rpath --disable-dependency-tracking --disable-silent-rules --without-gssapi --without-cdb Compilation error: builtin-strftime -c -o test-smtp-params.o test-smtp-params.c test-smtp-params.c:29: error: unknown field `data' specified in initializer test-smtp-params.c:29: warning: missing braces around initializer test-smtp-params.c:29: warning: (near initialization for `test_params_buffer1.<anonymous>') test-smtp-params.c:30: warning: missing initializer test-smtp-params.c:30: warning: (near initialization for `test_params_buffer1.<anonymous>.<anonymous>.used') test-smtp-params.c:30: error: unknown field `used' specified in initializer test-smtp-params.c:31: warning: excess elements in struct initializer test-smtp-params.c:31: warning: (near initialization for `test_params_buffer1') test-smtp-params.c:33: error: unknown field `data' specified in initializer test-smtp-params.c:33: warning: missing braces around initializer test-smtp-params.c:33: warning: (near initialization for `test_params_buffer2.<anonymous>') test-smtp-params.c:34: warning: missing initializer test-smtp-params.c:34: warning: (near initialization for `test_params_buffer2.<anonymous>.<anonymous>.used') test-smtp-params.c:34: error: unknown field `used' specified in initializer test-smtp-params.c:35: warning: excess elements in struct initializer test-smtp-params.c:35: warning: (near initialization for `test_params_buffer2') make[3]: *** [test-smtp-params.o] Error 1 make[3]: Leaving directory `/usr/src/redhat/BUILD/dovecot-2.3.15/src/lib-smtp' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/src/redhat/BUILD/dovecot-2.3.15/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/redhat/BUILD/dovecot-2.3.15' make: *** [all] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.7364 (%build) -- Mart

9 12

SQL Backend for IMAP METADATA Dictionary
by Joseph D Wagner 01 Aug '21

01 Aug '21

I've seen documentation on using a SQL backend for quota dictionary and passdb&userdb dictionary. However, I can't find any examples of a SQL backend for IMAP METADATA / mail_attributes_dict. Is this combination possible? If so, is there an example somewhere? I am unsure what data structures it's expected or how to create the map entries for it. Thanks in advance. Joseph D. Wagner

2 4

Disable authentication for submission service
by Dan Conway 01 Aug '21

01 Aug '21

Hello, Is it possible to disable the requirement for authentication on the submission service? I'm trying to require authentication for all, except for a handful of IP addresses. Thank you. ehlo test.com 250-aaa 250-AUTH PLAIN LOGIN 250-BURL imap 250-CHUNKING 250-DSN 250-ENHANCEDSTATUSCODES 250-SIZE 250 PIPELINING MAIL FROM:<test(a)test.com> 530 5.7.0 Authentication required.

8 11

Re: check_policy_service sends size=0
by dovecot＠ptld.com 01 Aug '21

01 Aug '21

> It sounds like a better approach would be to make Dovecot reject any > email no matter what the size is (even size=0) if a user is over > quota. I'll take further discussion to the dovecot mailing list then. If you are not aware, dovecot has by default a 10% over quota grace. So even being a couple of bytes over quota it would still accept a small message.

3 3

Re: Monitoring of director back end nodes
by Tom Sommer 31 Jul '21

31 Jul '21

On 2021-07-31 19:28, darkc0de wrote: > So dovemon for Dovecot pro, but nothing for community? https://github.com/brandond/poolmon --- Tom

1 0

Monitoring of director back end nodes
by Dan Conway 31 Jul '21

31 Jul '21

Hello, When working with director, the state of the backend nodes are not checked by Dovecot. The state always remains as "up". I understand that there are external applications documented that monitor backend nodes, and changes the state of them to "down" if they become unresponsive. The question I have is are there plans to implement something built into Dovecot that would monitor and change states based on backend "health"? Or will it always be dependent on an external service? Thanks.

3 2

quota-status fails when size=0 from Postfix
by Christoph Haas 30 Jul '21

30 Jul '21

Dear list, I've been pulling my hair out today and kindly ask you for help. I'm on Debian Bullseye with Dovecot 2.3.13 and Postfix 3.5.6. Users are stored in SQL and I want to use quotas. Basically I followed https://doc.dovecot.org/configuration_manual/quota_plugin/#quota-service With mail_debug enabled I see that the information from SQL is fetched correctly: dovecot: quota-status(test(a)bullseye.example.org)<45148><>: Debug: auth-master: userdb lookup(test(a)bullseye.example.org): auth USER input: test(a)bullseye.example.org quota_rule=*:bytes=1000 home=/var/vmail/bullseye.example.org/test uid=5000 gid=5000 So the quota rule "*:bytes=1000" is loaded as intended for testing. Before handing the email over to Dovecot through LMTP Postfix should call the quota-service (policy daemon) to determine if the user is over quota: smtpd_recipient_restrictions = \ reject_unauth_destination \ check_policy_service inet:localhost:12340 This is still by the book. What I found: - sending a test mail with Thunderbird properly returns a 5xx status (over quota) - sending a test mail with SWAKS returns DUNNO (swaks is an SMTP test tool) I have used tcpdump to look into the communication on port 12340 and the difference appears to be the "size=0" line that Postfix sends if I use SWAKS. Output from SWAKS: -> RCPT TO:<test(a)bullseye.example.org> <- 250 2.1.5 Ok However if Thunderbird sends an email it uses something like -> RCPT TO:<test(a)bullseye.example.org> SIZE=12345 If I understand the situation correctly then Postfix extracts the SIZE=… value and uses that to send it to the quota-status policy daemon. The user however is definitely over quota: $> doveadm quota get -u test(a)bullseye.example.org Quota name Type Value Limit % User quota STORAGE 1 1 100 User quota MESSAGE 1 - 0 So whatever the size of the incoming email is, it should be rejected. As quota-status returns DUNNO, Postfix will send the email to Dovecot through LMTP. And LMTP in turn does another quota check and correctly rejects the email: postfix/lmtp[45153]: 573419D6A3: to=<test(a)bullseye.example.org>, relay=iredmail-test[private/dovecot-lmtp], delay=0.08, delays=0.05/0.01/0.01/0.01, dsn=5.2.2, status=bounced (host iredmail-test[private/dovecot-lmtp] said: 552 5.2.2 <test(a)bullseye.example.org> Quota exceeded (mailbox for user is full) (in reply to end of DATA command)) Problem here is that a bounce is created and Postfix is sending backscatter. Had "quota-service" indicated that the mailbox is over quota then Postfix had instantly rejected the email without any bounce. I can also reproduce this effect by talking to the quota-status daemon: printf "recipient=test(a)bullseye.example.org\nsize=0\n\n" | nc localhost 12340 action=DUNNO printf "recipient=test(a)bullseye.example.org\nsize=10000\n\n" | nc localhost 12340 action=554 5.2.2 Quota exceeded (mailbox for user is full) Is this a feature? A bug? An evil coincidence? Thanks for reading this far. I know that this matter seems a bit complicated. But it feels like Dovecot's behavior leads to backscatter and of course I'd like to avoid that. Kindly… Christoph

4 14

[bug 2.3.15] seeing user-shared mailboxes across different storage types requires manual change to subscriptions
by Michal Soltys 29 Jul '21

29 Jul '21

Hi, While I was checking old bug I once reported (that one seems to be fixed, https://www.dovecot.org/list/dovecot/2017-January/106593.html) I discovered another issue happening under current version when user sharing his mailbox (with Maildir storage) is not visible under user using mdbox (or sdbox, also tested) - unless subscriptions file is manually adjusted (after subscribing). Consider following config: # 2.3.15 (0503334ab1): /etc/dovecot/dovecot.conf # OS: Linux 5.12.14-arch1-1 x86_64 Arch Linux btrfs # Hostname: hakai auth_debug = yes auth_mechanisms = plain login disable_plaintext_auth = no first_valid_uid = 1 listen = * mail_debug = yes mail_gid = dovecot mail_location = maildir:/var/mail1/%n/Maildir mail_plugins = acl mail_uid = dovecot namespace { inbox = yes location = prefix = separator = / type = private } namespace shared1 { inbox = no list = yes location = maildir:%%h/Maildir/ prefix = shared1/%%n/ separator = / subscriptions = no type = shared } namespace shared2 { inbox = no list = yes location = mdbox:%%h/mdbox/ prefix = shared2/%%n/ separator = / subscriptions = no type = shared } passdb { args = /etc/dovecot/local-maildir driver = passwd-file } passdb { args = /etc/dovecot/local-mdbox driver = passwd-file } plugin { acl = vfile acl_shared_dict = file:/var/mail-data/shared-database/shared-mailboxes.db } protocols = imap service auth { unix_listener auth-userdb { group = mail mode = 0660 user = dovecot } user = dovecot } service imap-login { inet_listener imap { address = * port = 143 } inet_listener imaps { address = * port = 993 } user = dovecot } service imap { executable = /usr/lib/dovecot/imap } userdb { driver = prefetch } userdb { args = /etc/dovecot/local-maildir driver = passwd-file } userdb { args = /etc/dovecot/local-mdbox driver = passwd-file } protocol imap { mail_max_userip_connections = 100 mail_plugins = acl imap_acl } /etc/dovecot/local-maildir: user1:{PLAIN}test:::user1:/var/mail1/user1::userdb_mail=maildir:/var/mail1/user1/Maildir userdb_home=/var/mail1/user1 user2:{PLAIN}test:::user2:/var/mail1/user2::userdb_mail=maildir:/var/mail1/user2/Maildir userdb_home=/var/mail1/user2 /etc/dovecot/local-mdbox: user3:{PLAIN}test:::user3:/var/mail2/user3::userdb_mail=mdbox:/var/mail2/user3/mdbox userdb_home=/var/mail2/user3 There are two shared namespaces - shared1 for Maildir mailboxes and shared2 for mdbox ones. 'user1' is sharing his 'qwer' folder to user3. doveadm mailbox create -u user1 -s qwer doveadm acl add -u user1 qwer user=user3 read lookup doveadm mailbox subscribe -u user3 shared1/user1/qwer This produces subscriptions file such as: 14:44 # cat /var/mail2/user3/mdbox/subscriptions V 2 Trash shared1 user1 qwer With all that in place, 'qwer' won't be visible to user3. But if we change the 'shared1 user1 qwer' to shared1/user1/qwer - then everything will be working fine. Sharing mdbox folder to maildir user (user3 -> user1) as well as maildir to maildir (user1 -> user2) works without issues.

1 1

Shared mailbox strange behaviors
by Ervin Hegedüs 27 Jul '21

27 Jul '21

Hi there, I've set up my Dovecot instance for shared mail accounts. I'm using Debian 10, Dovecot 2.3.4. This is what I did: #namespace { # type = private # separator = / # prefix = # location = # inbox = yes #} namespace { type = shared separator = / prefix = Osztott/%%u/ location = maildir:%%h:INDEX=~/shared/%%u subscriptions = no list = yes } Note, the word "Osztott" means "Shared" in my language. The strange behaviors: 1: as you can see, the first empty namespace is commented. This is because when I restarted the Dovecot instance, it sent this message to the log: Error: namespace configuration error: Duplicate namespace prefix: "" When I commented out these lines, the error message left. Why did that happen? What's the real solution? 2: with this config, I see the shared accounts under my account, with prefix "Osztott" - but the shared account is duplicated. There are two instances with similar names. In first mailbox I see the e-mails, this is fine. But under the "regular" name of the shared mailbox, there is the other mailbox with the same name + a suffix "-1", which is empty. Why is that second maildir there? Thank you for your help, a.

1 0

Submission server and Outlook delivery notification
by Tobia Grosselle [ Terralink ] 26 Jul '21

26 Jul '21

Version: 2.3.15 (0503334ab1) Hello everyone, it seems that the delivery notification function on Outlook doesn't work with Dovecot Submission service, is expected? Will it be implemented? Thanks in advance

1 0

Dovecot and Android's Gmail app
by Jakub Filo 26 Jul '21

26 Jul '21

Hello, does anyone else have this problem with connecting to dovecot (imap) via gmail app on Android, where after removing messages, they reappear shortly after? It happens seemingly randomly, not always. -- Jakub Filo jakub(a)plantroon.com

2 1

Set vhost count in config
by William Edwards 23 Jul '21

23 Jul '21

Hi, Can we do `doveadm director update ... 100` in the on-disk config, so the vhost count is retained after the ring goes down? I could not find such an option in doveconf. -- With kind regards, William Edwards

1 0

Quick Question
by Stephane Magnier 23 Jul '21

23 Jul '21

Hi, Is there a way to transform a "*mbox*" structure ( in the folder : like /var/spool/mail/........ ) into a *maildir* structure ? I would dream to see a doveadm instruction doing something like : */doveadm /var/spool/mail/%u /var/spool2/./*...... something like this.. That would be great !! :-) Thanks and regards

2 2

dovecot and auth cache
by Maciej Milaszewski 23 Jul '21

23 Jul '21

Hi In my lab I have tested auth cache in dovecot like: 1) test auth doveadm auth login ala(a)domain.ltd pass passdb: ala(a)domain.ltd auth succeeded - user ala(a)domain.ltd is in mysql (klater galera) 2)I stop the galley cluster 3)test auth - via cache doveadm auth login ala(a)domain.ltd pass passdb: ala(a)domain.ltd auth succeeded 4)flush cache root@msmtp3:~# doveadm auth cache flush 2 cache entries flushed root@msmtp3:~# doveadm auth cache flush 0 cache entries flushed - cache is emty 5)test auth doveadm auth login ala(a)domain.ltd pass passdb: ala(a)domain.ltd auth succeeded Why 5 step give - successed ? doveconf -n # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-12-amd64 x86_64 Debian 10.9 ... auth_cache_negative_ttl = 5 mins auth_cache_ttl = 5 mins ... If I restart dovecot works correctly - I mean: doveadm auth login ala(a)domain.ltd pass not auth I dont have any idea

1 1

BDAT to DATA translation on submission service when checkpassword is involved
by Dan Conway 23 Jul '21

23 Jul '21

Hello, I'm having issues with Dovecot translating "BDAT" commands (CHUNKING) into "DATA" commands when the backend does not support it in the submission service. I use "checkpassword" to authenticate users and judging by older mailing list entries the presence of "submission_*" directives must be in place for Dovecot to translate. Even with these directives set, the translation doesn't seem to occur. checkpassword returns "director_tag=remote_smtp" (along with other fields such as nopassword=y proxy=y) which in turn sets the backend host to relay the connection to. I have a feeling the use of checkpassword has something to do with this lack of translation. If the "submission_*" directives must be in place for this translation to occur, which ones are they? Can I return these fields from checkpassword? Output of doveconf -n: # 2.3.15 (0503334ab1): /etc/dovecot/dovecot.conf # OS: Linux 4.15.0-147-generic x86_64 Ubuntu 18.04.5 LTS # Hostname: xyz auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth_verbose = yes director_mail_servers = x.x.x.x@remote_smtp director_servers = x.x.x.x disable_plaintext_auth = no mail_log_prefix = "%Us(%u) [%r]: " passdb { args = /usr/local/bin/checkpassword driver = checkpassword } protocols = " imap pop3 submission" service anvil { client_limit = 3553 } service auth { client_limit = 3550 } service director { fifo_listener login/proxy-notify { mode = 0600 user = $default_login_user } inet_listener { address = x.x.x.x port = 9090 } unix_listener director-admin { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director inet_listener imap { address = x.x.x.x port = 143 } inet_listener imaps { address = x.x.x.x port = 993 ssl = yes } process_limit = 1000 process_min_avail = 0 service_count = 1 } service imap { process_limit = 2048 process_min_avail = 0 service_count = 1 vsz_limit = 384 M } service pop3-login { executable = pop3-login director inet_listener pop3 { address = x.x.x.x port = 110 } inet_listener pop3s { address = x.x.x.x port = 995 ssl = yes } process_limit = 450 } service pop3 { process_limit = 190 process_min_avail = 0 service_count = 1 } service submission-login { executable = submission-login director inet_listener smtp { address = x.x.x.x port = 25 } inet_listener smtps { address = x.x.x.x port = 465 ssl = yes } inet_listener submission { address = x.x.x.x port = 587 } process_limit = 2000 } ssl_cert = </etc/... ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.1 submission_backend_capabilities = submission_host = x.x.x.x submission_relay_host = x.x.x.x submission_relay_port = 465 submission_relay_ssl = smtps submission_relay_trusted = yes userdb { args = /etc/dovecot/userdb.conf driver = ldap } protocol imap { imap_logout_format = bytes=%i/%o, del=%e mail_max_userip_connections = 20 } protocol pop3 { mail_max_userip_connections = 20 pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s } protocol submission { mail_max_userip_connections = 10 } local_name *.domain.com { ssl_cert = </etc/... ssl_key = # hidden, use -P to show it }

2 1

folders and subfolders
by Stephane Magnier 22 Jul '21

22 Jul '21

Hi, Still looking for the way to create folders and sub folders.. Today, I am using "mbox", which apparently doesn't work for this ? correct ? So, I would probably need to use maildir.. ( https://doc.dovecot.org/configuration_manual/mail_location/Maildir/ ] Today, what I am using is :*mbox, *which is gather all the mailboxes of user 1, user 2 in one folder... like : mbox:/var/spool2/mail/%u 1) I suppose, that If I am using "mbox" with .. : LAYOUT=fs, I won't get these folders and subfolders ? - Correct ? 2) Instead of having : "maildir:~/Maildir " which, I suppose got each_user folder into their own home directory_ .. correct ? Can I have : *maildir:/var/spool2/mail/%u *? ( I would prefer to gather all users' mailbox into one folder like /var/spool2/mail/ ) 3) if so, *mbox:/var/spool2/mail/%u:INBOX=/var/spool/mail/%u* => can become : *maildir:/var/spool2/mail/%u:LAYOUT=fs:INBOX=/var/spool/mail/%u* What do you think ?... before trying and breaking everything :-)... if so, I will be killed Thanks and regards

5 20

Doveadm encrypt/decrypt files manually with per-user folder keys
by Ben Burk 21 Jul '21

21 Jul '21

There is an example of manually encrypting/decrypting mail processed by the mail_crypt plugin here: https://doc.dovecot.org/configuration_manual/mail_crypt_plugin/ It outlines how one would manually encrypt/decrypt messages using global keys: doveadm fs get/put crypt private_key_path=foo:public_key_path=foo2:posix:prefix=/path/to/files/root path/to/file Is there a way to accomplish this using per-user folder keys? Is there some way of making sense of the information in the dovecot-attributes file to accomplish this? -- Ben Burk BURK.TECH System Administrator

2 6

Traffic accounting
by Jesús Ángel del Pozo Domínguez 20 Jul '21

20 Jul '21

Hello, Could you please tell me whether is it possible to do traffic accounting using Dovecot 2.3.4? What I'd like to do is to collect network traffic (both in & out) for each user (both POP and IMAP traffic). Regards,

4 4

dovecot-lmtp crashing when setting lmtp_proxy=yes
by Camilo Sperberg 19 Jul '21

19 Jul '21

Hi all: We are currently in the process of setting up dovecot proxy so that we can deploy multiple machines in order to keep growing. We are trying now to create an entry point, and from there send the traffic to either the same machine or another node. For this, we are using a MySQL database with information about which server hosts which mailboxes, which turns out to be working great for sending out mail and general authentification. This was really simple to set up, kudos for that! However, whenever I want to *receive* email, I just have to enable the lmtp_proxy setting which makes the lmtp process segfault. This happens everytime as I can reliable reproduce it + get a stack trace of it. The process will crash on every incoming email. I have attached: - Complete output of dovecot-sysreport - A core dump of the crashed process Main information: Using dovecot v2.3.14 (cee3cbc0d) on Ubuntu 18.04 LTS: Linux 5.4.0-1046-gcp x86_64 Ubuntu 18.04.5 LTS. Our MTA is postfix. Logs around the crashed process: Jul 15 14:53:21 server postfix/postscreen[19402]: CONNECT from [XX.XX.XX.XX]:36411 to [10.164.0.18]:25 Jul 15 14:53:22 server postfix/dnsblog[19406]: addr XX.XX.XX.XX listed by domain dnsbl.sorbs.net as 127.0.0.6 Jul 15 14:53:27 server postfix/postscreen[19402]: PASS NEW [XX.XX.XX.XX]:36411 Jul 15 14:53:27 server postfix/smtpd[19408]: connect from mail-XX.google.com [XX.XX.XX.XX] Jul 15 14:53:28 server postfix/smtpd[19408]: B765F401DB: client= mail-XX.google.com[XX.XX.XX.XX] Jul 15 14:53:28 server postfix/cleanup[19411]: B765F401DB: message-id=< XX+5j3RpXXXXXOK7GHdiDSGSPXXXX(a)mail.gmail.com> Jul 15 14:53:29 server postfix/qmgr[1414]: B765F401DB: from=< unreal4u(a)gmail.com>, size=2815, nrcpt=1 (queue active) Jul 15 14:53:29 server dovecot: lmtp(19413): Connect from local Jul 15 14:53:29 server kernel: [1738624.857507] lmtp[19413]: segfault at 0 ip 00007fd486cd0a37 sp 00007ffc12a6c118 error 4 in libdovecot.so.0.0.0[7fd486ba1000+1aa000] Jul 15 14:53:29 server kernel: [1738624.857514] Code: eb de 90 48 85 d2 75 1e eb 33 66 0f 1f 84 00 00 00 00 00 84 c0 74 18 48 83 c7 01 48 83 c6 01 88 47 ff 48 83 ea 01 48 83 fa 01 <0f> b6 06 77 e4 c6 07 00 31 c0 80 3e 00 0f 95 c0 f7 d8 c3 b8 ff ff Jul 15 14:53:29 server dovecot: lmtp(19413): Fatal: master: service(lmtp): child 19413 killed with signal 11 (core dumped) Jul 15 14:53:29 server postfix/lmtp[19412]: B765F401DB: to=<YYY(a)YYYY.YY>, relay=ZZZ.ZZZ.ZZ[private/dovecot-lmtp], delay=0.88, delays=0.84/0.01/0.01/0.03, dsn=4.4.2, status=deferred (lost connection with ZZZ.ZZZ.ZZ[private/dovecot-lmtp] while sending RCPT TO) Jul 15 14:53:29 server postfix/smtpd[19408]: disconnect from mail-XX.google.com[XX.XX.XX.XX] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 Am I missing something in the conf? Did I encounter a bug? If you need more information, please let me know. Greetings, Camilo Sperberg

2 2

Major upgrade of mail server
by Shawn Heisey 18 Jul '21

18 Jul '21

I have a mail server in AWS that is currently running Ubuntu 18. Every time I log in, I am reminded that I can upgrade to Ubuntu 20. On Ubuntu 18, the dovecot version is 3.3.0-1ubuntu0.3. On Ubuntu 20, it is 2.3.7.2-1ubuntu3. Many other packages, probably including the mysql server, would also be upgraded. Dovecot and Postfix use a postfixadmin database in mysql for users, and postfix is using dovecot-lda to deliver mail. I am using managesieve from dovecot on roundcube webmail. As far as I know, my own user is the only one with sieve scripts actually in use ... and I have a LOT of filters/folders for various mailing lists. I've been a little bit terrified of doing an upgrade, because I do have a couple of people using my mail server for real work email and I don't want to disrupt them. I'm writing today to find out what are the likely pain points I might encounter when doing this kind of major upgrade, and if there is any helpful information that can help me get through those problems. I'm hoping that it will go smoothly and everything just works. Here's the doveconf -n output: https://apaste.info/FUgF If I have been silly enough to include sensitive data from the config, I would appreciate a heads up so I know what passwords to change. I did a quick glance and didn't see anything. Thanks, Shawn

5 5

Dovecot book for a newbie
by techlists＠phpcoderusa.com 16 Jul '21

16 Jul '21

Hi, Please recommend a Dovecot book for a newbie... I have a fair amount of Linux PHP hosting experience - LAMP virtual host configurations. I'm new to BIND, Postfix, and Dovecot. I'm running Ubuntu 20.04lts. I have a test server almost working. Can send but not receive. Would like to understand more. I'm guessing it is a Zone (MX) / SSL / Client configuration issue. Thanks in advance!!

5 8

OT somewhat, how to unsubscribe?
by Christy S 16 Jul '21

16 Jul '21

Hi folks, It's been a while since I've subscribed and I don't remember how to get off the mailing list. We've changed how we're handling mail now, so dovecot is no longer being used. Can anyone help? MOst mailing lists have a blurb at the bottom with instructions but this one doesn't seem to. Thanks Christy

3 2

Dovecot geographically distributed
by Claudio Corvino 16 Jul '21

16 Jul '21

Hi, I have a single Dovecot (2.3.4.1) IMAP/LMTP server on HQ "A" and I would like to create a backup server distributed to HQ "B", two HQ are connected through an IPsec tunnel. User mailboxes (type mbox) are on NFS storage. I don't need HA, it could even be an active / passive configuration with a floating IP, but I don't know how to keep in sync the two remote NFS filesystems. I don't know if Dovecot replication is suitable for me. Thanks -- *Claudio Corvino IT Systems Administrator*

1 0

2FA/MFA with IMAP & postfix/submission
by Alex 16 Jul '21

16 Jul '21

Hi, I have a dovecot-2.3.13 system on fedora34 with a few hundred IMAP4 accounts, as well as postfix users using submission. Clients are using primarily Outlook on Windows and old squirrelmail. Are there multi-factor options available? If it is not available, do you have any recommendations on where I should look to do this? All of the links related to this topic appear to be very old, or limited to Linux PAM users.

12 19

function for whitelisting IPs
by White, Daniel E. (GSFC-770.0)[NICS] 16 Jul '21

16 Jul '21

Sebastian, Do you have any examples of such a function and how/where it is used ? -----Original Message----- From: dovecot <dovecot-bounces(a)dovecot.org> on behalf of Sebastian <sebastian(a)sebbe.eu> Reply-To: Dovecot Mailing List <dovecot(a)dovecot.org> Date: Thursday, July 15, 2021 at 01:19 To: 'Mailing List' <dovecot(a)dovecot.org> Subject: [EXTERNAL] Sv: 2FA/MFA with IMAP & postfix/submission Main problem is that not many clients do natively support multifactor. Some clients, do popup a login dialog if the server rejects the password as invalid, which can be used to create a "cheaty variant" of multifactor, but some clients just popup an error dialog and tell the user to just correct password in settings. Some clients even go as long as requiring the user to delete the account with wrong password and set up a new connection. So no, it cannot be relied upon. I have a better idea: Have a function for whitelisting IPs, possible /24's or similiar, where a login to roundcube or other webmail client (with 2FA) will add the IP onto a whitelist for that account. Or perhaps, just "set" the country of the account based on GeoIP. When an account tries to login via IMAP or SMTP, you just check if IP and/or GeoIP country is right, and reject the login as invalid if so not. The only thing a client needs to do to get his IMAP or SMTP client to work again if it stops working, is to login once via the web client. -----Ursprungligt meddelande----- Från: dovecot-bounces(a)dovecot.org <dovecot-bounces(a)dovecot.org> För Alex Skickat: den 15 juli 2021 02:10 Till: dovecot(a)dovecot.org Ämne: 2FA/MFA with IMAP & postfix/submission Hi, I have a dovecot-2.3.13 system on fedora34 with a few hundred IMAP4 accounts, as well as postfix users using submission. Clients are using primarily Outlook on Windows and old squirrelmail. Are there multi-factor options available? If it is not available, do you have any recommendations on where I should look to do this? All of the links related to this topic appear to be very old, or limited to Linux PAM users.

7 10

TLS Security
by Stefan Schumacher 15 Jul '21

15 Jul '21

Hi, I wish to build a new secure email server. It seems I am on the right way – at least I get no more error messages for Postfix – but Dovecot is still making trouble. I am using Dovecot 1:2.3.4.1-5+deb10u6 and I am using ISPconfig 3.25 to do the rough configuring and nano and whats left of my brain to do the finer details. Lets start with what I added to conf.d/10-ssl.conf ssl_cert = </etc/letsencrypt/live/servername/fullchain.pem ssl_key = </etc/letsencrypt/live/servername/privkey.pem ssl_cipher_list = EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aR$ ssl_protocols = !SSLv2 !SSLv3 !TLSv1 !TLSv1.1 ssl_min_protocol = TLSv1.2 As you can see, I clearly do not want to use TLS before v1.2. I think this is not unreasonable in the year 2021. Now, after the changes I ran Kali (I use it to verify the results of my experiments) and - this is a mailing list, so no screenshots: It says: SSL/TLS Deprecated TLS v1.0 and TLS v1.1 Detection. I get this for the ports 143, 110, 993 and 995. I thought I had done everything one could to disable old TLS-Versions. What am I doing wrong? Yours sincerely Stefan Schumacher

4 6

AW: TLS Security
by Stefan Schumacher 15 Jul '21

15 Jul '21

Hi Justina, Kali tools is of course extremly unprecise. Excuse me, I had a long stressful day and wanted to get this out before the end of the Day. Kali is a rolling release and I keep it up to date by upgrading every few days. I also update the feeds. What I actually use for security scans is the former OpenVAS, which now has been relegated to being a part of the Community Edition of the Greenbone suite. You have seen the values I have in Dovecot. What follows now are my settings in the postfix main.cf. As you can clearly see it, it should prevent connections from TLS below 1.2. Dovecot is of course not very fresh because it's Debian 10 and Debian 11 is just around the corner (a few days). These are the settings of my postfix main.cf. I am very tempted to grab an Image of Debian 11 and install ISPConfig and my Dovecot and Postfix settings there. I am of course open to any other suggestions. A the moment I consider to install a new Bullseye RC2 and then put my configuration on it. I am of course open for any other suggestions. Yours sincerely Stefan smtpd_use_tls = yes smtpd_tls_cert_file = /etc/postfix/smtpd.cert smtpd_tls_key_file = /etc/postfix/smtpd.key smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_tls_eecdh_grade = strong smtpd_tls_protocols= !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtpd_tls_mandatory_protocols= !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtpd_tls_mandatory_ciphers = high smtpd_tls_security_level=may smtpd_tls_ciphers = high tls_preempt_cipherlist = yes smtpd_tls_mandatory_exclude_ciphers = aNULL, MD5 , DES, ADH, RC4, PSD, SRP, 3DES, eNULL smtpd_tls_exclude_ciphers = aNULL, MD5 , DES, ADH, RC4, PSD, SRP, 3DES, eNULL smtp_tls_mandatory_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtp_tls_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 ________________________________ Von: justina colmena ~biz <justina(a)colmena.biz> Gesendet: Mittwoch, 14. Juli 2021 18:50 An: dovecot(a)dovecot.org <dovecot(a)dovecot.org>; Stefan Schumacher <s.schumacher(a)consulting1x1.com> Betreff: Re: TLS Security Interesting. Assuming your "Kali" tools are in fact up to date to test with newer protocols TLS1.2+, is Dovecot compiled against a recent version of the OpenSSL or GnuTLS library or whatever it uses to support the newer TLS protocols? Definitely an outdated cipher issue, on Postfix as well as Dovecot.... On July 14, 2021 6:55:19 AM AKDT, Stefan Schumacher <s.schumacher(a)consulting1x1.com> wrote: Hi, I wish to build a new secure email server. It seems I am on the right way – at least I get no more error messages for Postfix – but Dovecot is still making trouble. I am using Dovecot 1:2.3.4.1-5+deb10u6 and I am using ISPconfig 3.25 to do the rough configuring and nano and whats left of my brain to do the finer details. Lets start with what I added to conf.d/10-ssl.conf ssl_cert = </etc/letsencrypt/live/servername/fullchain.pem ssl_key = </etc/letsencrypt/live/servername/privkey.pem ssl_cipher_list = EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aR$ ssl_protocols = !SSLv2 !SSLv3 !TLSv1 !TLSv1.1 ssl_min_protocol = TLSv1.2 As you can see, I clearly do not want to use TLS before v1.2. I think this is not unreasonable in the year 2021. Now, after the changes I ran Kali (I use it to verify the results of my experiments) and - this is a mailing list, so no screenshots: It says: SSL/TLS Deprecated TLS v1.0 and TLS v1.1 Detection. I get this for the ports 143, 110, 993 and 995. I thought I had done everything one could to disable old TLS-Versions. What am I doing wrong? Yours sincerely Stefan Schumacher -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

1 0

Verifying replication
by Arnold Hendriks 15 Jul '21

15 Jul '21

Dear Dovecot people, I've set up Dovecot replication a couple of years ago. I'm watching the general server health and having Nagios check doveadm replicator status regularly. I'm seeing accounts replicating, disk space usage obviously shows that things work in principle, however, I still wonder whether the replication actually works properly. Accounts I check work, but 1-5% of the messages could easily be missing without me noticing it. These servers have I think about 50K accounts (a lot of them dormant) and between 1 to 2TB of mail. I'm trying to get some more confidence as to whether replication is actually working properly and whether I'm not missing anything that will burn me if I ever have to 'fallback'. Has anyone ever done some verification outside of simply watching doveadm replication stats, to see if they are missing anything ? Eg, I could imagine a process that generates a list of accounts, and then generates hashes on both sides of the replication for each mailbox folder. If the hashes match, the folder gets removed from the list, and once all folders are removed, the account gets removed. Iterating the account list should finally reduce it to 0, or a few extremely high traffic accounts which can be checked manually or be ignored. But I'm trying to avoid reinventing the wheel. Has anyone done anything like this, or can suggest a different approach? With regards, Arnold Hendriks

1 1

Forcing replication - difference is a 0x0D 0x0D 0xA sequence?
by Arnold Hendriks 15 Jul '21

15 Jul '21

I've found a few mailboxes on my system that were being replicated where the mailboxes are not in sync. On server 1 I see: dovecot1:/# doveadm fetch -u s0000000 "size.physical size.virtual" mailbox-guid c92f64f79f0d1ed01e6d5b314f04886c uid 115 size.physical: 1815 size.virtual: 1843 On server 2 I see: dovecot2:/# doveadm fetch -u s0000000 "size.physical size.virtual" mailbox-guid c92f64f79f0d1ed01e6d5b314f04886c uid 115 size.physical: 1805 size.virtual: 1833 Running ' doveadm replicator replicate -f s0000000 "*" ' does not fix the issue. I've compared the mails and the difference appears to be that the primary server (where the mail comes in) has a few occurences of "0D 0D 0A" (hex) which on the replicated server looks like "0D 0A". (ie, \r\r\n was replicated as \r\n ?) Is there a way to force these two messages to be in sync again ? Is the \r\r\n being replicated as \r\n a known issue ? (I'm not sure if I could replicate this, this message dates back to 2007 so probably wasn't even received originally on this server. Replication was configured much later than 2007)

1 0

folders management
by Stephane Magnier 15 Jul '21

15 Jul '21

Hi, Sorry to ask you , maybe a silly question :-) On my folders' architecture, I can see all the folders underneeth each other fodler1 folder2 etc.... I would like to have the possibility to have _folders INTO folders_, like Folder1 Folder2 .......folder 21 ......folder 22 Folders 3 Apparently, this is link to this déclaration :__*_mbox_:/var/spool2/mail/%u. *Is that correct ? is that the "mbox" declaration? or Am I complety wrong ? If I have need to change...I have to change it for what ? * Can I use this new structure with NFS shares ? * What is the backside of it ? Now, if I make this modification.. on an existing dovecot system... , Will it make a true disaster ? or I can change the declaration easily? Thanks and regards,

2 1

Restrict number of mail moved/copied
by Amol Kulkarni 14 Jul '21

14 Jul '21

Hello, I need to restrict number of mail moved/copied by end user using imap in operation. Is there any configuration for that ? Thanks and regards, Amol

1 0

dsync I/O Stalled
by Paolo Daniele 14 Jul '21

14 Jul '21

Hi guys, i've a strange problem between 2 servers. It happened after a changing on our network core routing infrastructure. We've moved to Juniper network and eBGP and iBGP of our server. One of this server is behind a firewall and communicate with another server in another country to sync our emails. Doveadmin replica seems to be fine, but sometimes i get this error message: dsync-server(aaaaa(a)bbb.bb): Error: Timeout during state=sync_mails (send=done recv=mails) It seems like the remote server has troubles to reach our local server but if i do a stupid ping i'm not losing anything. Maybe is there something am i missing? I thought that it could be related to a MTU problem but i'm not so sure and i've increased MTU on the routers involved in routing process without success. I wa missing that both servers are behind a load balancer wich is in our local DC. Can you give me some hints? Regards, Paolo -- Paolo Daniele Intendo s.r.l. E-mail: paolo.daniele(a)intendo.it Business Unit TLCWEB Tel.: +39 0968 430786 Via Coschi, 11 Skype: paolo_daniele1 88046 - Lamezia Terme, Cz Web: http://www.tlcweb.it Italia Web: http://www.intendo.it

2 2

Potential bug: Assumption that POSIX time functions do not clobber errno
by Florian Weimer 13 Jul '21

13 Jul '21

We accidentally ran the dovecot 2.3.14 testsuite on a host where clock_gettime (and probably time and gettimeofday) succeed, but set errno to ENOSYS. This behavior is unusual, but permitted by POSIX: successful function calls can overwrite errno, as long as they don't set it to 0. The relevant log excerpt looks like this: make[3]: Entering directory '/builddir/build/BUILD/dovecot-2.3.14/src/master' for bin in test-auth-client test-auth-master test-master-login-auth; do \ if ! ./$bin; then exit 1; fi; \ done test-common.c:200: Assert failed: suppress == TRUE connection refused: run (ret == -1) .................................. : ok: Connection failed CLIENT: Error: auth-client: conn unix:./auth-client-test: connect(./auth-client-test) failed: Function not implemented connection refused ................................................... : FAILED connection timed out: run (ret == -1) ................................ : ok: Connection failed connection timed out: timeout ........................................ : ok connection timed out ................................................. : ok bad version: run (ret == -1) ......................................... : ok: Connection failed bad version .......................................................... : ok disconnect version: run (ret == -1) .................................. : ok: Internal failure disconnect version ................................................... : ok auth PLAIN disconnect: run (ret < 0) ................................. : ok auth PLAIN disconnect ................................................ : ok auth PLAIN reconnect: run (ret < 0) .................................. : ok auth PLAIN reconnect ................................................. : ok auth PLAIN failure: run (ret < 0) .................................... : ok auth PLAIN failure ................................................... : ok auth PLAIN success: run (ret == 0) ................................... : ok auth PLAIN success ................................................... : ok auth LOGIN failure 1: run (ret < 0) .................................. : ok auth LOGIN failure 1 ................................................. : ok auth LOGIN failure 2: run (ret < 0) .................................. : ok auth LOGIN failure 2 ................................................. : ok auth LOGIN success: run (ret == 0) ................................... : ok auth LOGIN success ................................................... : ok auth PLAIN parallel failure: run (ret < 0) ........................... : ok auth PLAIN parallel failure .......................................... : ok auth PLAIN parallel success: run (ret == 0) .......................... : ok auth PLAIN parallel success .......................................... : ok auth LOGIN parallel failure 1: run (ret < 0) ......................... : ok auth LOGIN parallel failure 1 ........................................ : ok auth LOGIN parallel failure 2: run (ret < 0) ......................... : ok auth LOGIN parallel failure 2 ........................................ : ok auth LOGIN parallel success: run (ret == 0) .......................... : ok auth LOGIN parallel success .......................................... : ok 1 / 49 tests failed make[3]: Leaving directory '/builddir/build/BUILD/dovecot-2.3.14/src/master' “Function not implemented” suggests that dovecot somehow used the clock_gettime (or gettimeofday) ENOSYS error instead of the expected ECONNREFUSED error code. Unfortunately, I have not figured out where this exactly happens. I don't expect that the problematic glibc build escapes to the wild It was a glibc 2.34 development snapshot, and this particular source of ENOSYS errors is gone again. So fixing this is not urgent. Thanks, Florian

1 0

move mails between mailboxes
by Tom Doenen 13 Jul '21

13 Jul '21

Hello, i am using dovecot 2.3.4.1 I am tyring to make a script using the doveadm move command to move old emails into a subfolder of the users INBOX ; say all mails from 2016 into INBOX/2016. Selecting and moving is not the issue; everything works just i am amazed that the (test) mail client Thunderbird downloads all mails in INBOX/2016 after the move. When i make an IMAP move of all 2016-mails in Thunderbird; mails are moved between the mailboxes without any mails being (re-)downloaded. So what am i missing here? Thank for the tip :) Kind regards, Tom the doveadm move debug output is : Debug: Loading modules from directory: /usr/lib/dovecot/modules Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so Debug: Module loaded: /usr/lib/dovecot/modules/lib20_listescape_plugin.so Debug: Module loaded: /usr/lib/dovecot/modules/lib20_zlib_plugin.so Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_deinit (this is usually intentional, so just ignore this message) Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_sieve_plugin.so Debug: Skipping module doveadm_fts_lucene_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_lucene_plugin.so: undefined symbol: lucene_index_iter_deinit (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_user_get_language_list (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_mail_crypt_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_mail_crypt_plugin.so: undefined symbol: mail_crypt_box_get_pvt_digests (this is usually intentional, so just ignore this message) doveadm(tom(a)somedomain.org)<17541><>: Debug: auth USER input: tom(a)somedomain.org uid=5000 gid=5000 home=/mailstore/somedomain.org/to/tom/ doveadm(tom(a)somedomain.org): Debug: Effective uid=5000, gid=5000, home=/mailstore/somedomain.org/to/tom/ doveadm(tom(a)somedomain.org): Debug: Quota root: name=User quota backend=maildir args= doveadm(tom(a)somedomain.org): Debug: Quota rule: root=User quota mailbox=* bytes=8589934592 messages=0 doveadm(tom(a)somedomain.org): Debug: Quota rule: root=User quota mailbox=Trash bytes=+104857600 messages=0 doveadm(tom(a)somedomain.org): Debug: Quota warning: bytes=8589934592 (100%) messages=0 reverse=no command=quota-warning 100 tom(a)somedomain.org doveadm(tom(a)somedomain.org): Debug: Quota warning: bytes=8504035246 (99%) messages=0 reverse=no command=quota-warning 99 tom(a)somedomain.org doveadm(tom(a)somedomain.org): Debug: Quota warning: bytes=8418135900 (98%) messages=0 reverse=no command=quota-warning 98 tom(a)somedomain.org doveadm(tom(a)somedomain.org): Debug: Quota warning: bytes=8246337208 (96%) messages=0 reverse=no command=quota-warning 96 tom(a)somedomain.org doveadm(tom(a)somedomain.org): Debug: Quota warning: bytes=8074538516 (94%) messages=0 reverse=no command=quota-warning 94 tom(a)somedomain.org doveadm(tom(a)somedomain.org): Debug: Quota warning: bytes=7902739824 (92%) messages=0 reverse=no command=quota-warning 92 tom(a)somedomain.org doveadm(tom(a)somedomain.org): Debug: Quota warning: bytes=7730941132 (90%) messages=0 reverse=no command=quota-warning 90 tom(a)somedomain.org doveadm(tom(a)somedomain.org): Debug: Quota warning: bytes=7301444403 (85%) messages=0 reverse=no command=quota-warning 85 tom(a)somedomain.org doveadm(tom(a)somedomain.org): Debug: Quota warning: bytes=6871947673 (80%) messages=0 reverse=no command=quota-warning 80 tom(a)somedomain.org doveadm(tom(a)somedomain.org): Debug: Quota warning: bytes=6012954214 (70%) messages=0 reverse=no command=quota-warning 70 tom(a)somedomain.org doveadm(tom(a)somedomain.org): Debug: Quota warning: bytes=8589934592 (100%) messages=0 reverse=yes command=quota-warning 0 tom(a)somedomain.org doveadm(tom(a)somedomain.org): Debug: Quota grace: root=User quota bytes=47185920 doveadm(tom(a)somedomain.org): Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/mailstore/somedomain.org/to/tom:INDEX=/indexes/somedomain… doveadm(tom(a)somedomain.org): Debug: maildir++: root=/mailstore/somedomain.org/to/tom, index=/indexes/somedomain.org/to/tom, indexpvt=, control=, inbox=/mailstore/somedomain.org/to/tom/.INBOX, alt= doveadm(tom(a)somedomain.org): Debug: quota: quota_over_flag check: quota_over_script unset - skipping doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: Mailbox opened because: move doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: Mailbox opened because: move doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52642: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52643: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52644: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52645: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52646: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52963: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52964: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52965: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52967: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52968: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52969: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52970: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52972: Opened mail because: mail stream etc etc... obscured config : # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.194-rt81 x86_64 Debian 10.0 ext4 # Hostname: hardy.somedomain.org auth_cache_negative_ttl = 7 mins auth_cache_size = 20 M auth_cache_ttl = 12 mins auth_cache_verify_password_with_worker = yes auth_failure_delay = 9 secs auth_mechanisms = plain login auth_username_chars = auth_worker_max_count = 90 default_client_limit = 2500 default_process_limit = 500 default_vsz_limit = 4 G hostname = post.somedomain.org imap_capability = +SPECIAL_USE imap_fetch_failure = no-after imap_hibernate_timeout = 15 secs imap_idle_notify_interval = 4 mins imap_max_line_length = 512 k lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lda_original_recipient_header = X-Original-To listen = * lmtp_rcpt_check_quota = yes login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k mail_cache_min_mail_count = 15 mail_fsync = never mail_location = maildir:/mailstore/%d/%2n/%n:INDEX=/indexes/%d/%2n/%n:INBOX=/mailstore/%d/%2n/%n/.INBOX:VOLATILEDIR=/tmp/dovecot:NO-NOSELECT:UTF-8 mail_max_keyword_length = 100 mail_plugins = quota zlib listescape mail_prefetch_count = 20 mail_privileged_group = mail mail_temp_scan_interval = 0 mailbox_idle_check_interval = 55 secs mailbox_list_index_include_inbox = yes mailbox_list_index_very_dirty_syncs = yes maildir_broken_filename_sizes = yes maildir_very_dirty_syncs = yes namespace inbox { inbox = yes location = mailbox Concepts { auto = no special_use = \Drafts } mailbox "Deleted Messages" { auto = no special_use = \Trash } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = no special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } passdb { args = /etc/dovecot/passwd--%d driver = passwd-file } plugin { listescape_char = } quota = maildir:User quota quota_grace = 45M quota_rule = *:storage=8G quota_rule2 = Trash:storage=+100M quota_status_overquota = 552 5.2.2 User mailbox is full.. quota_status_succes = DUNNO quota_warning = storage=100%% quota-warning 100 %u quota_warning10 = storage=70%% quota-warning 70 %u quota_warning11 = -storage=100%% quota-warning 0 %u quota_warning2 = storage=99%% quota-warning 99 %u quota_warning3 = storage=98%% quota-warning 98 %u quota_warning4 = storage=96%% quota-warning 96 %u quota_warning5 = storage=94%% quota-warning 94 %u quota_warning6 = storage=92%% quota-warning 92 %u quota_warning7 = storage=90%% quota-warning 90 %u quota_warning8 = storage=85%% quota-warning 85 %u quota_warning9 = storage=80%% quota-warning 80 %u sieve = ~/dovecot.sieve sieve_extensions = +notify +imapflags +envelope +vacation +fileinto +date +relational +vacation-seconds sieve_user_log = /dev/null sieve_vacation_min_period = 1h sieve_vacation_send_from_recipient = yes virtual_overquota_bounce = yes zlib_save = gz zlib_save_level = 3 } pop3_fast_size_lookups = yes protocols = imap lmtp pop3 service auth-worker { user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-hibernate { unix_listener imap-hibernate { group = $default_internal_group mode = 0660 } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { address = 100.100.100.104 port = 993 ssl = yes } process_min_avail = 20 service_count = 0 } service imap { extra_groups = $default_internal_group process_limit = 5000 unix_listener imap-master { user = $default_internal_user } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { address = 100.100.100.99 port = 995 ssl = yes } process_min_avail = 10 service_count = 0 } service pop3 { process_limit = 1000 } service quota-warning { executable = script /etc/dovecot/quota-warning.sh unix_listener quota-warning { user = vmail } user = vmail } service submission-login { inet_listener submission { address = 127.0.0.1 port = 587 ssl = yes } process_min_avail = 5 service_count = 1 } service submission { process_limit = 150 } ssl = required ssl_cert = </etc/ssl/private/somedomain.org.crta ssl_cipher_list = ALL:!SSLv2:!SSLv3:!DH:!kRSA:!SRP:!kDHd:!DSS:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK:!RC4:!ADH:!LOW@STRENGTH:!EXP:!SEED:!IDEA:!RSA:!CAMELLIA:!SHA1:!SHA256:!SHA384 ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes submission_host = 127.0.0.1 syslog_facility = local2 userdb { args = /etc/dovecot/passwd--%d driver = passwd-file result_failure = return-fail result_internalfail = return-fail } valid_chroot_dirs = /var/spool/vmail verbose_proctitle = yes protocol lmtp { mail_fsync = optimized mail_plugins = quota zlib listescape quota sieve zlib postmaster_address = postmaster(a)somedomain.org } protocol lda { mail_fsync = optimized } protocol imap { mail_max_userip_connections = 25 mail_plugins = quota zlib listescape imap_quota zlib } protocol pop3 { mail_max_userip_connections = 6 }

2 1

doveadm backup Error: Mailbox INBOX sync
by Pierre Sablé 13 Jul '21

13 Jul '21

Hi, the command "doveadm backup -u {user@mail} maildir:/home/backup/{user@mail}/mails/" returns the following error : dsync(user@mail): Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted. ...and nothing in dovecot logs dovecot actual version 2.3.15 I did not have this pb in dovecot 2.3.2 /Should this be considered a bug report?/ -- Pierre Sablé Formateur & Administrateur Systèmes Linux - DevOps Tel : 07.63.88.76.21 psable(a)dawan.fr www.dawan.fr

1 0

[ENHANCEMENT] Doveadm HTTP API and the mail-crypt plugin
by Kevin N. 13 Jul '21

13 Jul '21

Hello everybody, I was wondering, are there any plans for the near future to include the mail-crypt plugin related functions, like changing the user key password, into the doveadm http api? It would probably be possible to implement it in a more secure way than any other external ad-hoc solution. Wouldn't it? Cheers, K.

2 2

getting rid of the passwd file unknown user messages
by Marc 12 Jul '21

12 Jul '21

I have configured a userdb file, so I can test with some accounts and override settings. But it is a bit annoying getting unkown user messages for the majority of accounts not in this userdb. Is there a way to skip this reporting? dovecot: auth: passwd-file(aaaaaaaaaaaa,X.X.X.X,<lGapvOzGS5tNPz8/>): unknown user

2 3

Mailbox lost
by Stephane Magnier 12 Jul '21

12 Jul '21

Hi, Any idea why * * *list "" * *-> displays all I want to see but *lsub "" ** -> doesn't display anything ? and AFAIK, this is what I need to get in order any Email clients see my folders ? - Correct ? how can I make visible, by "lsub" all my folders ? Thanks and regards,

4 4

doveadm altmove -r still broken in 2.3.15
by María Arrea 12 Jul '21

12 Jul '21

2 1

High Availability Dovecot / Roundcube / PostfixAdmin ?
by White, Daniel E. (GSFC-770.0)[NICS] 12 Jul '21

12 Jul '21

This is a new setup, running on RHEL 8 with the latest everything. Has anyone out there set up a high availability pair of Dovecot servers - with Roundcube and PostfixAdmin - successfully ? "Callahan's Law: Shared pain is lessened; shared joy, increased — thus do we refute entropy" (Spider Robinson)

4 3

Sieve vacation + SRS + forwarded e-mail
by Saarts, Erik 10 Jul '21

10 Jul '21

Hello! Having a problem here and am unable to solve it on my own and even dr Google is unable to help. We have domain A on cloud, from where mail gets forwarded to our local server to domain B. Forwarding is done in SPF-compliant way by using SRS (this part we have no control over). This SRS address ends up in Return-Path header, and sieve vacation replies to this address. This is all absolutely correct, but also useless, as sending mail to SRS address leads nowhere. I've tried to edit headers in sieve before passing control to vacation, but that does not work. I tried modifying Return-Path to the value of X-Original-Sender (both in user's sieve file and using scripts in "sieve_before" parameter). Mail gets delivered with changed headers, but vacation acts upon original headers. Is there a workaround? MTA is postfix (3.1.15), dovecot is version 2.3.4.1 (f79e8e7e4), Pigeonhole version 0.5.4 LMTP as local delivery agent. Erik

2 1

Nabble
by Plutocrat 10 Jul '21

10 Jul '21

Not sure if this is an issue, but Nabble seems to have stopped archiving this newsgroup around 22 Jun. http://dovecot.2317879.n4.nabble.com/ Thought I should probably tell someone P.

1 0