February 2022 - dovecot

Messages reappearing in mailboxes as duplicates
by Andrew Skipper 22 Feb '22

22 Feb '22

Hello, We have 3 nodes running, with a two way replication between 2 of them and a 1 way replication to a DR node running off one. We use mdbox, and directors to split traffic across nodes. There is no shared file system. Users are experiencing messages reappearing in their INBOX as unread with duplicate GUID and message headers. This occurs generally several days after a message was first received (and often actioned; read, moved, trashed, expunged, also often bulk moved/deleted). We have attempted to remove replication from the equation by cutting down to one single node with all replication disabled which did not have any impact. We have also started regular cache and mailbox purging. There are no logged events when mail items reappear, and we only observe it based on user report, mailbox inspection (doveadm looking for duplicate GUIDs/unique message headers) or seeing IMAP commands being done against the same message twice (e.g. monday they copy to trash, delete and expunge from inbox, delete and expunge from trash, then the next monday they will have to do the same for the reappearing message). OS: Centos 7 Dovecot: dovecot -version Scheduled jobs: */15 0 * * 0 doveadm sync -u "*" tcps:<dr node>:12345 > /var/log/dovecot/dr_sync.log 2>&1 1 3 * * * doveadm mailbox cache purge -A INBOX 21 3 * * * doveadm mailbox cache purge -A Trash 0 1 * * 0 /usr/bin/doveadm purge -A >/dev/null 2>&1 Conf: dovecot -n # 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-1160.53.1.el7.x86_64 x86_64 CentOS Linux release 7.9.2009 (Core) # Hostname: <primary node> auth_master_user_separator = * default_vsz_limit = 1 G disable_plaintext_auth = no dotlock_use_excl = no doveadm_password = # hidden, use -P to show it listen = * mail_fsync = always mail_location = mdbox:~/mail mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = " notify replication" mmap_disable = yes namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { autoexpunge = 30 days special_use = \Trash } prefix = separator = . } passdb { args = /etc/dovecot/conf.d/passwd.masterusers driver = passwd-file master = yes } passdb { args = /etc/dovecot/conf.d/passwd.masterusers driver = passwd-file } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename save flag_change mail_log_fields = uid box msgid size flags mail_log_group_events = mail_replica = tcps:<second node>:12345 } protocols = imap service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = vmail } unix_listener replication-notify { mode = 0666 user = vmail } } service doveadm { inet_listener { port = 12345 ssl = yes } } service imap-login { inet_listener imap { port = 144 } inet_listener imaps { port = 994 ssl = yes } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl = required ssl_cert = </etc/pki/dovecot/certs/dovecot-internal.pem ssl_cipher_list = TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_client_ca_file = /etc/ssl/certs/ca-bundle.crt ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = /etc/dovecot/conf.d/dovecot-dict-auth.conf.ext driver = dict } userdb { args = /etc/dovecot/conf.d/dovecot-ldap.conf.ext driver = ldap } protocol imap { mail_max_userip_connections = 9999 mail_plugins = " notify replication mail_log notify" } Any thoughts would be greatly appreciated. Thanks in advance, Andrew

1 0

Pigeonhole page's RFC links broken (fix attached)
by Patrick Nagel 22 Feb '22

22 Feb '22

Hi there, I was just reading https://pigeonhole.dovecot.org/ and noticed that all the links to the RFCs are broken. I fixed them via regexp search & replace curl https://pigeonhole.dovecot.org/ | sed -e 's|https\?://tools.ietf.org/html/rfc\([0-9]\{4\}\)/\?|https://www.ietf.org/r…' >Pigeonhole_fixed_rfc_links.html and attached the resulting page. Cheers, Patrick.

1 0

postfix, dovecot-lda, /run/dovecot/stats-writer socket permision and local user delivery, again
by Michael Tokarev 22 Feb '22

22 Feb '22

Hi! There are many questions on the 'net about the same theme: lda(mjt): Error: net_connect_unix(/run/dovecot/stats-writer) failed: Permission denied dovecot-lda is run from postfix as mailbox_command for local users. There's even a suggestion on dovecot wiki to make dovecot-lda setgid (to mail) - for a different reason but people use this trick to shut this error message up. See eg the last message at https://forum.zentyal.org/index.php?topic=35236.0 which points to https://wiki2.dovecot.org/LDA/Postfix . But the thing is: mail delivery stops right after making dovecot-lda setgid, like this: Feb 22 00:06:46 tsrv dovecot: lda(mjt)<253650><s+nnHub+E2LS3gMA7tuOMA>: \ Fatal: setresgid(914(dovecot),914(dovecot),8(mail)) failed with euid=1000(mjt): \ Operation not permitted why the hell lda tries to setuid to dovecot user? It will definitely unable to write to the maildir since it is owned by user mjt, not by user dovecot! And I *only* made it setgid, not setuid. How to use dovecot-lda together with postfix, after all? Thanks, /mjt

2 2

RE: Different auth logging with cache lookup. (OPEN)
by Eikås Arvid 22 Feb '22

22 Feb '22

No, the problem is the logging of the cache lookup with password mismatch. (release 2.3.17) We missing client IP and user in the cache lookup logging. auth-worker(1676266): Info: conn unix:auth-worker (pid=1675846,uid=97): auth-worker<2>: Password mismatch (given password: xxxx) Arvid -----Original Message----- From: Aki Tuomi <aki.tuomi(a)open-xchange.com> Sent: tirsdag 22. februar 2022 09:15 To: Eikås Arvid <arvid.eikas(a)telenor.no>; dovecot(a)dovecot.org Subject: Re: Different auth logging with cache lookup. (OPEN) > On 22/02/2022 09:42 Eikås Arvid <arvid.eikas(a)telenor.no> wrote: > > > dovecot-2.3.5 and centos 7 > User and IP are logged in both scenarios. > auth-worker(26145): sql(user,1.1.1.1,<XXXXXXXX>): Password mismatch > auth-worker(13380): cache(user(a)online.no,1.1.1.1): Password mismatch > > > > > dovecot-2.3.17 and rhel 8 > Feb 03 14:42:53 auth-worker(1676266): Info: conn unix:auth-worker > (pid=1675846,uid=97): auth-worker<1>: sql(user,127.0.0.1,<XXXXXXXX>): > Password mismatch (given password: xxxx) Feb 03 14:43:48 > auth-worker(1676266): Info: conn unix:auth-worker > (pid=1675846,uid=97): auth-worker<2>: Password mismatch (given > password: xxxx) > > User and IP is not logged in cache lookup. > Is this a design change or a unplanned change? > > Any ide when it was changed? Looks more like 2.3.5 is incorrectly checking both cache and sql? Aki

1 0

Different auth logging with cache lookup. (OPEN)
by Eikås Arvid 22 Feb '22

22 Feb '22

dovecot-2.3.5 and centos 7 User and IP are logged in both scenarios. auth-worker(26145): sql(user,1.1.1.1,<XXXXXXXX>): Password mismatch auth-worker(13380): cache(user(a)online.no,1.1.1.1<mailto:user@online.no,1.1.1.1>): Password mismatch dovecot-2.3.17 and rhel 8 Feb 03 14:42:53 auth-worker(1676266): Info: conn unix:auth-worker (pid=1675846,uid=97): auth-worker<1>: sql(user,127.0.0.1,<XXXXXXXX>): Password mismatch (given password: xxxx) Feb 03 14:43:48 auth-worker(1676266): Info: conn unix:auth-worker (pid=1675846,uid=97): auth-worker<2>: Password mismatch (given password: xxxx) User and IP is not logged in cache lookup. Is this a design change or a unplanned change? Any ide when it was changed?

2 1

/usr/libexec/dovecot/anvil crashes immediately
by Friedrich Kink 21 Feb '22

21 Feb '22

Dear list, I built a dovecot package for openindiana (which is a Solaris derivative) from latest version 2.3.18. Everything compiles and builds fine without any issue. Even subsequent installation and startup of main dovecot process works as expected. But execution of /usr/libexec/dovecot/anvil immediately crashes. To get some more meaningful backtrace I compiled with -g. Below some facts of my environment and a backtrace. Maybe some of you are more familiar with this kind of issue as I, and can give some hint or share ideas how to nail down the problem. Or can it be a configuration issue? BTW it is running in a so-called zone. And former versions, I don't know exactly but I believe up to 2.3.17, did not show this crash. gcc --version gcc (OpenIndiana 7.5.0-il-0) 7.5.0 Configure parameters: gcc_OPT = -g CONFIGURE_OPTIONS+= --sysconfdir=/etc \ --localstatedir=/var \ --with-gssapi=plugin \ --with-ldap=plugin \ --with-sql=plugin \ --with-lua=plugin \ --with-ssl=openssl \ --with-ioloop=poll \ --with-notify=none \ --with-sodium \ --with-mysql \ --with-pgsql \ --enable-static=no \ --without-systemd \ SSL_CFLAGS=-I/usr/openssl/1.1/include \ SSL_LIBS="-L/usr/openssl/1.1/lib/amd64 -lssl -lcrypto" \ LDFLAGS="-lldap_r" Backtrace: (gdb) bt full #0 0x00007fff5d2e6f2a in _lwp_kill () from /lib/64/libc.so.1 No symbol table info available. #1 0x00007fff5d2dd7f0 in thr_kill () from /lib/64/libc.so.1 No symbol table info available. #2 0x00007fff5d27ae7e in raise () from /lib/64/libc.so.1 No symbol table info available. #3 0x00007fff5d254ad8 in abort () from /lib/64/libc.so.1 No symbol table info available. #4 0x00007ffef05367c0 in default_fatal_finish (type=LOG_TYPE_PANIC, status=0) at /usr/src/myoi-userland/components/mail/dovecot/dovecot-2.3.18/src/lib/failures.c:459 backtrace = 0x4178b8 "/usr/lib/amd64/dovecot/libdovecot.so.0.0.0'backtrace_append_libc+0x4c [0x7ffef0522042] -> /usr/lib/amd64/dovecot/libdovecot.so.0.0.0'backtrace_append+0x18 [0x7ffef05221c5] -> /usr/lib/amd64/dovecot/li"... recursed = 0 #5 0x00007ffef0536827 in fatal_handler_real (ctx=0x7fffbffff820, format=0x7ffef05d8730 "file %s: line %d (%s): assertion failed: (%s)", args=0x7fffbffff850) at /usr/src/myoi-userland/components/mail/dovecot/dovecot-2.3.18/src/lib/failures.c:471 status = 0 #6 0x00007ffef0536871 in default_fatal_handler (ctx=0x7fffbffff820, format=0x7ffef05d8730 "file %s: line %d (%s): assertion failed: (%s)", args=0x7fffbffff850) at /usr/src/myoi-userland/components/mail/dovecot/dovecot-2.3.18/src/lib/failures.c:479 No locals. #7 0x00007ffef0536aed in i_panic (format=0x7ffef05d8730 "file %s: line %d (%s): assertion failed: (%s)") at /usr/src/myoi-userland/components/mail/dovecot/dovecot-2.3.18/src/lib/failures.c:524 ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0, timestamp_usecs = 0, log_prefix = 0x0, log_prefix_type_pos = 0} args = {{gp_offset = 8, fp_offset = 48, overflow_arg_area = 0x7fffbffff930, reg_save_area = 0x7fffbffff870}} #8 0x00007ffef056048b in io_loop_handle_add (io=0x42d7c0) at /usr/src/myoi-userland/components/mail/dovecot/dovecot-2.3.18/src/lib/ioloop-poll.c:94 ctx = 0x423180 condition = IO_READ old_count = 3221223792 index = 0 old_events = 59 fd = 4 __func__ = "io_loop_handle_add" #9 0x00007ffef055c1ab in io_add_file (ioloop=0x423070, fd=4, condition=IO_READ, source_filename=0x7ffef05d9f48 "/usr/src/myoi-userland/components/mail/dovecot/dovecot-2.3.18/src/lib/lib-signals.c", source_linenum=192, callback=0x7ffef05698f4 <signal_read>, context=0x0) at /usr/src/myoi-userland/components/mail/dovecot/dovecot-2.3.18/src/lib/ioloop.c:72 io = 0x42d7c0 __func__ = "io_add_file" #10 0x00007ffef055c27a in io_add_to (ioloop=0x423070, fd=4, condition=IO_READ, source_filename=0x7ffef05d9f48 "/usr/src/myoi-userland/components/mail/dovecot/dovecot-2.3.18/src/lib/lib-signals.c", source_linenum=192, callback=0x7ffef05698f4 <signal_read>, context=0x0) at /usr/src/myoi-userland/components/mail/dovecot/dovecot-2.3.18/src/lib/ioloop.c:94 io = 0x7ffef0609aa0 <static_system_pool> __func__ = "io_add_to" #11 0x00007ffef0569289 in lib_signals_init_io (l=0x420a00) at /usr/src/myoi-userland/components/mail/dovecot/dovecot-2.3.18/src/lib/lib-signals.c:192 __func__ = "lib_signals_init_io" #12 0x00007ffef056933c in lib_signals_ioloop_ref (ioloop=0x423070) at /usr/src/myoi-userland/components/mail/dovecot/dovecot-2.3.18/src/lib/lib-signals.c:205 l = 0x420a00 #13 0x00007ffef0569507 in signal_handler_switch_ioloop (h=0x4209c0) at /usr/src/myoi-userland/components/mail/dovecot/dovecot-2.3.18/src/lib/lib-signals.c:232 No locals. #14 0x00007ffef056a10a in lib_signals_set_handler (signo=2, flags=LIBSIG_FLAG_DELAYED, handler=0x7ffef0475e74 <sig_die>, context=0x422f20) at /usr/src/myoi-userland/components/mail/dovecot/dovecot-2.3.18/src/lib/lib-signals.c:520 h = 0x4209c0 __func__ = "lib_signals_set_handler" #15 0x00007ffef0477596 in master_service_init_finish (service=0x422f20) at /usr/src/myoi-userland/components/mail/dovecot/dovecot-2.3.18/src/lib-master/master-service.c:668 sigint_flags = LIBSIG_FLAG_DELAYED st = {st_dev = 79, st_ino = 4209307, st_mode = 1, st_nlink = 79, st_uid = 4218704, st_gid = 0, st_rdev = 17179869185, st_size = 4337776, st_atim = {tv_sec = 140736414612384, tv_nsec = 1}, st_mtim = {tv_sec = 0, tv_nsec = 8388608}, st_ctim = {tv_sec = 0, tv_nsec = 0}, st_blksize = 4378928, st_blocks = 255, st_fstype = " /B\000\000\000\000\000 /B\000\000\000\000"} __func__ = "master_service_init_finish" #16 0x0000000000403cce in main (argc=1, argv=0x7fffbffffc38) at /usr/src/myoi-userland/components/mail/dovecot/dovecot-2.3.18/src/anvil/main.c:80 service_flags = (MASTER_SERVICE_FLAG_UPDATE_PROCTITLE | MASTER_SERVICE_FLAG_DONT_SEND_STATS) error = 0x7fffbffffc10 " \374\377\277\377\177" Thanks a lot for any help, Fritz

2 1

Fwd: Memory problems with config service
by Víctor Rubiella Monfort 21 Feb '22

21 Feb '22

(Resend to list, sorry for personal reply) -------- Mensaje reenviado -------- Asunto: Re: Memory problems with config service Fecha: Wed, 16 Feb 2022 16:19:32 +0100 De: Víctor Rubiella Monfort <vrubiella(a)cdmon.com> Para: Aki Tuomi <aki.tuomi(a)open-xchange.com> # 2.2.27 (): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 () # OS: Linux 4.9.0-16-amd64 x86_64 Debian 9.9 auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@& auth_worker_max_count = 25 default_client_limit = 1200 disable_plaintext_auth = no first_valid_uid = 100 info_log_path = /var/log/dovecot-info.log log_path = /var/log/dovecot.log login_greeting = Server ready login_log_format_elements = user=<%u> method=%m port=%a rip=%r lip=%l mpid=%e %c mail_location = maildir:%h mail_max_userip_connections = 100 passdb { args = /etc/dovecot/mailaccounts.db driver = passwd-file } plugin { quota = maildir:User quota quota_rule3 = SPAM:storage=+50M } protocols = imap pop3 service config { vsz_limit = 9 G } service imap-login { process_limit = 500 } service pop3-login { process_limit = 500 } ssl_ca = </home/ssl/system/domain.cat/ca.pem ssl_cert = </home/ssl/system/domain.cat/crt.pem ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/mailaccounts.db driver = passwd-file } valid_chroot_dirs = /home/postfix/ protocol imap { mail_plugins = quota imap_quota mail_log notify } protocol pop3 { mail_plugins = quota mail_log notify } protocol lda { mail_plugins = quota } local_name *.hidden.com { ssl_cert = </home/ssl/dovecot/live/hidden.com/fullchain.pem ssl_key = # hidden, use -P to show it } #3100+ local_name more with different domains. El 16/2/22 a las 10:02, Aki Tuomi escribió: >> On 16/02/2022 07:30 Víctor Rubiella Monfort <vrubiella(a)cdmon.com> wrote: >> >> >> Hi all, >> I'm having problems with memory in config service. I increased >> vsz_limit to 10GB but continue with this errors when try to reload or >> restart dovecot: >> >> config: Panic: data stack: Out of memory when allocating 2147483688 bytes >> master: Error: service(config): command startup failed, throttling >> for 2 secs >> config: Fatal: master: service(config): child 5512 killed with signal >> 6 (core dumps disabled) >> >> Dovecot has a lot of certificates TLS configured (SNI) (about 3k), >> but if I check the size of all of them is aprox 170MB on disk.Why >> does it need so much memory to boot? Is normal? >> >> >> >> service config { >> vsz_limit = {{ vszlimit }} >> } > Hi! > > Can you send your doveconf -n output? > > Aki >

2 2

Index Corruption Problem with new VM Host - But Only With Replication Enabled
by Reuben Farrelly 21 Feb '22

21 Feb '22

Hi, I've recently migrated my two VMs across from Linode (who use KVM) onto a local VPS service (which also uses KVM). Since doing so I have started to see some strange problems with Dovecot relating to indexes and replication. I have copied the configuration files across from old host to new host. The kernel is the same - as this is Gentoo everything was rebuilt and installed from fresh, but with the same options (use flags). Even the Linux kernel is the same version with the exact same options (as is Dovecot). The filesystem is the same EXT4 with the same options too. Here is what is logged: Feb 18 15:20:41 tornado.reub.net dovecot: imap(reuben)<20031><d0yxIEPY3ROfxG3u>: Error: Mailbox INBOX: /home/reuben/Maildir/dovecot.index reset, view is now inconsistent Feb 18 15:20:41 tornado.reub.net dovecot: imap(reuben)<20031><d0yxIEPY3ROfxG3u>: Disconnected: IMAP session state is inconsistent, please relogin. in=146 out=1398 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 The trigger is the move/delete of an email. Just reading seems to be OK. But as soon as you move/delete an email this event occurs and is logged. The move fails on the first attempt (error is logged, client refreshes) but then if attempted again it succeeds. This error causes the clients to be thrown off and the client view refreshed which seems to require a redownload of everything. It is extremely disruptive to client access. The odd thing is that as soon as I disable replication by commenting out the mail_replica line, *all* of the index corruption messages and symptoms go away completely and I don't see this problem occur. As soon as I re-add it they come back. So it appears that replication at least is triggering the problem. Replication is imap1 -> imap2 and on the other host imap2 - imap1 The odd thing is that this never was a problem while the system was on Linode. I have removed all files on the remote and let dovecot re-replicate everything but this didn't help. I can go back to the VPS host and talk to them about it as I have an open ticket but from their perspective it looks like an application level problem, so there's not a lot for them to go on especially given everything else is working OK. Could the underlying host be playing a role in this? It seems unlikely given turning replication or or off causes the problem to appear or disappear. All clients are connecting to only the master of the two replication partners. Many have multiple concurrent sessions (eg my phone, and Thunderbird at the same time) but all are connecting to only one instance at a time. The second instance is only there for a failover scenario (update a DNS entry to failover). There is no NFS or any sort of sharing set up on the VMs. They are dedicated virtual disks. Can anyone give me any ideas how to troubleshoot this further or things to try? Some system details: # 2.3.18 (9dd8408c18): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.18 (0bc28b32) # OS: Linux 5.16.10-gentoo x86_64 Gentoo Base System release 2.8 # Hostname: tornado.reub.net auth_mechanisms = plain login auth_username_format = %Ln doveadm_password = # hidden, use -P to show it first_valid_uid = 1000 imap_client_workarounds = tb-lsub-flags tb-extra-mailbox-sep last_valid_uid = 1099 login_log_format_elements = user=<%u> auth-method=%m remote=%r local=%l %c %k mail_attribute_dict = file:%h/Maildir/dovecot-attributes mail_location = maildir:~/Maildir mail_plugins = notify replication 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 { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = failure_show_msg=yes %s driver = pam } plugin { mail_replica = tcp:imap2.reub.net:4814 replication_full_sync_interval = 2 hours sieve = file:~/sieve;active=~/.dovecot.sieve } postmaster_address = postmaster(a)reub.net protocols = imap lmtp sieve submission sieve recipient_delimiter = - service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = root } unix_listener replication-notify { mode = 0666 user = root } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0777 } } service doveadm { inet_listener { address = 2404:9400:2264:7200::143 port = 4813 ssl = yes } inet_listener { address = 2404:9400:2264:7200::143 port = 4814 ssl = no } user = root } service imap-login { inet_listener imap { port = 143 } } service lmtp { inet_listener lmtp { address = ::1 port = 24 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service managesieve-login { inet_listener sieve { address = 127.0.0.1 port = 4190 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } service submission-login { inet_listener submission { address = 103.4.234.81 2404:9400:2264:7200::587 port = 587 } } ssl_cert = </etc/ssl/dovecot/reub.net.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it submission_client_workarounds = whitespace-before-path submission_relay_host = localhost submission_relay_port = 587 submission_relay_trusted = yes userdb { driver = passwd result_success = continue-ok } protocol lmtp { mail_plugins = notify replication sieve } protocol lda { mail_plugins = notify replication sieve } protocol imap { imap_metadata = yes mail_max_userip_connections = 25 } Thanks, Reuben

2 2

dovecot-2.3-pigeonhole-0.5.18 : Freebsd Will not build
by Paul Kudla (Scom.ca Internet Services Inc.) 20 Feb '22

20 Feb '22

dovecot version : dovecot-2.3.14 freebsd 12.1 dovecot-2.3.14 built manually (no port build) : ./configure --with-pgsql currentconfig (dovecot-2.3-pigeonhole-0.5.18) : ./configure --with-dovecot=/usr/local/lib/dovecot Error when building : Screen Shot (color may help) Actual : libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../.. -I/usr/local/include/dovecot -I../../../.. -I../../../../src/lib-sieve -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -mfunction-return=keep -mindirect-branch=keep -I../../../.. -MT sieve-dict-script.lo -MD -MP -MF .deps/sieve-dict-script.Tpo -c sieve-dict-script.c -fPIC -DPIC -o .libs/sieve-dict-script.o sieve-dict-script.c: In function 'sieve_dict_script_open': sieve-dict-script.c:84:9: error: variable 'set' has initializer but incomplete type 84 | struct dict_op_settings set = { | ^~~~~~~~~~~~~~~~ sieve-dict-script.c:85:4: error: 'struct dict_op_settings' has no member named 'username' 85 | .username = dstorage->username, | ^~~~~~~~ sieve-dict-script.c:85:15: warning: excess elements in struct initializer 85 | .username = dstorage->username, | ^~~~~~~~ sieve-dict-script.c:85:15: note: (near initialization for 'set') sieve-dict-script.c:84:26: error: storage size of 'set' isn't known 84 | struct dict_op_settings set = { | ^~~ sieve-dict-script.c:88:31: warning: passing argument 3 of 'dict_lookup' from incompatible pointer type [-Wincompatible-pointer-types] 88 | (dscript->dict, &set, script->pool, path, &data_id, &error); | ~~~~~~^~~~~~ | | | pool_t {aka struct pool *} In file included from sieve-dict-script.c:8: /usr/local/include/dovecot/dict.h:102:15: note: expected 'const char *' but argument is of type 'pool_t' {aka 'struct pool *'} 102 | const char *key, const char **value_r, const char **error_r); | ~~~~~~~~~~~~^~~ sieve-dict-script.c:88:39: warning: passing argument 4 of 'dict_lookup' from incompatible pointer type [-Wincompatible-pointer-types] 88 | (dscript->dict, &set, script->pool, path, &data_id, &error); | ^~~~ | | | const char * In file included from sieve-dict-script.c:8: /usr/local/include/dovecot/dict.h:102:33: note: expected 'const char **' but argument is of type 'const char *' 102 | const char *key, const char **value_r, const char **error_r); | ~~~~~~~~~~~~~^~~~~~~ sieve-dict-script.c:87:8: error: too many arguments to function 'dict_lookup' 87 | ret = dict_lookup | ^~~~~~~~~~~ In file included from sieve-dict-script.c:8: /usr/local/include/dovecot/dict.h:101:5: note: declared here 101 | int dict_lookup(struct dict *dict, pool_t pool, | ^~~~~~~~~~~ sieve-dict-script.c:84:26: warning: unused variable 'set' [-Wunused-variable] 84 | struct dict_op_settings set = { | ^~~ sieve-dict-script.c: In function 'sieve_dict_script_get_stream': sieve-dict-script.c:126:9: error: variable 'set' has initializer but incomplete type 126 | struct dict_op_settings set = { | ^~~~~~~~~~~~~~~~ sieve-dict-script.c:127:4: error: 'struct dict_op_settings' has no member named 'username' 127 | .username = dstorage->username, | ^~~~~~~~ sieve-dict-script.c:127:15: warning: excess elements in struct initializer 127 | .username = dstorage->username, | ^~~~~~~~ sieve-dict-script.c:127:15: note: (near initialization for 'set') sieve-dict-script.c:126:26: error: storage size of 'set' isn't known 126 | struct dict_op_settings set = { | ^~~ sieve-dict-script.c:130:32: warning: passing argument 3 of 'dict_lookup' from incompatible pointer type [-Wincompatible-pointer-types] 130 | (dscript->dict, &set, dscript->data_pool, path, &data, &error); | ~~~~~~~^~~~~~~~~~~ | | | pool_t {aka struct pool *} In file included from sieve-dict-script.c:8: /usr/local/include/dovecot/dict.h:102:15: note: expected 'const char *' but argument is of type 'pool_t' {aka 'struct pool *'} 102 | const char *key, const char **value_r, const char **error_r); | ~~~~~~~~~~~~^~~ sieve-dict-script.c:130:45: warning: passing argument 4 of 'dict_lookup' from incompatible pointer type [-Wincompatible-pointer-types] 130 | (dscript->dict, &set, dscript->data_pool, path, &data, &error); | ^~~~ | | | const char * In file included from sieve-dict-script.c:8: /usr/local/include/dovecot/dict.h:102:33: note: expected 'const char **' but argument is of type 'const char *' 102 | const char *key, const char **value_r, const char **error_r); | ~~~~~~~~~~~~~^~~~~~~ sieve-dict-script.c:129:8: error: too many arguments to function 'dict_lookup' 129 | ret = dict_lookup | ^~~~~~~~~~~ In file included from sieve-dict-script.c:8: /usr/local/include/dovecot/dict.h:101:5: note: declared here 101 | int dict_lookup(struct dict *dict, pool_t pool, | ^~~~~~~~~~~ sieve-dict-script.c:126:26: warning: unused variable 'set' [-Wunused-variable] 126 | struct dict_op_settings set = { | ^~~ gmake[5]: *** [Makefile:461: sieve-dict-script.lo] Error 1 gmake[5]: Leaving directory '/usr/local/src/mail/dovecot-2.3-pigeonhole-0.5.18/src/lib-sieve/storage/dict' gmake[4]: *** [Makefile:426: all-recursive] Error 1 gmake[4]: Leaving directory '/usr/local/src/mail/dovecot-2.3-pigeonhole-0.5.18/src/lib-sieve/storage' gmake[3]: *** [Makefile:909: all-recursive] Error 1 gmake[3]: Leaving directory '/usr/local/src/mail/dovecot-2.3-pigeonhole-0.5.18/src/lib-sieve' gmake[2]: *** [Makefile:438: all-recursive] Error 1 gmake[2]: Leaving directory '/usr/local/src/mail/dovecot-2.3-pigeonhole-0.5.18/src' gmake[1]: *** [Makefile:763: all-recursive] Error 1 gmake[1]: Leaving directory '/usr/local/src/mail/dovecot-2.3-pigeonhole-0.5.18' gmake: *** [Makefile:622: all] Error 2 -- Happy Sunday !!! Thanks - paul Paul Kudla Scom.ca Internet Services <http://www.scom.ca> 004-1009 Byron Street South Whitby, Ontario - Canada L1N 4S3 Toronto 416.642.7266 Main 1.866.411.7266 Fax 1.888.892.7266

2 1

initial replication or clone?
by Joachim Lindenberg 19 Feb '22

19 Feb '22

Hello, I want to improve availability of my dovecot installation by implementing replication as outlined in https://wiki.dovecot.org/Replication. I am wondering whether I have to install an empty copy or whether it is also an option to clone the entire existing system and then configure replication, just to avoid the initial overhead. Any input? Thanks, Joachim

1 0