- dovecot - dovecot.org

sieve-filter not respecting :create flag of fileinto
by David Arroyo 16 Mar '22

16 Mar '22

Hello, I recently significantly modified my sieve rules for filing mailing list posts in my Fastmail inbox. The rules contain a few rules that file mail like so: fileinto :create ml.${5}${4}{$3}{$2}{$1}; # reversed list-id The rules work as expected on delivery to fastmail. Because these rules only run on delivery, and the new folder layout is different from my existing one, I want to apply the rules to my existing mail. I thought dovecot's `sieve-filter` command, together with the `imapc` storage backend, would be a good way to do that, so I moved some existing mail into a folder, `sieve-test`, and ran the following: sieve-filter -x '+editheader +mailbox' -W -e rules.sieve sieve-test However, what I see is that sieve-filter fails when the new directory does not exist. Here is some example (redacted) output: Info: imapc(imap.fastmail.com:993): Connected to x.x.x.x:993 (local x.x.x.x) error: msgid=<xxx>: fileinto action: failed to store into mailbox 'ml.gnu.guix-devel': Mailbox does not exist. sieve-filter(me): Info: sieve: msgid=<xxx>: left message in mailbox 'sieve-test' error: sieve script execution failed for this message; message left in source mailbox. sieve-filter(me): Info: sieve: msgid=<yyy>: fileinto action: stored mail into mailbox 'ml.9fans.9fans' My config looks like this: protocols = none mail_location = imapc: namespace { inbox = yes separator = . } imapc_host = imap.fastmail.com imapc_port = 993 imapc_ssl = imaps imapc_user = $username If this is a bug in sieve-filter I'd be happy to try and fix it, but I'm reaching out here first to see if this is expected behavior or a misconfiguration on my part. Thanks for any help, David

2 4

mdbox_rotate_size recommendation / performance
by Lucas Rolff 15 Mar '22

15 Mar '22

Hi guys, When using mdbox under Dovecot, the mdbox_rotate_size setting defaults to 10 megabyte - from a performance point of view if using spinning drives does this matter whether one goes for e.g. 2MB versus 10MB, especially in the combination with compression. Does anyone have any performance data regarding it’s size, and what’s a decent trade-off between limiting IOPS required by the drive versus the sequential read/write speeds. Any pointers would be awesome! Thanks in advance

1 0

AntiVirus in Maildir
by Masakazu Hirose 15 Mar '22

15 Mar '22

Hi all, I run a mail server on Maildir. Does Dovecot work correctly if I delete the mail files stored in Maildir? Do I need to run the doveadm command? I want to run a virus scan on Maildir. When a virus is detected, the mail file is deleted without notifying Dovecot. I assumed this was incorrect behavior for Dovecot. Please help me when someone has time. Thanks, Masa

4 5

allow_nets equivalent for all users?
by Bryan K. Walton 14 Mar '22

14 Mar '22

Hi, It is my understanding that allow_nets is a field that gets used in a password database, and therefore is a per-user setting. Is there an equivalent method for defining allowed network(s) for ALL users? In other words, a single setting that applies to every user? Thanks, Bryan

2 4

Possible bug interaction between Dovecot and Thunderbird 98/99 email client
by Arthur Koziol 11 Mar '22

11 Mar '22

Hi Dovecot devs, My name is Arthur. I'm a volunteer with Mozilla and am working with a user who's having some odd issues with his Thunderbird email client. I'm reaching out to you folks because he's using an at-home IMAP setup with Dovecot. It's not 100% clear if his setup is polling his GMail accounts and then pulling everything to his Dovecot setup but if there's any interesting in jumping into the bug we're trying to help this user with, feel free to browse the bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1726319 I asked the user if he's reached out to the Dovecot devs yet but he's not replied. We're not sure if this is a Dovecot / setup issue, a Thunderbird issue or something in between but we could use some other eyes and ideas of what to check for this user if you guys have a couple seconds to take a look. Thanks for reading. best, Arthur

1 0

Dovecot High Availability ?
by White, Daniel E. (GSFC-770.0)[NICS] 11 Mar '22

11 Mar '22

Are there any current, free high availability strategies for Dovecot ?

2 1

Can't create viable password hashes
by David Griffith 11 Mar '22

11 Mar '22

I recently discovered that I can no longer create viable password hashes for use in /etc/dovecot/dovecot.passwd. So far, I've been using the following command done by root: doveadm_cmd pw -s SHA512-CRYPT -u joe -p mypassword This creates something that looks legit, but dovecot won't accept it. I've been using my own solution for allowing users to change their dovecot passwords (https://gitlab.com/DavidGriffith/dovepasswd) and this is how it generates the hashes. Is there a better way of going about this? -- David Griffith dave(a)661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?

1 0

XOAUTH2 submission - "500 5.5.2 Line too long"
by Rosario Esposito 08 Mar '22

08 Mar '22

Hello, I setup a dovecot submission server, using xoauth2 authentication. My roundcube webmail points to dovecot submission. In roundcube smtp logs, I see: [08-Mar-2022 15:47:16 +0100]: <qjonb57c> Recv: 250-PIPELINING [08-Mar-2022 15:47:16 +0100]: <qjonb57c> Recv: 250 XCLIENT ADDR PORT PROTO HELO LOGIN SESSION TTL TIMEOUT FORWARD [08-Mar-2022 15:47:16 +0100]: <qjonb57c> Send: AUTH XOAUTH2 dXNlcj1yZXNwb3NpdAFhdXRoPWJlYXJlci<<<...*very long base64 string*....>>> [08-Mar-2022 15:47:16 +0100]: <qjonb57c> Recv: 500 5.5.2 Line too long [08-Mar-2022 15:47:16 +0100]: <qjonb57c> Send: ****** [4] [08-Mar-2022 15:47:16 +0100]: <qjonb57c> Recv: 221 2.0.0 Bye And, in dovecot logs I found: Mar 8 15:47:17 ### dovecot[97376]: submission-login: Debug: smtp-server: conn 172.18.6.100:38658 [1]: command EHLO: 250 reply: Sent: 250-###.<#####> 8BITMIME AUTH PLAIN OAUTHBEARER XOAUTH2 BURL imap CHUNKING ENHANCEDSTATUSCODES SIZE PIPELINING XCLIENT ADDR PORT PROTO HELO LOGIN SESSION TTL TIMEOUT FORWARD Mar 8 15:47:17 ### dovecot[97376]: submission-login: Debug: smtp-server: conn 172.18.6.100:38658 [1]: command EHLO: Finished Mar 8 15:47:17 ### dovecot[97376]: submission-login: Debug: smtp-server: conn 172.18.6.100:38658 [1]: command EHLO: Destroy Mar 8 15:47:17 ### dovecot[97376]: submission-login: Debug: smtp-server: conn 172.18.6.100:38658 [1]: command EHLO: 250 reply: Destroy Mar 8 15:47:17 ### dovecot[97376]: submission-login: Debug: smtp-server: conn 172.18.6.100:38658 [1]: Trigger output Mar 8 15:47:17 ### dovecot[97376]: submission-login: Debug: smtp-server: conn 172.18.6.100:38658 [1]: No more commands pending Mar 8 15:47:17 ### dovecot[97376]: submission-login: Debug: smtp-server: conn 172.18.6.100:38658 [1]: Sending replies Mar 8 15:47:17 ### dovecot[97376]: submission-login: Debug: smtp-server: conn 172.18.6.100:38658 [1]: No more commands pending Mar 8 15:47:17 ### dovecot[97376]: submission-login: Debug: smtp-server: conn 172.18.6.100:38658 [1]: Client sent invalid command: Command line is too long Apparently, the problem came out after upgrading from dovecot 2.3.17 to 2.3.18 Any ideas ?

3 2

Replicator Issues on Large Mail Boxes
by Paul Kudla (Scom.ca Internet Services Inc.) 08 Mar '22

08 Mar '22

Ok running : freebsd-12.1 dovecot-2.3.18.current dovecot-2.3-pigeonhole-0.5.18.current simply put replication works fine on smaller email boxes without issues. dsync also works when run manually, longest sync is 60 secords or so when using dsync so need replicator bumped up ? i get the fact that the file locking issue relative since a larger mailbox will take longer to replicate when an email comes in ? mail18 03-05 18:05:51 {dovecot} [15799] (872623573) doveadm(keith(a)elirpa.com)<32249><GnS3M53sI2L5fQAAz1jc/w>: Error: Couldn't lock /data/dovecot/users/elirpa.com/keith(a)elirpa.com//tmp/.dovecot-sync.lock: fcntl(/data/dovecot/users/elirpa.com/keith@elirpa.com//tmp/.dovecot-sync.lo…, write-lock, F_SETLKW) locking failed: Timed out after 30 seconds (WRITE lock held by pid 31519) so what i need is where fcntl is setting a 30 second timeout for replication (i have adjust all the others in the src code) simply put replicator fails and retries and keeps failing which is understandable as it probably needs a little more time ? # sync.users carol(a)scom.ca none 00:02:51 08:16:34 - y nick(a)elirpa.com low 02:45:17 09:28:32 - y keith(a)elirpa.com none 02:30:13 09:28:32 - y paul(a)scom.ca high 02:45:17 09:28:32 - y ed(a)scom.ca none 02:34:34 09:28:32 - y ed.hanna(a)dssmgmt.com high 02:45:17 09:28:32 - y i found under /programs/src/mail/dovecot-2.3.18.current/src/lib file-lock.c struct flock fl; fl.l_type = lock_type; fl.l_whence = SEEK_SET; fl.l_start = 0; fl.l_len = 0; ret = fcntl(fd, timeout_secs != 0 ? F_SETLKW : F_SETLK, &fl); if (timeout_secs != 0) { alarm(0); file_lock_wait_end(path); } if (ret == 0) break; if (timeout_secs == 0 && (errno == EACCES || errno == EAGAIN)) { /* locked by another process */ *error_r = t_strdup_printf( "fcntl(%s, %s, F_SETLK) locking failed: %m " "(File is already locked)", path, lock_type_str); return 0; } if (err_is_lock_timeout(started, timeout_secs)) { errno = EAGAIN; *error_r = t_strdup_printf( "fcntl(%s, %s, F_SETLKW) locking failed: " "Timed out after %u seconds%s", path, lock_type_str, timeout_secs, file_lock_find(fd, set->lock_method, lock_type)); return 0; } *error_r = t_strdup_printf("fcntl(%s, %s, %s) locking failed: %m", path, lock_type_str, timeout_secs == 0 ? "F_SETLK" : "F_SETLKW"); if (errno == EDEADLK && !set->allow_deadlock) { i_panic("%s%s", *error_r, file_lock_find(fd, set->lock_method, lock_type)); } return -1; #endif -- Happy Saturday !!! 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

Is fts_autoindex_exclude options working fine?
by Alessio Cecchi 07 Mar '22

07 Mar '22

Hi, we have some trouble with Solr ad FTS engine. Solr have some spike of load and responding slow when an user expunge or append a message. fts_autoindex is set to "yes". So I add to 90-plugin.conf these options: fts_autoindex_exclude = Drafts fts_autoindex_exclude2 = Spam fts_autoindex_exclude3 = Trash fts_autoindex_exclude4 = Sent or fts_autoindex_exclude = \Drafts fts_autoindex_exclude2 = \Junk fts_autoindex_exclude3 = \Trash fts_autoindex_exclude4 = \Sent But the problem is still present. Here some example of logs when users have timeout in their email client, specially when saving in Drafts automatically: Mar 7 12:21:37 pop01 dovecot: imap(user1(a)company1.com) session=<flNVCZ/ZcO5dPnGT>: Warning: Maildir /home/vmail/domains/company1.com/user1/Maildir/.Drafts: Synchronization took 119 seconds (0 new msgs, 0 flag change attempts, 1 expunge attempts) Mar 7 12:21:37 pop01 dovecot: imap(user1(a)company1.com) session=<flNVCZ/ZcO5dPnGT>: Disconnected: Connection closed (UID EXPUNGE finished 118.715 secs ago) in=77617 out=679511 deleted=1 expunged=1 autoexpunged=0 trashed=0 appended=2 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Mar 7 12:21:52 pop02 dovecot: imap(user2(a)company2.net) session=<B9NNCZ/Z+uC5Ydlv>: Warning: Maildir /home/vmail/domains/company2.net/user2/Maildir/.Trash: Synchronization took 149 seconds (0 new msgs, 0 flag change attempts, 1 expunge attempts) Mar 7 12:21:52 pop02 dovecot: imap(user2(a)company2.net) session=<B9NNCZ/Z+uC5Ydlv>: Disconnected: Logged out in=2407 out=7025 deleted=0 expunged=0 autoexpunged=1 trashed=0 appended=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Is my fts_autoindex_exclude wrong or there are some limits with this option? Here the relevant part of 15-mailboxes.conf namespace inbox { inbox = yes location = mailbox Archive { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } mailbox virtual/All { comment = All my messages special_use = \All } prefix = separator = / } Thanks -- Alessio Cecchi Postmaster @http://www.qboxmail.it https://www.linkedin.com/in/alessice

1 0

doveadm complains about virtual namespace
by Roberto Sanchez 07 Mar '22

07 Mar '22

Hi, I’ve setup my server __user__nd mail sending/receiving is all working without issue. However, a cron script that cleans up the Junk folder and runs: doveadm expunge -A mailbox Junk savedbefore 60d gives out the following error: doveadm(__user__(a)example.com): Error: Namespace 'Virtual.': Unknown mail storage driver virtual I don’t know if I have a configuration issue or if I have to load the virtual plugin at some other point in the config? I would appreciate any help. This is the output with debug enabled, and further below is my dovecot -n output (I’ve changed the user name to __user__ and the domain to example.com) 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: Skipping module doveadm_quota_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so: undefined symbol: quota_user_module (this is usually intentional, so just ignore this message) 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) Debug: auth-master: userdb list: Started listing users (user_mask=) Debug: auth-master: conn unix:/var/run/dovecot/auth-userdb: Connecting Debug: auth-master: conn unix:/var/run/dovecot/auth-userdb: Client connected (fd=10) Debug: auth-master: userdb list: Returned username: __user__(a)example.com doveadm(__user__(a)example.com)<1068593><>: Debug: auth-master: userdb lookup(__user__(a)example.com): Started userdb lookup doveadm(__user__(a)example.com)<1068593><>: Debug: auth-master: conn unix:/var/run/dovecot/auth-userdb: Connecting doveadm(__user__(a)example.com)<1068593><>: Debug: auth-master: conn unix:/var/run/dovecot/auth-userdb: Client connected (fd=12) doveadm(__user__(a)example.com)<1068593><>: Debug: auth-master: userdb lookup(__user__(a)example.com): auth USER input: __user__(a)example.com maildir=example.com/__user__/ home=/var/mail/vhosts/example.com/__user__ uid=5000 gid=5000 doveadm(__user__(a)example.com)<1068593><>: Debug: auth-master: userdb lookup(__user__(a)example.com): Finished userdb lookup (username=__user__(a)example.com maildir=example.com/__user__/ home=/var/mail/vhosts/example.com/__user__ uid=5000 gid=5000) doveadm(__user__(a)example.com)<1068593><>: Debug: Added userdb setting: plugin/maildir=example.com/__user__/ doveadm(__user__(a)example.com): Debug: Effective uid=5000, gid=5000, home=/var/mail/vhosts/example.com/__user__ doveadm(__user__(a)example.com): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/var/mail/vhosts/example.com/__user__/Maildir doveadm(__user__(a)example.com): Debug: maildir++: root=/var/mail/vhosts/example.com/__user__/Maildir, index=, indexpvt=, control=, inbox=/var/mail/vhosts/example.com/__user__/Maildir, alt= doveadm(__user__(a)example.com): Debug: Namespace virtual: type=private, prefix=Virtual., sep=., inbox=no, hidden=no, list=yes, subscriptions=yes location=virtual:/var/mail/virtual:INDEX=/var/mail/vhosts/example.com/__use… doveadm(__user__(a)example.com): Error: Namespace 'Virtual.': Unknown mail storage driver virtual > dovecot -n # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.16.3-x86_64-linode152 x86_64 Ubuntu 20.04.4 LTS # Hostname: bender.example.com auth_mechanisms = plain login auth_username_format = %u mail_location = maildir:%h/Maildir mail_privileged_group = vmail 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 Archive { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe autoexpunge = 30 days special_use = \Trash } prefix = } namespace virtual { list = yes location = virtual:/var/mail/virtual:INDEX=/var/mail/vhosts/%d/%n/virtual mailbox All { auto = subscribe comment = All my messages special_use = \All } mailbox Flagged { auto = subscribe comment = All my flagged messages special_use = \Flagged } prefix = Virtual. separator = . subscriptions = yes } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = file:%h/sieve;active=%h/dovecot.sieve sieve_before = /etc/dovecot/sieve/ } postmaster_address = postmaster at example.com protocols = imap lmtp sieve service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail } user = dovecot } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { address = localhost port = 4190 } } service stats { unix_listener stats-reader { group = www-data mode = 0660 user = www-data } unix_listener stats-writer { group = www-data mode = 0660 user = www-data } } ssl = required 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 ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } userdb { args = uid=vmail gid=vmail home=/var/mail/vhosts/%d/%n driver = static } protocol lmtp { mail_plugins = " sieve virtual" postmaster_address = postmaster(a)example.com } protocol lda { mail_plugins = " virtual" } protocol imap { mail_plugins = " virtual" } protocol sieve { mail_plugins = virtual }

3 2

Pigeonhole Sieve: Vacation Extension issue
by Zakaria 05 Mar '22

05 Mar '22

Hi there, I wondered if there is any one who can help me out on this issue. I tried to setup the vacation extension, and it works fine if the Return-Path header and Envelope-From field in Received wasn’t rewritten and contains the actual sender email address which the vacation extension will retrieve from and reply to. Given, I’ve rewritten both headers, to modify TLS connection mailed-by address and I had to revert back to get the vacation extension working, I wondered if there is anyone know how to modify the Sieve settings in Dovecot config for LMTP/LDA and Sieve, or Sieve script rules to retrieve sender email address from From header or any other specific header? If it's not possible, it would be so good if its implemented, it doesn’t seem to be a hard task, so please log this as a feature request. With thanks. Zakaria. Btw, all my prayers and solidarity I send out to Ukraine, Russia and the rest of Europe, and the world, and the sick from this and COVID and alike. We should value one another, Seriously, Putin must urgently stop giving to who want destruction and harm in Europe and manipulating behind the scene such devil affair and leading to this very sickening and unacceptable horror. Palestine deserve justice than preoccupying the world with creating more injustices.

1 0

doveadm quota get hangs for 60 seconds (some analysis done)
by jaroslav＠thinline.cz 05 Mar '22

05 Mar '22

Hello, I encountered somewhat strange behaviour when running doveadm quota get with wildcard username (all usernames are in user@domain format): doveadm -f pager quota get -u *(a)example.domain The command hangs for 60 seconds before returning its result. I tried to dig into the issue a bit using strace and found out that there seems to be some kind of communication mismatch between Dovecot processes. Here is what I found - sorry for the wall of text, strace outputs tend to be large, I tried to reduce them as much as possible. I also tried to draw some conclusions below. This is from strace in the doveadm process, it connects to auth-userdb and requests list of users 1646473083.263021 connect(10, {sa_family=AF_UNIX, sun_path="/run/dovecot/auth-userdb"}, 110) = 0 1646473083.263627 write(10, "VERSION\t1\t0\nLIST\t1\tuser=*(a)example.domain\n", 47) = 47 1646473083.263807 read(10, "VERSION\t1\t1\nSPID\t30012\n", 8192) = 23 1646473084.188212 read(10, "LIST\t1\tuser1@notthat.domain\nLIST\t1\tuser2@another.domain\nLIST\t1\tuser3@also.not\nLIST\t1\t.... This list goes on, the server has over 10000 user accounts. (As a side note, this behaviour struck me as strange - I would expect that the result would be filtered by the server side of the connection, only listing users that match the requested wildcard. I don't know anything about Dovecot internals though, so this might be perfectly normal.) At some point the returned data contain users doveadm is interested in (ie. users that match the wildcard) and requests their information from other Dovecot services, this is an excerpt for a dict service: 1646473084.224608 connect(13, {sa_family=AF_UNIX, sun_path="/run/dovecot/dict"}, 110) = 0 1646473084.225617 write(13, "H2\t2\t0\trelevantuser(a)example.domain\tsqldomainquota\n", 50) = 50 No data are read from FD 10 during this time. When all users are queried, reading from FD 10 resumes 1646473084.274405 read(10, "ifth.domain\nLIST\t1\tuser987(a)domain.six\nLIST\t1\t... At this point though, the process gets stuck: 1646473084.274514 epoll_wait(11, [], 1, 0) = 0 1646473084.274555 read(10, 0x5620076d79dd, 6035) = -1 EAGAIN (Resource temporarily unavailable) 1646473084.274601 epoll_wait(11, [{EPOLLIN, {u32=124338208, u64=94695563280416}}], 1, 155000) = 1 It resumes after 60 seconds, reads some more users and then receives string "DONE" 1646473144.287149 read(10, "LIST\t1\tuser456@domain.seven\nLIST\t1\tuser123@domain.e8\nLIST\t1\tuser7865@dom.nine\n", 6035) = 99 1646473144.287149 read(10, "LIST\t1\t ... ", 5936) = 82 ... 1646473144.294373 epoll_wait(11, [{EPOLLIN, {u32=124338208, u64=94695563280416}}], 1, 155000) = 1 1646473144.307846 read(10, "DONE\t1\t\n", 1611) = 8 Note that at this point the read syscall is no longer trucated. As opposed to reads above, which amounted to 8kB blocks, these are reading few addresses at a time. After the "DONE" string is received, there is no more communication with other Dovecot processes, doveadm prints out results to the console and terminates. Next I investigated the auth process. 1646473083.263121 accept(11, {sa_family=AF_UNIX}, [28->2]) = 23 1646473083.263181 getsockname(23, {sa_family=AF_UNIX, sun_path="/run/dovecot/auth-userdb"}, [28->27]) = 0 1646473083.263690 read(23, "VERSION\t1\t0\nLIST\t1\tuser=*(a)example.domain\n", 1024) = 47 1646473083.263939 connect(24, {sa_family=AF_UNIX, sun_path="auth-worker"}, 110) = 0 1646473083.264228 write(24, "VERSION\tauth-worker\t1\t0\nDBHASH\t1234567890abcdef1234567890abcdef\tfedcba0987654321fedcba0987654321\n", 97) = 97 1646473083.264271 writev(24, [{iov_base="1\t", iov_len=2}, {iov_base="LIST\t1\tuser=*(a)example.domain\tservice=\toriginal-username", iov_len=61}, {iov_base="\n", iov_len=1}], 3) = 64 1646473084.187567 read(24, "1\t*\tuser1(a)notthat.domain\n1\t*\t... 1646473084.187977 write(23, "LIST\t1\tuser1(a)notthat.domain\nLIST\t1\t Reads and writes alternate until these syscalls: 1646473084.238938 read(24, " ... \n1\tOK\n", 8167) = 5354 1646473084.239108 write(23, "LIST\t1\t ... , 51224) = -1 EAGAIN (Resource temporarily unavailable) 1646473084.239536 write(23, "LIST\t1\t ... , 51224) = -1 EAGAIN (Resource temporarily unavailable) From the timing this looks like a kernel buffer for the connection is filled because the other side is not reading the data. This matches strace from doveadm which is at this point reading information about quotas from dict service (timestamp 1646473084.225617.) Auth process seems to react to this by putting the FD on epoll list and then it goes to handle other connections. FD 24 is removed from the epoll list at the same time: 1646473084.239926 epoll_ctl(14, EPOLL_CTL_ADD, 23, {EPOLLOUT|EPOLLERR|EPOLLHUP, {u32=109861328, u64=94566699784656}}) = 0 1646473084.239980 epoll_ctl(14, EPOLL_CTL_DEL, 24, 0x7ffca3a9ae2c) = 0 FD 23 becomes writable relatively quickly, pending data is written to it and read from FD 24 is attempted with no data available: 1646473084.270224 epoll_ctl(14, EPOLL_CTL_DEL, 23, 0x7ffca3a9ae5c) = 0 1646473084.270271 write(23, "LIST\t1\t ... , 51224) = 51224 1646473084.270620 epoll_ctl(14, EPOLL_CTL_ADD, 24, {EPOLLIN|EPOLLPRI|EPOLLERR|EPOLLHUP, {u32=109860944, u64=94566699784272}}) = 0 1646473084.270712 read(24, 0x5602069198e3, 2813) = -1 EAGAIN (Resource temporarily unavailable) Again, nothing else happens for 60 seconds until FD 24 signals what I presume is a connection close attempt. Note that there was no data read from FD 24 but when the "SHUTDOWN" string arrives from it, auth process starts writing items to FD 23, one by one. 1646473144.286936 read(24, "SHUTDOWN\n", 2813) = 9 1646473144.287003 write(23, "LIST\t1\tuser456(a)domain.seven\n", 29) = 29 1646473144.287059 write(23, "LIST\t1\tuser123(a)domain.e8\n", 31) = 31 1646473144.287103 write(23, "LIST\t1\tuser7865(a)dom.nine\n", 39) = 39 There are multiple user databases, I assume the following is a lookup from the others: 1646473144.294256 writev(24, [{iov_base="2\t", iov_len=2}, {iov_base="LIST\t2\tuser=*(a)example.domain\tservice=\toriginal-username", iov_len=61}, {iov_base="\n", iov_len=1}], 3) = 64 1646473144.294379 read(24, 0x5602069198ec, 2804) = -1 EAGAIN (Resource temporarily unavailable) 1646473144.300490 read(24, "2\tOK\n", 2804) = 5 1646473144.300556 writev(24, [{iov_base="3\t", iov_len=2}, {iov_base="LIST\t3\tuser=*(a)example.domain\tservice=\toriginal-username", iov_len=61}, {iov_base="\n", iov_len=1}], 3) = 64 1646473144.300653 read(24, 0x5602069198f1, 2799) = -1 EAGAIN (Resource temporarily unavailable) 1646473144.307687 read(24, "3\tOK\n", 2799) = 5 1646473144.307751 write(23, "DONE\t1\t\n", 8) = 8 1646473144.307944 close(24) = 0 1646473144.308092 read(23, "", 977) = 0 1646473144.308185 close(23) = 0 I also looked into the auth-userdb (auth -w) service, it seems to mirror what happens in the auth process: [pid 22387] 1646473083.407660 accept(7, <unfinished ...> [pid 22387] 1646473083.407767 <... accept resumed>{sa_family=AF_UNIX}, [28->2]) = 17 [pid 22387] 1646473084.187096 write(17, "1\t*\tuser1(a)notthat.domain\n1\t*\t [pid 22387] 1646473084.233120 write(17, "1\tOK\n", 5 <unfinished ...> [pid 22387] 1646473084.233577 epoll_ctl(9, EPOLL_CTL_ADD, 17, {EPOLLIN|EPOLLPRI|EPOLLERR|EPOLLHUP, {u32=659542480, u64=94356796068304}} <unfinished ...> [pid 22387] 1646473084.234006 read(17, <unfinished ...> [pid 22387] 1646473084.234254 <... read resumed>0x55d12753b7d1, 8031) = -1 EAGAIN (Resource temporarily unavailable) And after 60 seconds: [pid 22387] 1646473144.286843 write(17, "SHUTDOWN\n", 9 <unfinished ...> At which point the other two requests come in and are replied to. As I said above, I don't know anything about Dovecot internals but from I can gather from these outputs, all data are exchanged correctly and nothing gets stuck reading them from a permanent storage or alike. This bug doesn't manifest every time but seems to be fairly deterministic in that it always triggers for some domains but not for others. From what I've noticed, this affected domain receives all its users in single 8k read in the doveadm process, which in turns triggers (relatively) lengthy lookups and forces the auth process to put more writes on hold (at timestamp 1646473084.239108) Is it possible that when this happens, the "OK" string received from auth-userdb process (timestamp 1646473084.238938) is overlooked and auth process is waiting for more data from auth-userdb while auth-userdb waits for another request? The server itself runs Dovecot 1:2.3.13+dfsg1-2 from Debian repository on amd64. Output from dovecot --version is 2.3.13 (89f716dc2). As far as I can see, nothing indicates this is a performance problem related to insufficient hardware - server runs at 25% CPU utilization average, Pressure Stall Information reports average of 0.5% for CPU, 1% for I/O. System memory used is 10 out of 64GB. As far as I can see, no Dovecot process becomes CPU-bound when doveadm is running. I tried some web search but found nothing related to this. For our purposes, this issue has a relatively simple workaround - using doveadm quota get on specific usernames instead of the wildcard one. Since this might be an issue with a relatively easy fix for someone who knows where to look, I decided to post this bug report anyway. If needed, I should be able to test patches that apply cleanly to Debian sources and compile with dpkg-buildpackage. Thanks

1 0

Dupliate-ish email search?
by ＠lbutlr 04 Mar '22

04 Mar '22

I'm mulling over writing some code to find emails in a maildir that are duplicates, ish. That is to say that sometimes the same message doesn't quite show up as an exact match. Like some ad company may send you three identical messages, except they aren't actually EXACTLY identical, the message-IDs are different, and may the to address quoted part is different, so normal duplicate finders fail to find them. Before I start, is this a solved problem? -- I thought that they were angels, but to my surprise, we climbed aboard their starship, we headed for the skies.

3 2

Issue in 2.3.18 with fts_header_excludes/includes
by Alessio Cecchi 03 Mar '22

03 Mar '22

Hi, I'm still doing some test with fts-flatcurve, after updating to 2.3.18 I enabled: fts_header_excludes = * fts_header_includes = From To Cc Bcc Subject Message-ID but when I try to re-index all messages with FTS flatcurve the fts-flatcurve/ folder inside the Maildir/ become huge. Taking for example a Maildir with cur folder of 1.1G the related fts-flatcurve folder passed from 140M to 2.2G. After remove fts_header_excludes/includes config options, and re-index all messages, the fts-flatcurve/ size return to normal size. Is an issue? Thanks -- Alessio Cecchi Postmaster @http://www.qboxmail.it https://www.linkedin.com/in/alessice

1 1

Does disabling POP3 just mean removing it from the `protocols` list?
by Sean McBride 02 Mar '22

02 Mar '22

Hi all, Hopefully a simple question. If I want to disable POP3 support (because everyone is using IMAP anyway), it is just a matter of removing `pop3` from the `protocols` setting in dovecot.conf? Are there side effects or other considerations I should be aware of? Thanks, Sean

7 9

multiple doveadm ports?
by Joachim Lindenberg 02 Mar '22

02 Mar '22

Hello, I am trying to add another doveadm listener but am struggling with that. The primary reason is that I want to enable replication between two systems and want the replication to be encrypted using TLS. However there are also other doveadm clients locally that are not using TLS and I don´t want to touch all of them. I tried to define something like service doveadm { inet_listener { port = 2425 } inet_listener { port = 2426 ssl = true } } But didn´t get that to work. Is that not possible? I also tried service doveadm { inet_listener { port = 2425 } inet_listener http { port = 2426 ssl = yes } } but then I failed with plugin { mail_replica = https:dove2.example.com:2426 } Can someone please share what is supported and what not, or any pointer to documentation that does? Thanks a lot! Regards, Joachim

2 4

Apple Mail behaviour: can not create sub-folders
by Joseph Tam 02 Mar '22

02 Mar '22

One of my Apple Mail users recently complained his mail reader couldn't create sub-folders -- he could only create top-level folders. Playing around with this, I discovered that I could create folders ( as opposed to mialboxes) *if* I specified mailbox name with a trailing slash. Has anyone come across this? Is this related to https://doc.dovecot.org/configuration_manual/mail_location/mbox/mboxchildfo… ? Joseph Tam <jtam.home(a)gmail.com>

2 2

Re: dovecot Digest, Vol 212, Issue 56
by Korehicom 01 Mar '22

01 Mar '22

1 0

Custom Authentication Method
by Matthew R 01 Mar '22

01 Mar '22

Hi guys, we're using Dovecot/Postfix here for our mail system. I'd like to switch the `passdb` authentication on Dovecot from PAM over to a custom implementation. We'd prefer to have some sort of script check the password with an external IAM provider via HTTP. Is there any way we can accomplish this? The idea is to have Dovecot somehow call a script or send a username/password to some service, which checks the username/password against the identity provider and returns a "yes/no" back to Dovecot. `checkpassword` seems like it may work but I see no documentation on its API. Matthew R, AD, FSEN, FSO, FSCR Chief Director of Engineering & Chairman of the Board of Directors Library of Code sp-us matthew(a)staff.libraryofcode.org

3 2

General Locking & Replication Issues
by Paul Kudla (Scom.ca Internet Services Inc.) 01 Mar '22

01 Mar '22

Ok I am running two dovecot servers and feel pretty close to getting things resolved config wise there are however 2 or 3 issues that all seem to be related i have enclosed FULL config files for both mail18.scom.ca & mail19.scom.ca I have a private network that is used for the replication (10.221.0.0/24) - port 12345 is blocked by pf firewall from outside. I am running freebsd 12.1 and built one server and then raid copied it to the second (mail19) so all the ports / builds etc are identical I did start with dovecot-2.3.14 but pigeonhole would not build on freebsd (thanks for that advice / reply )until upgrade to dovecot-2.3.18 dovecot-2.3.18 was built and installed on both servers along with a good build (freebsd build error was fixed after upgrading) dovecot-2.3-pigeonhole-0.5.18 please note that the second mailserver (mail19) is on an nfs share dedicated to the server (i am awaiting sdram drives to replace this issue) but since i am getting errors on both servers i feel nfs share is not the issue (and yes i enabled dlock) mail18 is on normal sdram drives (more of an fyi as i dont think this is the issue) neither mail server is connected to the other in any kind of a shared way - other then replication postfix should be delivering via : pipe -n dovecot -t unix flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/deliver -f ${sender} -d ${recipient} Replication only works properly at startup (ie the mail boxes do sync), afterwhich nothing seems to trigger the differences between the servers to update (notify i believe) manually running : [05:04:46] mail18.scom.ca [root:0] /usr/local/etc/dovecot # doveadm sync -u paul(a)scom.ca remote:10.221.0.19 & [05:21:18] mail19.scom.ca [root:0] /usr/local/etc/dovecot # doveadm sync -u paul(a)scom.ca remote:10.221.0.18 does seem to work but with mixed results. I also included postfix main.cf & master.cf as well as some googling has indicated the file locking may be on the postfix side ?? Also more then happy to donate just can not figure out how ??? so that being said : General logging errors are as follows ? [04:46:43] peer1.scom.ca [paul:0] /home/paul ## log dovecot rror Filtering by : dovecot & rror mail18 02-28 04:46:58 {dovecot} [30374] (859753649) doveadm(ed(a)scom.ca)<30486><SUtDJMGZHGIWdwAAz1jc/w>: Error: write(<local>) failed: Timed out after 60 seconds mail19 02-28 04:47:00 {dovecot} [22194] (859753669) doveadm(paul(a)scom.ca)<22219><KQzDNbyZHGLLVgAA0dxyZQ>: Error: write(<local>) failed: Timed out after 60 seconds mail18 02-28 04:47:05 {dovecot} [30374] (859753724) doveadm(ed.hanna(a)dssmgmt.com)<30484><0dYbI8G ZHGIUdwAAz1jc/w>: Error: write(<local>) failed: Timed out after 60 seconds mail18 02-28 04:47:14 {dovecot} [30374] (859753799) doveadm(paul(a)scom.ca)<30485><W/KsI8GZHGIVdwAAz1jc/w>: Error: write(<local>) failed: Timed out after 60 seconds mail18 02-28 04:47:57 {dovecot} [30374] (859754250) doveadm(paul(a)paulkudla.net)<30676></v6tIASaH GLUdwAAz1jc/w>: Error: write(<local>) failed: Timed out after 60 seconds mail18 02-28 04:49:05 {dovecot} [30374] (859754939) doveadm(keith(a)elirpa.com)<30675><aasfIASaHGL TdwAAz1jc/w>: Error: write(<local>) failed: Timed out after 60 seconds mail19 02-28 04:54:45 {dovecot} [22194] (859759457) doveadm(paul(a)paulkudla.net)<22533><m1NpN4GbH GIFWAAA0dxyZQ>: Error: write(<local>) failed: Timed out after 60 seconds mail19 02-28 04:55:07 {dovecot} [22194] (859759868) doveadm(ed(a)scom.ca)<22535><UrLTOYGbHGIHWAAA0dxyZQ>: Error: write(<local>) failed: Timed out after 60 seconds mail19 02-28 04:55:28 {dovecot} [22194] (859760130) doveadm(ed.hanna(a)dssmgmt.com)<22534><kc2dOIG bHGIGWAAA0dxyZQ>: Error: write(<local>) failed: Timed out after 60 seconds mail19 02-28 04:58:52 {dovecot} [22194] (859762842) replicator: Error: Raw backtrace: #0 fatal_handler_real[0x11370e50] -> #1 i_internal_fatal_handler[0x11370f80] -> #2 i_panic[0x112c4456] -> #3 mem_block_alloc.cold[0x112c3d0d] -> #4 t_malloc_real[0x1136a420] -> #5 pool_data_stack_realloc[0x113905f0] -> #6 buffer_alloc[0x11366060] -> #7 buffer_append[0x11366390] -> #8 replicator_queue_push[0x01026fb0] -> #9 dsync_callback[0x01026730] -> #10 dsync_callback[0x01025e60] -> #11 dsync_input[0x010 mail19 02-28 04:58:52 {dovecot} [22194] (859762844) replicator: Error: 0x11388360] -> #14 io_loop_handler_run[0x11386fb0] -> #15 io_loop_run[0x11387130] -> #16 master_service_run[0x112f9c00] -> #17 main[0x01024de0] -> #18 _start[0x01024ff0] -> #19 [unw_get_proc_name() failed: -1] mail19 02-28 04:58:55 {dovecot} [22194] (859762875) doveadm(keith(a)elirpa.com)<22532><zxU4NoGbHGI EWAAA0dxyZQ>: Error: write(<local>) failed: Timed out after 60 seconds Dovecot config for mail18.scom.ca (server - 1) [05:03:57] mail18.scom.ca [root:0] /usr/local/etc/dovecot # cat dovecot.conf # 2.3.14 (cee3cbc0d): /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 12.1-RELEASE amd64 # Hostname: mail18.scom.ca auth_debug = no auth_debug_passwords = no mail_debug = no #lock_method = dotlock #mail_max_lock_timeout = 300s #mbox_read_locks = dotlock #mbox_write_locks = dotlock mmap_disable = yes mail_fsync = always mail_nfs_storage = yes mail_nfs_index = yes auth_mechanisms = plain login auth_verbose = yes base_dir = /data/dovecot/run/ debug_log_path = syslog disable_plaintext_auth = no dsync_features = empty-header-workaround #imapc_features = rfc822.size fetch-headers #imapc_host = mail.scom.ca #imapc_password = Pk554669 #imapc_user = paul(a)scom.ca info_log_path = syslog login_greeting = SCOM.CA Internet Services Inc. - Dovecot ready login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c mail_location = maildir:~/ mail_plugins = " virtual" mail_prefetch_count = 20 protocols = imap pop3 sieve mail_plugins = $mail_plugins notify replication protocol lmtp { mail_plugins = $mail_plugins notify replication sieve } protocol lda { mail_plugins = $mail_plugins notify replication sieve } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / } passdb { args = /usr/local/etc/dovecot/dovecot-pgsql.conf driver = sql } doveadm_port = 12345 doveadm_password = secretxxxx service doveadm { inet_listener { port = 12345 } } #dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u #dsync_remote_cmd = doveadm sync -d -u%u replication_dsync_parameters = -d -N -l 30 -U plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid, box, msgid, from, subject, size, vsize, flags sieve = file:~/sieve/sieve;active=~/sieve/.dovecot.sieve sieve_duplicate_default_period = 1h sieve_duplicate_max_period = 1d mail_replica = tcp:10.221.0.19 #mail_replica = remote:10.221.0.19 replication_sync_timeout = 2 } service anvil { unix_listener anvil { group = vmail mode = 0666 } } service auth { unix_listener /usr/home/postfix/private/auth { mode = 0660 user = postfix group = postfix } } service stats { unix_listener stats-reader { group = vmail mode = 0660 } unix_listener stats-writer { group = vmail mode = 0660 } } userdb { args = /usr/local/etc/dovecot/dovecot-pgsql.conf driver = sql } protocol imap { mail_max_userip_connections = 50 mail_plugins = $mail_plugins notify replication } protocol pop3 { mail_max_userip_connections = 50 mail_plugins = $mail_plugins notify replication } service managesieve-login { inet_listener sieve { port = 4190 } } verbose_proctitle = yes replication_max_conns = 10 replication_full_sync_interval = 30m service replicator { unix_listener replicator-doveadm { mode = 0666 user = vmail } } service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } #Addition ssl config !include sni.conf And dovecot-pgsql.conf file (same on both servers) : driver = pgsql connect = host=localhost port=5433 dbname=scom_billing user=pgsql password=Scom411400 default_pass_scheme = PLAIN password_query = SELECT username as user, password FROM email_users WHERE username = '%u' and password <> 'alias' and status = True and destination = '%u' user_query = SELECT home, uid, gid FROM email_users WHERE username = '%u' and password <> 'alias' and status = True and destination = '%u' iterate_query = SELECT user, password FROM email_users WHERE username = '%u' and password <> 'alias' and status = True and destination = '%u' Mail 19 dovecot config file : [05:05:40] mail19.scom.ca [root:0] /usr/local/etc/dovecot # cat dovecot.conf # 2.3.14 (cee3cbc0d): /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 12.1-RELEASE amd64 # Hostname: mail19.scom.ca auth_debug = no auth_debug_passwords = no mail_debug = no #lock_method = dotlock #mail_max_lock_timeout = 5s #mbox_read_locks = dotlock #mbox_write_locks = dotlock mmap_disable = yes mail_fsync = always mail_nfs_storage = yes mail_nfs_index = yes auth_mechanisms = plain login auth_verbose = yes base_dir = /data/dovecot/run/ debug_log_path = syslog disable_plaintext_auth = no dsync_features = empty-header-workaround #imapc_features = rfc822.size fetch-headers #imapc_host = mail.scom.ca #imapc_password = Pk554669 #imapc_user = paul(a)scom.ca info_log_path = syslog login_greeting = SCOM.CA Internet Services Inc. - Dovecot ready login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c mail_location = maildir:~/ mail_plugins = " virtual" mail_prefetch_count = 20 mail_plugins = $mail_plugins notify replication protocols = imap pop3 sieve protocol lmtp { mail_plugins = $mail_plugins notify replication sieve } protocol lda { mail_plugins = $mail_plugins notify replication sieve } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / } passdb { args = /usr/local/etc/dovecot/dovecot-pgsql.conf driver = sql } doveadm_port = 12345 doveadm_password = secretxxxx service doveadm { inet_listener { port = 12345 } } #dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u #dsync_remote_cmd = doveadm sync -d -u%u replication_dsync_parameters = -d -N -l 30 -U plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid, box, msgid, from, subject, size, vsize, flags sieve = file:~/sieve/sieve;active=~/sieve/.dovecot.sieve sieve_duplicate_default_period = 1h sieve_duplicate_max_period = 1d mail_replica = tcp:10.221.0.18 #mail_replica = remote:vmail@10.221.0.18 replication_sync_timeout = 2 } service anvil { unix_listener anvil { group = vmail mode = 0666 } } service auth { unix_listener /usr/home/postfix/private/auth { mode = 0660 user = postfix group = postfix } } service stats { unix_listener stats-reader { group = vmail mode = 0660 } unix_listener stats-writer { group = vmail mode = 0660 } } userdb { args = /usr/local/etc/dovecot/dovecot-pgsql.conf driver = sql } protocol imap { mail_max_userip_connections = 50 mail_plugins = $mail_plugins notify replication } protocol pop3 { mail_max_userip_connections = 50 mail_plugins = $mail_plugins notify replication } service managesieve-login { inet_listener sieve { port = 4190 } } verbose_proctitle = yes replication_max_conns = 10 replication_full_sync_interval = 30m service replicator { unix_listener replicator-doveadm { mode = 0666 user = vmail } } service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service replicator { unix_listener replicator-doveadm { mode = 0600 user = vmail } } replication_dsync_parameters = -d -N -l 30 -U #Addition ssl config !include sni.conf sni.conf file (same on both servers) : #sni.conf ssl = yes verbose_ssl = yes ssl_dh =</usr/local/etc/dovecot/dh-4096.pem ssl_prefer_server_ciphers = yes #ssl_min_protocol = TLSv1.2 #Default *.scom.ca ssl_key =</usr/local/etc/dovecot/scom.pem ssl_cert =</usr/local/etc/dovecot/scom.pem ssl_ca =</usr/local/etc/dovecot/scom.pem local_name .scom.ca { ssl_key = /programs/common/getssl.cert -c *.scom.ca -q yes ssl_cert = /programs/common/getssl.cert -c *.scom.ca -q yes ssl_ca = /programs/common/getssl.cert -c *.scom.ca -q yes } local_name mail.clancyca.com { ssl_key = /programs/common/getssl.cert -c mail.clancyca.com -q yes ssl_cert = /programs/common/getssl.cert -c mail.clancyca.com -q yes ssl_ca = /programs/common/getssl.cert -c mail.clancyca.com -q yes } local_name secure.clancyca.com { ssl_key = /programs/common/getssl.cert -c secure.clancyca.com -q yes ssl_cert = /programs/common/getssl.cert -c secure.clancyca.com -q yes ssl_ca = /programs/common/getssl.cert -c secure.clancyca.com -q yes } local_name mail.paulkudla.net { ssl_key = /programs/common/getssl.cert -c mail.paulkudla.net -q yes ssl_cert = /programs/common/getssl.cert -c mail.paulkudla.net -q yes ssl_ca = /programs/common/getssl.cert -c mail.paulkudla.net -q yes } local_name mail.ekst.ca { ssl_key = /programs/common/getssl.cert -c mail.ekst.ca -q yes ssl_cert = /programs/common/getssl.cert -c mail.ekst.ca -q yes ssl_ca = /programs/common/getssl.cert -c mail.ekst.ca -q yes } local_name mail.hamletdevelopments.ca { ssl_key = /programs/common/getssl.cert -c mail.hamletdevelopments.ca -q yes ssl_cert = /programs/common/getssl.cert -c mail.hamletdevelopments.ca -q yes ssl_ca = /programs/common/getssl.cert -c mail.hamletdevelopments.ca -q yes } Postfix main.cf (same on both servers) [05:15:03] mail19.scom.ca [root:0] /usr/home/postfix.local/config # cat main.cf # Global Postfix configuration file. This file lists only a subset # of all parameters. For the syntax, and for a complete parameter # list, see the postconf(5) manual page (command: "man 5 postconf"). # # For common configuration examples, see BASIC_CONFIGURATION_README # and STANDARD_CONFIGURATION_README. To find these documents, use # the command "postconf html_directory readme_directory", or go to # http://www.postfix.org/. # # For best results, change no more than 2-3 parameters at a time, # and test if Postfix still works after every change. alternate_config_directories = /usr/home/postfix/config data_directory = /var/lib/postfix.local maillog_file = /var/log/postfix.local compatibility_level=2 #compatibility_level=3.6 # SOFT BOUNCE # # The soft_bounce parameter provides a limited safety net for # testing. When soft_bounce is enabled, mail will remain queued that # would otherwise bounce. This parameter disables locally-generated # bounces, and prevents the SMTP server from rejecting mail permanently # (by changing 5xx replies into 4xx replies). However, soft_bounce # is no cure for address rewriting mistakes or mail routing mistakes. # soft_bounce = no #relayhost = 216.106.96.23 # LOCAL PATHNAME INFORMATION # # The queue_directory specifies the location of the Postfix queue. # This is also the root directory of Postfix daemons that run chrooted. # See the files in examples/chroot-setup for setting up Postfix chroot # environments on different UNIX systems. # queue_directory = /usr/home/postfix.local # The command_directory parameter specifies the location of all # postXXX commands. # command_directory = /usr/local/sbin # The daemon_directory parameter specifies the location of all Postfix # daemon programs (i.e. programs listed in the master.cf file). This # directory must be owned by root. # daemon_directory = /usr/local/libexec/postfix # QUEUE AND PROCESS OWNERSHIP # # The mail_owner parameter specifies the owner of the Postfix queue # and of most Postfix daemon processes. Specify the name of a user # account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS # AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In # particular, don't specify nobody or daemon. PLEASE USE A DEDICATED # USER. # mail_owner = postfix # The default_privs parameter specifies the default rights used by # the local delivery agent for delivery to external file or command. # These rights are used in the absence of a recipient user context. # DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER. # #default_privs = nobody # INTERNET HOST AND DOMAIN NAMES # # The myhostname parameter specifies the internet hostname of this # mail system. The default is to use the fully-qualified domain name # from gethostname(). $myhostname is used as a default value for many # other configuration parameters. # #myhostname = localhost myhostname = mail19.scom.ca # The mydomain parameter specifies the local internet domain name. # The default is to use $myhostname minus the first component. # $mydomain is used as a default value for many other configuration # parameters. # #mydomain = localhost mydomain = mail19.scom.ca # SENDING MAIL # # The myorigin parameter specifies the domain that locally-posted # mail appears to come from. The default is to append $myhostname, # which is fine for small sites. If you run a domain with multiple # machines, you should (1) change this to $mydomain and (2) set up # a domain-wide alias database that aliases each user to # user(a)that.users.mailhost. # # For the sake of consistency between sender and recipient addresses, # myorigin also specifies the default domain name that is appended # to recipient addresses that have no @domain part. # myorigin = $myhostname #myorigin = $mydomain # RECEIVING MAIL # The inet_interfaces parameter specifies the network interface # addresses that this mail system receives mail on. By default, # the software claims all active interfaces on the machine. The # parameter also controls delivery of mail to user(a)[ip.address]. # # See also the proxy_interfaces parameter, for network addresses that # are forwarded to us via a proxy or network address translator. # # Note: you need to stop/start Postfix when this parameter changes. # inet_interfaces = 127.0.0.1 #inet_interfaces = $myhostname #inet_interfaces = $myhostname, localhost, 76.74.132.2 #inet_interfaces = mail.dsl.scom.ca, dsl.scom.ca # The proxy_interfaces parameter specifies the network interface # addresses that this mail system receives mail on by way of a # proxy or network address translation unit. This setting extends # the address list specified with the inet_interfaces parameter. # # You must specify your proxy/NAT addresses when your system is a # backup MX host for other domains, otherwise mail delivery loops # will happen when the primary MX host is down. # #proxy_interfaces = #proxy_interfaces = 1.2.3.4 # The mydestination parameter specifies the list of domains that this # machine considers itself the final destination for. # # These domains are routed to the delivery agent specified with the # local_transport parameter setting. By default, that is the UNIX # compatible delivery agent that lookups all recipients in /etc/passwd # and /etc/aliases or their equivalent. # # The default is $myhostname + localhost.$mydomain. On a mail domain # gateway, you should also include $mydomain. # # Do not specify the names of virtual domains - those domains are # specified elsewhere (see VIRTUAL_README). # # Do not specify the names of domains that this machine is backup MX # host for. Specify those names via the relay_domains settings for # the SMTP server, or use permit_mx_backup if you are lazy (see # STANDARD_CONFIGURATION_README). # # The local machine is always the final destination for mail addressed # to user(a)[the.net.work.address] of an interface that the mail system # receives mail on (see the inet_interfaces parameter). # # Specify a list of host or domain names, /file/name or type:table # patterns, separated by commas and/or whitespace. A /file/name # pattern is replaced by its contents; a type:table is matched when # a name matches a lookup key (the right-hand side is ignored). # Continue long lines by starting the next line with whitespace. # # See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS". # #mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain #mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain, # mail.$mydomain, www.$mydomain, ftp.$mydomain # REJECTING MAIL FOR UNKNOWN LOCAL USERS # # The local_recipient_maps parameter specifies optional lookup tables # with all names or addresses of users that are local with respect # to $mydestination, $inet_interfaces or $proxy_interfaces. # # If this parameter is defined, then the SMTP server will reject # mail for unknown local users. This parameter is defined by default. # # To turn off local recipient checking in the SMTP server, specify # local_recipient_maps = (i.e. empty). # # The default setting assumes that you use the default Postfix local # delivery agent for local delivery. You need to update the # local_recipient_maps setting if: # # - You define $mydestination domain recipients in files other than # /etc/passwd, /etc/aliases, or the $virtual_alias_maps files. # For example, you define $mydestination domain recipients in # the $virtual_mailbox_maps files. # # - You redefine the local delivery agent in master.cf. # # - You redefine the "local_transport" setting in main.cf. # # - You use the "luser_relay", "mailbox_transport", or "fallback_transport" # feature of the Postfix local delivery agent (see local(8)). # # Details are described in the LOCAL_RECIPIENT_README file. # # Beware: if the Postfix SMTP server runs chrooted, you probably have # to access the passwd file via the proxymap service, in order to # overcome chroot restrictions. The alternative, having a copy of # the system passwd file in the chroot jail is just not practical. # # The right-hand side of the lookup tables is conveniently ignored. # In the left-hand side, specify a bare username, an @domain.tld # wild-card, or specify a user(a)domain.tld address. # local_recipient_maps = unix:passwd.byname $alias_maps #local_recipient_maps = proxy:unix:passwd.byname $alias_maps #local_recipient_maps = # The unknown_local_recipient_reject_code specifies the SMTP server # response code when a recipient domain matches $mydestination or # ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty # and the recipient address or address local-part is not found. # # The default setting is 550 (reject mail) but it is safer to start # with 450 (try again later) until you are certain that your # local_recipient_maps settings are OK. # #unknown_local_recipient_reject_code = 450 #Set by Mailscanner # TRUST AND RELAY CONTROL # The mynetworks parameter specifies the list of "trusted" SMTP # clients that have more privileges than "strangers". # # In particular, "trusted" SMTP clients are allowed to relay mail # through Postfix. See the smtpd_recipient_restrictions parameter # in postconf(5). # # You can specify the list of "trusted" network addresses by hand # or you can let Postfix do it for you (which is the default). # # By default (mynetworks_style = subnet), Postfix "trusts" SMTP # clients in the same IP subnetworks as the local machine. # On Linux, this does works correctly only with interfaces specified # with the "ifconfig" command. # # Specify "mynetworks_style = class" when Postfix should "trust" SMTP # clients in the same IP class A/B/C networks as the local machine. # Don't do this with a dialup site - it would cause Postfix to "trust" # your entire provider's network. Instead, specify an explicit # mynetworks list by hand, as described below. # # Specify "mynetworks_style = host" when Postfix should "trust" # only the local machine. # #mynetworks_style = class #mynetworks_style = subnet #mynetworks_style = host # Alternatively, you can specify the mynetworks list by hand, in # which case Postfix ignores the mynetworks_style setting. # # Specify an explicit list of network/netmask patterns, where the # mask specifies the number of bits in the network part of a host # address. # # You can also specify the absolute pathname of a pattern file instead # of listing the patterns here. Specify type:table for table-based lookups # (the value on the table right-hand side is not used). # mynetworks = 127.0.0.0/8 65.39.148.0/26 10.220.0.0/16 10.221.0.0/16 #mynetworks = $config_directory/mynetworks #mynetworks = hash:/usr/local/etc/postfix/network_table # The relay_domains parameter restricts what destinations this system will # relay mail to. See the smtpd_recipient_restrictions description in # postconf(5) for detailed information. # # By default, Postfix relays mail # - from "trusted" clients (IP address matches $mynetworks) to any destination, # - from "untrusted" clients to destinations that match $relay_domains or # subdomains thereof, except addresses with sender-specified routing. # The default relay_domains value is $mydestination. # # In addition to the above, the Postfix SMTP server by default accepts mail # that Postfix is final destination for: # - destinations that match $inet_interfaces or $proxy_interfaces, # - destinations that match $mydestination # - destinations that match $virtual_alias_domains, # - destinations that match $virtual_mailbox_domains. # These destinations do not need to be listed in $relay_domains. # # Specify a list of hosts or domains, /file/name patterns or type:name # lookup tables, separated by commas and/or whitespace. Continue # long lines by starting the next line with whitespace. A file name # is replaced by its contents; a type:name table is matched when a # (parent) domain appears as lookup key. # # NOTE: Postfix will not automatically forward mail for domains that # list this system as their primary or backup MX host. See the # permit_mx_backup restriction description in postconf(5). # relay_domains = $mydestination # INTERNET OR INTRANET # The relayhost parameter specifies the default host to send mail to # when no entry is matched in the optional transport(5) table. When # no relayhost is given, mail is routed directly to the destination. # # On an intranet, specify the organizational domain name. If your # internal DNS uses no MX records, specify the name of the intranet # gateway host instead. # # In the case of SMTP, specify a domain, host, host:port, [host]:port, # [address] or [address]:port; the form [host] turns off MX lookups. # # If you're connected via UUCP, see also the default_transport parameter. # #relayhost = [gateway.my.domain] #relayhost = [mailserver.isp.tld] #relayhost = uucphost #relayhost = [an.ip.add.ress] # REJECTING UNKNOWN RELAY USERS # # The relay_recipient_maps parameter specifies optional lookup tables # with all addresses in the domains that match $relay_domains. # # If this parameter is defined, then the SMTP server will reject # mail for unknown relay users. This feature is off by default. # # The right-hand side of the lookup tables is conveniently ignored. # In the left-hand side, specify an @domain.tld wild-card, or specify # a user(a)domain.tld address. # #relay_recipient_maps = hash:/usr/local/etc/postfix/relay_recipients # INPUT RATE CONTROL # # The in_flow_delay configuration parameter implements mail input # flow control. This feature is turned on by default, although it # still needs further development (it's disabled on SCO UNIX due # to an SCO bug). # # A Postfix process will pause for $in_flow_delay seconds before # accepting a new message, when the message arrival rate exceeds the # message delivery rate. With the default 100 SMTP server process # limit, this limits the mail inflow to 100 messages a second more # than the number of messages delivered per second. # # Specify 0 to disable the feature. Valid delays are 0..10. # #in_flow_delay = 1s # ADDRESS REWRITING # # The ADDRESS_REWRITING_README document gives information about # address masquerading or other forms of address rewriting including # username->Firstname.Lastname mapping. # ADDRESS REDIRECTION (VIRTUAL DOMAIN) # # The VIRTUAL_README document gives information about the many forms # of domain hosting that Postfix supports. # "USER HAS MOVED" BOUNCE MESSAGES # # See the discussion in the ADDRESS_REWRITING_README document. # TRANSPORT MAP # # See the discussion in the ADDRESS_REWRITING_README document. # ALIAS DATABASE # # The alias_maps parameter specifies the list of alias databases used # by the local delivery agent. The default list is system dependent. # # On systems with NIS, the default is to search the local alias # database, then the NIS alias database. See aliases(5) for syntax # details. # # If you change the alias database, run "postalias /etc/aliases" (or # wherever your system stores the mail alias file), or simply run # "newaliases" to build the necessary DBM or DB file. # # It will take a minute or so before changes become visible. Use # "postfix reload" to eliminate the delay. # #alias_maps = dbm:/etc/aliases alias_maps = hash:/usr/home/postfix/config/aliases #alias_maps = hash:/etc/aliases, nis:mail.aliases #alias_maps = netinfo:/aliases # The alias_database parameter specifies the alias database(s) that # are built with "newaliases" or "sendmail -bi". This is a separate # configuration parameter, because alias_maps (see above) may specify # tables that are not necessarily all under control by Postfix. # #alias_database = dbm:/etc/aliases #alias_database = dbm:/etc/mail/aliases alias_database = hash:/etc/postfix/aliases #alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases # ADDRESS EXTENSIONS (e.g., user+foo) # # The recipient_delimiter parameter specifies the separator between # user names and address extensions (user+foo). See canonical(5), # local(8), relocated(5) and virtual(5) for the effects this has on # aliases, canonical, virtual, relocated and .forward file lookups. # Basically, the software tries user+foo and .forward+foo before # trying user and .forward. # recipient_delimiter = + # DELIVERY TO MAILBOX # # The home_mailbox parameter specifies the optional pathname of a # mailbox file relative to a user's home directory. The default # mailbox file is /var/spool/mail/user or /var/mail/user. Specify # "Maildir/" for qmail-style delivery (the / is required). # #home_mailbox = Mailbox #home_mailbox = Maildir/ # The mail_spool_directory parameter specifies the directory where # UNIX-style mailboxes are kept. The default setting depends on the # system type. # #mail_spool_directory = /var/mail # The mailbox_command parameter specifies the optional external # command to use instead of mailbox delivery. The command is run as # the recipient with proper HOME, SHELL and LOGNAME environment settings. # Exception: delivery for root is done as $default_user. # # Other environment variables of interest: USER (recipient username), # EXTENSION (address extension), DOMAIN (domain part of address), # and LOCAL (the address localpart). # # Unlike other Postfix configuration parameters, the mailbox_command # parameter is not subjected to $parameter substitutions. This is to # make it easier to specify shell syntax (see example below). # # Avoid shell meta characters because they will force Postfix to run # an expensive shell process. Procmail alone is expensive enough. # # IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN # ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER. # #mailbox_command = /some/where/procmail #mailbox_command = /some/where/procmail -a "$EXTENSION" # The mailbox_transport specifies the optional transport in master.cf # to use after processing aliases and .forward files. This parameter # has precedence over the mailbox_command, fallback_transport and # luser_relay parameters. # # Specify a string of the form transport:nexthop, where transport is # the name of a mail delivery transport defined in master.cf. The # :nexthop part is optional. For more details see the sample transport # configuration file. # # NOTE: if you use this feature for accounts not in the UNIX password # file, then you must update the "local_recipient_maps" setting in # the main.cf file, otherwise the SMTP server will reject mail for # non-UNIX accounts with "User unknown in local recipient table". # mailbox_transport = dovecot # The fallback_transport specifies the optional transport in master.cf # to use for recipients that are not found in the UNIX passwd database. # This parameter has precedence over the luser_relay parameter. # # Specify a string of the form transport:nexthop, where transport is # the name of a mail delivery transport defined in master.cf. The # :nexthop part is optional. For more details see the sample transport # configuration file. # # NOTE: if you use this feature for accounts not in the UNIX password # file, then you must update the "local_recipient_maps" setting in # the main.cf file, otherwise the SMTP server will reject mail for # non-UNIX accounts with "User unknown in local recipient table". # #fallback_transport = lmtp:unix:/file/name #fallback_transport = cyrus #fallback_transport = # The luser_relay parameter specifies an optional destination address # for unknown recipients. By default, mail for unknown@$mydestination, # unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned # as undeliverable. # # The following expansions are done on luser_relay: $user (recipient # username), $shell (recipient shell), $home (recipient home directory), # $recipient (full recipient address), $extension (recipient address # extension), $domain (recipient domain), $local (entire recipient # localpart), $recipient_delimiter. Specify ${name?value} or # ${name:value} to expand value only when $name does (does not) exist. # # luser_relay works only for the default Postfix local delivery agent. # # NOTE: if you use this feature for accounts not in the UNIX password # file, then you must specify "local_recipient_maps =" (i.e. empty) in # the main.cf file, otherwise the SMTP server will reject mail for # non-UNIX accounts with "User unknown in local recipient table". # #luser_relay = $user(a)other.host #luser_relay = $local(a)other.host #luser_relay = admin+$local # JUNK MAIL CONTROLS # # The controls listed here are only a very small subset. The file # SMTPD_ACCESS_README provides an overview. # The header_checks parameter specifies an optional table with patterns # that each logical message header is matched against, including # headers that span multiple physical lines. # # By default, these patterns also apply to MIME headers and to the # headers of attached messages. With older Postfix versions, MIME and # attached message headers were treated as body text. # # For details, see "man header_checks". # #header_checks = regexp:/usr/local/etc/postfix/header_checks #Divert to Hold Queue #header_checks = regexp:/etc/postfix/header_checks # FAST ETRN SERVICE # # Postfix maintains per-destination logfiles with information about # deferred mail, so that mail can be flushed quickly with the SMTP # "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld". # See the ETRN_README document for a detailed description. # # The fast_flush_domains parameter controls what destinations are # eligible for this service. By default, they are all domains that # this server is willing to relay mail to. # #fast_flush_domains = $relay_domains # SHOW SOFTWARE VERSION OR NOT # # The smtpd_banner parameter specifies the text that follows the 220 # code in the SMTP server's greeting banner. Some people like to see # the mail version advertised. By default, Postfix shows no version. # # You MUST specify $myhostname at the start of the text. That is an # RFC requirement. Postfix itself does not care. # #smtpd_banner = $myhostname ESMTP $mail_name #smtpd_banner = $myhostname ESMTP $mail_name ($mail_version) # PARALLEL DELIVERY TO THE SAME DESTINATION # # How many parallel deliveries to the same user or domain? With local # delivery, it does not make sense to do massively parallel delivery # to the same user, because mailbox updates must happen sequentially, # and expensive pipelines in .forward files can cause disasters when # too many are run at the same time. With SMTP deliveries, 10 # simultaneous connections to the same domain could be sufficient to # raise eyebrows. # # Each message delivery transport has its XXX_destination_concurrency_limit # parameter. The default is $default_destination_concurrency_limit for # most delivery transports. For the local delivery agent the default is 2. #local_destination_concurrency_limit = 1 #2 #default_destination_concurrency_limit = 100 #20 # DEBUGGING CONTROL # # The debug_peer_level parameter specifies the increment in verbose # logging level when an SMTP client or server host name or address # matches a pattern in the debug_peer_list parameter. # debug_peer_level = 9 # The debug_peer_list parameter specifies an optional list of domain # or network patterns, /file/name patterns or type:name tables. When # an SMTP client or server host name or address matches a pattern, # increase the verbose logging level by the amount specified in the # debug_peer_level parameter. # #debug_peer_list = 127.0.0.1 #debug_peer_list = some.domain # The debugger_command specifies the external command that is executed # when a Postfix daemon program is run with the -D option. # # Use "command .. & sleep 5" so that the debugger can attach before # the process marches on. If you use an X-based debugger, be sure to # set up your XAUTHORITY environment variable before starting Postfix. # debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin xxgdb $daemon_directory/$process_name $process_id & sleep 5 # If you can't use X, use this to capture the call stack when a # daemon crashes. The result is in a file in the configuration # directory, and is named after the process name and the process ID. # # debugger_command = # PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont; # echo where) | gdb $daemon_directory/$process_name $process_id 2>&1 # >$config_directory/$process_name.$process_id.log & sleep 5 # # Another possibility is to run gdb under a detached screen session. # To attach to the screen sesssion, su root and run "screen -r # <id_string>" where <id_string> uniquely matches one of the detached # sessions (from "screen -list"). # # debugger_command = # PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen # -dmS $process_name gdb $daemon_directory/$process_name # $process_id & sleep 1 # INSTALL-TIME CONFIGURATION INFORMATION # # The following parameters are used when installing a new Postfix version. # # sendmail_path: The full pathname of the Postfix sendmail command. # This is the Sendmail-compatible mail posting interface. # sendmail_path = /usr/local/sbin/sendmail # newaliases_path: The full pathname of the Postfix newaliases command. # This is the Sendmail-compatible command to build alias databases. # newaliases_path = /usr/local/bin/newaliases # mailq_path: The full pathname of the Postfix mailq command. This # is the Sendmail-compatible mail queue listing command. # mailq_path = /usr/local/bin/mailq # setgid_group: The group for mail submission and queue management # commands. This must be a group name with a numerical group ID that # is not shared with other accounts, not even with the Postfix account. # setgid_group = maildrop # html_directory: The location of the Postfix HTML documentation. # html_directory = no # manpage_directory: The location of the Postfix on-line manual pages. # manpage_directory = /usr/local/man # sample_directory: The location of the Postfix sample configuration files. # This parameter is obsolete as of Postfix 2.1. # #sample_directory = /usr/local/etc/postfix # readme_directory: The location of the Postfix README files. # #readme_directory = no #Auth Stuff smtpd_sasl_auth_enable = yes broken_sasl_auth_clients = yes smtpd_sasl_security_options = noanonymous smtpd_sasl_authenticated_header = yes smtpd_sasl_local_domain = $myhostname smtpd_sasl_path = smtpd smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks reject_unauth_destination, #check_policy_service unix:private/policyd-spf #TLS Stuff #TLS Stuff #smtpd_tls_mandatory_protocols = !SSLv2,!SSLv3,!TLSv1 #smtp_tls_mandatory_protocols = !SSLv2,!SSLv3,!TLSv1 #smtpd_tls_protocols = !SSLv2,!SSLv3,!TLSv1 #smtp_tls_protocols = !SSLv2,!SSLv3,!TLSv1 smtpd_tls_exclude_ciphers = RC4, aNULL smtpd_tls_ask_ccert = yes smtpd_tls_security_level = may smtp_tls_security_level = may smtpd_tls_req_ccert = no smtpd_tls_auth_only = no smtpd_tls_loglevel = 2 smtp_tls_loglevel = 2 smtpd_use_tls = yes smtp_tls_chain_files = /etc/ssl/.scom.ca smtp_use_tls = yes smtp_tls_chain_files = /etc/ssl/.scom.ca smtpd_tls_session_cache_database = btree:${queue_directory}/smtpd_scache smtp_tls_session_cache_database = btree:${queue_directory}/smtp_scache smtp_tls_CApath = /etc/ssl/certs smtpd_tls_CApath = /etc/ssl/certs #Sort out hard bounce to softbounce smtp_reply_filter = pcre:/usr/home/postfix.local/config/smtp_5xx_to_4xx #General Options delay_warning_time = 1h mailbox_size_limit = 0 message_size_limit = 1000000000 #Mailscanner Options #header_checks = regexp:/usr/local/etc/postfix/header_checks unknown_local_recipient_reject_code = 550 #Dovecot stuff #Postgres Stuff #Temp off till i am a mail server mydestination = pgsql:/usr/home/postfix/config/pgsql-mydestination.cf virtual_maps=pgsql:/usr/home/postfix/config/pgsql-virtual.cf #Dovecot Stuff? dovecot_destination_recipient_limit = 1 virtual_transport = dovecot #Spf filter #policy_time_limit = 3600 #Other restrictions strict_rfc821_envelopes = yes smtpd_client_connection_count_limit = 1000 default_process_limit = 100 #minimal_backoff_time = 300s #maximal_backoff_time = 600s #queue_run_delay = 300s #Duplicate suppresion #enable_original_recipient = no #smtpd_discard_ehlo_keywords = silent-discard, dsn milter_default_action = accept milter_protocol = 6 smtpd_milters = inet:localhost:8891 non_smtpd_milters = inet:localhost:8891 #virtual_mailbox_lock = dotlock Postfix Master.cf : [05:16:09] mail19.scom.ca [root:0] /usr/home/postfix.local/config # cat master.cf # # Postfix master process configuration file. For details on the format # of the file, see the master(5) manual page (command: "man 5 master"). # # Do not forget to execute "postfix reload" after editing this file. # # ========================================================================== # service type private unpriv chroot wakeup maxproc command + args # (yes) (yes) (yes) (never) (100) # ========================================================================== #smtp inet n - n - - smtpd #submission inet n - n - - smtpd #465 inet n - n - - smtpd #995 inet n - n - - smtpd 61220 inet n - n - - smtpd # -o smtpd_tls_security_level=encrypt # -o smtpd_sasl_auth_enable=yes # -o smtpd_client_restrictions=permit_sasl_authenticated,reject # -o milter_macro_daemon_name=ORIGINATING #smtps inet n - n - - smtpd # -o smtpd_tls_wrappermode=yes # -o smtpd_sasl_auth_enable=yes # -o smtpd_client_restrictions=permit_sasl_authenticated,reject # -o milter_macro_daemon_name=ORIGINATING #628 inet n - n - - qmqpd pickup fifo n - n 60 1 pickup cleanup unix n - n - 0 cleanup qmgr fifo n - n 300 1 qmgr #qmgr fifo n - n 300 1 oqmgr tlsmgr unix - - n 1000? 1 tlsmgr rewrite unix - - n - - trivial-rewrite bounce unix - - n - 0 bounce defer unix - - n - 0 bounce trace unix - - n - 0 bounce verify unix - - n - 1 verify flush unix n - n 1000? 0 flush proxymap unix - - n - - proxymap proxywrite unix - - n - 1 proxymap smtp unix - - n - - smtp # When relaying mail as backup MX, disable fallback_relay to avoid MX loops relay unix - - n - - smtp -o smtp_fallback_relay= # -o smtp_helo_timeout=5 -o smtp_connect_timeout=5 showq unix n - n - - showq error unix - - n - - error retry unix - - n - - error discard unix - - n - - discard local unix - n n - - local virtual unix - n n - - virtual lmtp unix - - n - - lmtp anvil unix - - n - 1 anvil scache unix - - n - 1 scache # # ==================================================================== # Interfaces to non-Postfix software. Be sure to examine the manual # pages of the non-Postfix software to find out what options it wants. # # Many of the following services use the Postfix pipe(8) delivery # agent. See the pipe(8) man page for information about ${recipient} # and other message envelope options. # ==================================================================== # # maildrop. See the Postfix MAILDROP_README file for details. # Also specify in main.cf: maildrop_destination_recipient_limit=1 # #maildrop unix - n n - - pipe # flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d ${recipient} # # ==================================================================== # # The Cyrus deliver program has changed incompatibly, multiple times. # #old-cyrus unix - n n - - pipe # flags=R user=cyrus argv=/usr/local/cyrus/bin/deliver -e -m ${extension} ${user} # # ==================================================================== # # Cyrus 2.1.5 (Amos Gouaux) # Also specify in main.cf: cyrus_destination_recipient_limit=1 # #cyrus unix - n n - - pipe # user=cyrus argv=/usr/local/cyrus/bin/deliver -e -r ${sender} -m ${extension} ${recipient} # # ==================================================================== # # See the Postfix UUCP_README file for configuration details. # #uucp unix - n n - - pipe # flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) # # ==================================================================== # # Other external delivery methods. # #ifmail unix - n n - - pipe # flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient) # #bsmtp unix - n n - - pipe # flags=Fq. user=bsmtp argv=/usr/local/sbin/bsmtp -f $sender $nexthop $recipient # #scalemail-backend unix - n n - 2 pipe # flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store # ${nexthop} ${user} ${extension} # #mailman unix - n n - - pipe # flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py # ${nexthop} ${user} dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/deliver -f ${sender} -d ${recipient} policyd-spf unix - n n - - spawn user=nobody argv=/usr/local/bin/policyd-spf postlog unix-dgram n - n - 1 postlogd -- Happy Monday !!! 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

Build with MySQL -> libmysqlclient not found
by Dimitri 28 Feb '22

28 Feb '22

> John: > > ./configure --help > > might also be a good idea, I think it might have some options like: > > --mysql-libs=/path/to/lib > --mysql-includes=/path/to/include > > or something similiar to use. Unfortunately not, just the "--with-mysql" Option. > Oscar: > > You might need CPPFLAGS as well. (e.g. CPPFLAGS="-I/test/core/mariadb/include") > Check also "config.log" for errors. I had already done both, just forgot to mention it. But i should have looked further. Near the end of config.log is saw: ================================ > | /* Override any GCC internal prototype to avoid an error. > | Use char because int might match the return type of a GCC > | builtin and then its argument prototype would still apply. */ > | #ifdef __cplusplus > | extern "C" > | #endif > | char mysql_init (); > | int > | main () > | { > | return mysql_init (); > | ; > | return 0; > | } > configure:23386: result: noconfigure:23520: error: Can't build with MySQL support: libmysqlclient not found ================================ and thought that wouldn't help me. Now i looked again but further up an saw: ================================ > configure:23377: gcc -o conftest -std=gnu99 -g -O2 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -mfunction-return=keep -mindirect-branch=keep -Wall -W -Wmissing-prototypes -Wmissing-declarations> ... > /usr/bin/ld: cannot find -lzcollect2: error: ld returned 1 exit status ================================ Zlib i have (of course ;) ) also compiled from source. After adding "/test/dep/zlib/include" to CPPFLAGS and "/test/dep/zlib/lib" to LDFLAGS the configuration runs without errors. However i don't understand why the configuration-script takes the non-standard path for openssl automatically and correctly from the PKG_CONFIG_PATH, but the paths to my zlib and mariadb installations, which i also set in PKG_CONFIG_PATH not...

3 3

Build with MySQL -> libmysqlclient not found
by Dimitri 28 Feb '22

28 Feb '22

Hi folks, just step into another problem and don't know why? If i try to configure dovecot with the following: > ./configure --prefix=/test/core/dovecot --with-ssldir=/test/core/dovecot/tls --with-mysql i get > ... > checking for auth_userokay... no > checking for mysql_config... NO > checking for mysql_init in -lmysqlclient... noconfigure: error: Can't build with MySQL support: libmysqlclient not found After that i've tried to configure with following: > LDFLAGS="-L/test/core/mariadb/lib" ./configure --prefix=/test/core/dovecot --with-ssldir=/test/core/dovecot/tls --with-mysql but with same result. The Content of "/test/core/mariadb/lib" is: libmariadbclient.a libmariadb.so -> libmariadb.so.3 libmariadb.so.3 libmysqlclient.a -> libmariadbclient.a libmysqlclient_r.a -> libmariadbclient.a libmysqlclient_r.so -> libmariadb.so.3 libmysqlclient.so -> libmariadb.so.3 libmysqlservices.a pkgconfigplugin Also the Path "/test/core/mariadb/lib/pkgconfig" is in the PKG_CONFIG_PATH variable and the Library-Path "/test/core/mariadb/lib" is known by the dynamic linker (/etc/ld.so.conf.d/mylibs.conf). So what am i doing wrong? My Dovecot version: 2.3.18 My Mariadb version: 10.6.5 My OS: Ubuntu 20.04

4 4

Build with MySQL -> libmysqlclient not found
by Dimitri 27 Feb '22

27 Feb '22

> Why aren't you just using the Ubuntu 20.04 packaged version instead? > > Also, did you install the headers for libmysqlclient properly as > > well? > > What does /test/core/mariadb/includes/ or > > /test/core/includes/... show? Hi John, i just want to manage all the software manually, use own directorie-structur and have all the programs in one place, deepen my understanding how these programs work and build these programs only with the components i need. The content of "/test/core/mariadb/include/mysql" is: > errmsg.h > ma_list.h > ma_pvio.h > mariadb/ > mariadb/ma_io.h > mariadb_com.h > mariadb_ctype.h > mariadb_dyncol.h > mariadb_rpl.h > mariadb_stmt.h > mariadb_version.h > ma_tls.h > my_config.h > my_global.h > mysql/ > mysql/client_plugin.h > mysql/plugin_auth_common.h > mysql/plugin_auth.h > mysql_com.h > mysqld_error.h > mysql.h > mysql_version.h > my_sys.h > server/...

1 0

email location - files or sql
by Robert Moskowitz 25 Feb '22

25 Feb '22

I have been running a Dovecot based mail server for over 10 years and it is time (really past) to upgrade. I really don't want to roll my own anymore. Too much time and too many skills needed. Time to retire. But still want it 'in-house'. What I am seeing is that many of the packages seem to roll the messages into some SQL database. My Dovecot setup uses the /home/vmail/doman/../{cur,new,etc} tree structure. Is there any pros vs cons on this that I can read? Is there some nice packed mailserver I can drop on a Centos-arm server that has Dovecot under the covers and I can easily rsync my current mail store to it? Mail-in-a-box looks interesting. But I have not figured out its internals and if I have to worry about anything compiled for arm that is not part of the distro. Thanks in advance for help.

5 7

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

23 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.) 21 Feb '22

21 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 20 Feb '22

20 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

Unable to connect from macOS mail client
by necktwi 19 Feb '22

19 Feb '22

When trying to add mail account to the macOS mail client, I get following error Feb 13 13:05:15 imap-login: Info: Disconnected: Connection closed: SSL_accept() failed: error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown: SSL alert number 46 (no auth attempts in 0 secs): user=<>, rip=157.48.200.20, lip=192.168.1.101, TLS handshaking: SSL_accept() failed: error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown: SSL alert number 46, session=<5mZDV+HXxK+dMMgU> How to fix it? — Necktwi

4 4

--with-textcat: configure error?
by Felipe Gasper 18 Feb '22

18 Feb '22

Hello, With Dovecot 2.3.18 on AlmaLinux 8 I’m trying this: LIBEXTTEXTCAT_LIBS="-L/usr/lib64 -lexttextcat" ./configure --with-textcat … which gives me: checking for special_textcat_Init in -lexttextcat... no checking for special_textcat_Init in -ltextcat... no configure: error: Can't build with textcat support: libtextcat or libexttextcat not found I do have: > ls -la /usr/lib64 | grep textcat lrwxrwxrwx 1 root root 26 Oct 12 2019 libexttextcat-2.0.so.0 -> libexttextcat-2.0.so.0.0.0 -rwxr-xr-x 1 root root 22128 Oct 12 2019 libexttextcat-2.0.so.0.0.0 Is there some way of knowing what command it’s actually running that makes it say “libtextcat or libexttextcat not found”? Thank you! cheers, -Felipe Gasper

1 0

Debug shared namespace issues
by Kees van Vloten 18 Feb '22

18 Feb '22

Hi Team, I am still having troubles with the shared namespace. mail_shared_explicit_inbox = yes namespace { type = shared separator = "~" prefix = shared~%%u~ location = maildir:/srv/mail/vmail/example.com/%%n/store:LAYOUT=fs:FULLDIRNAME=0_Folde… hidden = no list = children subscriptions = no } To rule out ACL issues (for now), I have added: plugin { acl = vfile acl_shared_dict = file:/srv/mail/dovecot/lib/shared-mailboxes.db #acl_defaults_from_inbox = yes acl_user = %n acl_ignore_namespace = shared~ } The client imap communication looks like this: C[0x55ae80480750]: 1 login "test2" "" S[0x55ae8044a600]: 1 OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY PREVIEW=FUZZY STATUS=SIZE SAVEDATE LITERAL+ NOTIFY SPECIAL-USE ACL RIGHTS=texk] Logged in C[0x55ae80480750]: 2 capability S[0x55ae8044a600]: * CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY PREVIEW=FUZZY STATUS=SIZE SAVEDATE LITERAL+ NOTIFY SPECIAL-USE ACL RIGHTS=texk S[0x55ae8044a600]: 2 OK Capability completed (0.001 + 0.000 secs). C[0x55ae80480750]: 3 ID ("x-originating-ip" "192.168.10.106") S[0x55ae8044a600]: * ID ("name" "Dovecot") S[0x55ae8044a600]: 3 OK ID completed (0.001 + 0.000 secs). C[0x55ae80480750]: 4 namespace S[0x55ae8044a600]: * NAMESPACE (("" "~")) (("shared~" "~")) NIL S[0x55ae8044a600]: 4 OK Namespace completed (0.001 + 0.001 secs). C[0x55ae80480750]: 5 LIST "" "" S[0x55ae8044a600]: * LIST (\Noselect) "~" "" S[0x55ae8044a600]: 5 OK List completed (0.001 + 0.001 secs). C[0x55ae80480750]: 6 getacl "shared~test1~Drafts" S[0x55ae8044a600]: 6 NO [NONEXISTENT] Mailbox doesn't exist: shared~test1~Drafts (0.001 + 0.000 secs). C[0x55ae80480750]: 7 create "shared~test1~Drafts" S[0x55ae8044a600]: 7 NO [CANNOT] Invalid mailbox name 'shared~test1~Drafts': Missing namespace prefix 'shared~test1/Drafts~' (0.001 + 0.000 secs). C[0x55ae80480750]: 8 getacl "shared~test1~Drafts" S[0x55ae8044a600]: 8 NO [NONEXISTENT] Mailbox doesn't exist: shared~test1~Drafts (0.001 + 0.000 secs). C[0x55ae80480750]: 9 select "shared~test1~Drafts" S[0x55ae8044a600]: 9 NO [CANNOT] Invalid mailbox name 'shared~test1~Drafts': Missing namespace prefix 'shared~test1/Drafts~' (0.001 + 0.001 secs). C[0x55ae80480750]: 10 unsubscribe "shared~test1~Drafts" S[0x55ae8044a600]: 10 NO [CANNOT] Invalid mailbox name 'shared~test1~Drafts': Missing namespace prefix 'shared~test1/Drafts~' (0.001 + 0.000 secs). C[0x55ae80480750]: 11 logout S[0x55ae8044a600]: * BYE Logging out The client shows the shared user, but no content. I am using Sogo to test and sometimes Thunderbird to verify it is not a Sogo specific issue. I have currently set these debug options in Dovecot: auth_verbose = yes auth_debug = yes mail_debug = yes Unfortunately this is not enough to get a clue. What more can I do (other debug options?) to figure out what is going on? - Kees

2 5

Using dovecot-shared for an shared index not working
by Achim Gottinger 18 Feb '22

18 Feb '22

Hello I'm in the process to migrate our mail server from version 2.2.13 with maildirs to 2.3.13 with sdbox. On the old server if we wanted an common index for the seen flag on shared folders we created an file called dovecot-shared in the mail_location folder and the mailbox folders. This does not work on the new server for all shared mailboxes the seen flag is stored per user. The log file shows this if the seen flag is changed Feb 18 13:24:15 SERVER dovecot[18887]: imap(USER)<18978><51HhlUnYeOfAwAx3>: Debug: imapsieve: mailbox shared/info: FLAG event (changed flags: \Seen) The dovecot-acl file for the shared/info/INBOX folder has the s flag set. I hope i can get a few pointers here how to get the seen flag working for all users again. On the old server the location variable for the shared folders had the variable INDEX defined which can not be used with sdbox. location = maildir:/home/vmail/%%u/mail:INDEX=/home/vmail/%u/mail/shared/%%u:INBOX=/home/vmail/%%u/mail/.INBOX Does that imply that sharing the seen flag can not be used with sdbox? Thanks in advance, Achim Here is the dovecot -n output: ---------------------------------------------------------------------------------------------------------------------- # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 4.19.0+1 x86_64 Debian 11.2 zfs # Hostname: SERVER auth_cache_size = 5 M auth_gssapi_hostname = SERVER auth_krb5_keytab = /etc/dovecot/dovecot.keytab auth_master_user_separator = % auth_mechanisms = plain login gssapi auth_username_format = %Ln debug_log_path = syslog first_valid_gid = 998 first_valid_uid = 998 imap_max_line_length = 2 M info_log_path = syslog mail_attachment_dir = /var/lib/vmail/attachements mail_debug = yes mail_gid = 998 mail_home = /var/lib/vmail/%u mail_location = sdbox:/var/lib/vmail/%u/sdbox:INDEX=/var/lib/vmail/%u/sdbox mail_plugins = acl fts fts_solr mail_uid = 998 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 imapsieve vnd.dovecot.imapsieve namespace { list = children location = sdbox:/var/lib/vmail/%%u/sdbox:INDEXPVT=/var/lib/vmail/%u/sdbox/shared/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } 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 = separator = / type = private } passdb { args = /etc/dovecot/dovecot-ldap-passdb.conf.ext driver = ldap } plugin { acl = vfile acl_anyone = allow acl_defaults_from_inbox = yes acl_shared_dict = file:/var/lib/vmail/.shared-mailboxes fts = solr fts_autoindex = yes fts_autoindex_exclude = \Junk fts_autoindex_exclude2 = \Trash fts_solr = url=http://localhost:8983/solr/dovecot/ imapsieve_mailbox1_before = file:/etc/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/etc/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid from subject size sieve = ~/.dovecot.sieve sieve_after = /etc/dovecot/sieve/after.d/ sieve_dir = ~/sieve sieve_global_extensions = +vnd.dovecot.pipe sieve_pipe_bin_dir = /etc/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms } protocols = " imap lmtp sieve" service auth-worker { user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0777 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service imap-postlogin { executable = script-login /etc/dovecot/acl-groups.sh user = $default_internal_user } service imap { executable = imap imap-postlogin } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } ssl_cert = </etc/ssl/certs/SERVER.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-user.conf.ext driver = ldap } userdb { args = /etc/dovecot/dovecot-ldap-group.conf.ext driver = ldap } protocol lmtp { mail_plugins = acl fts fts_solr sieve } protocol imap { imap_client_workarounds = delay-newmail mail_plugins = acl fts fts_solr imap_sieve imap_acl fts fts_solr } local_name EXTERN { ssl_cert = </etc/letsencrypt/live/EXTERN/fullchain.pem ssl_key = # hidden, use -P to show it }

1 1

Dovecot with Microsoft Azure OAUTH2 ?
by Max Kostikov 18 Feb '22

18 Feb '22

Does anyone have experience successfully setting up Dovecot OAUTH2 for authentication with Microsoft Azure? I'm not sure what to use as tokeninfo_url and introspection_url in the Dovecot configuration. I would appreciate any help and advice. -- Best regards, Max Kostikov

2 1

Too many wait in auth process
by ismael.tanguy＠univ-brest.fr 18 Feb '22

18 Feb '22

Hello, I'm currently benchmarking new hardware aimed to serve around 70k users For now, our IMAP server have 13k users. To run imaptest, I've spwan some bench clients. Each bench client can run imaptest with 1000 clients. More than 1000 clients will load CPU of this bench client imaptest command (command are chosen from usage stat on our other IMAP servers): imaptest host=xxxxx port=xxx userfile=userfile mbox=/root/dovecot-crlf pass=sxxxx seed=123 clients=1000 select=194 uidfetch=94 noop=70 status=82 append=49 fetch=276 list=12 store=19 expunge=22 msubs=4 search=4 logout=1 delete=81 no_pipelining With one bench client, everything runs smoothly. # ps aux | grep dovecot | awk '{print $11,$12,$13,$14,$15,$16,$17,$18}' | sort | uniq -c 1 anvil: [221 connections] (anvil) 1 auth: [13 wait, 0 passdb, 0 userdb] (auth) 1 dovecot/config 1 dovecot/imap 84 dovecot/imap-login 1 dovecot/log 20 dovecot/pop3-login 1 grep dovecot 1 stats: [1307 connections] (stats) When a second instance bench instance start imaptest, clients of first and second instance begin to stall : 1400 stalled for 20 secs in command: 1 LOGIN"fakeuser644@mailbench...." "password" And : # ps aux | grep dovecot | awk '{print $11,$12,$13,$14,$15,$16,$17,$18}' | sort | uniq -c 1 anvil: [221 connections] (anvil) 1 auth: [1227 wait, 0 passdb, 0 userdb] (auth) 1 dovecot/config 1 dovecot/imap 37 dovecot/imap-login 1 dovecot/log 20 dovecot/pop3-login 1 grep dovecot 1 stats: [680 connections] (stats) Every auth go in wait, number of connection decreases. Using mysql or a password file give same results. I have used different values for service_count with also no success. I think my use of imaptest could be false. My understanding of service auth is limited for now because I'm quite new to Dovecot (I have previously worked with Cyrus). Thank you for every hints. Ismaël Tanguy

12 13

Shared mailbox visible but not readable
by Kees van Vloten 17 Feb '22

17 Feb '22

After the previous thread, I am now able to see / list the structure of a shared mailbox but cannot see the messages. doveadm acl get -u test2 INBOX ID Global Rights user=test1 admin create delete expunge insert lookup post read write write-deleted write-seen dovecot -n # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 5.10.0-10-amd64 x86_64 Debian 11.2 ext4 # Hostname: server.example.com auth_debug = yes auth_default_realm = EXAMPLE.COM auth_gssapi_hostname = server.example.com auth_krb5_keytab = /etc/keytab/dovecot.keytab auth_master_user_separator = * auth_mechanisms = gssapi gss-spnego plain auth_realms = EXAMPLE.COM auth_verbose = yes first_valid_gid = 986 first_valid_uid = 990 hostname = server.example.com imap_client_workarounds = tb-extra-mailbox-sep imap_max_line_length = 2 M login_greeting = Dovecot ready. mail_debug = yes mail_gid = 986 mail_location = maildir:/srv/mail/vmail/example.com/%n/store:LAYOUT=fs:FULLDIRNAME=0_Folder… mail_plugins = zlib notify push_notification listescape acl mail_shared_explicit_inbox = yes mail_uid = 990 namespace { hidden = no list = children location = maildir:/srv/mail/vmail/example.com/%%n/store:LAYOUT=fs:FULLDIRNAME=0_Folde… prefix = shared~%%n~ separator = ~ subscriptions = no type = shared } namespace inbox { hidden = no inbox = yes list = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Inbox { auto = subscribe } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = ~ subscriptions = yes type = private } passdb { args = username_format=%u /etc/dovecot/master-users driver = passwd-file master = yes } passdb { args = /etc/dovecot/ldap_user_to_principal.conf.ext driver = ldap pass = yes } passdb { args = nopassword=y allow_nets=127.0.0.1/32 driver = static } passdb { driver = pam } plugin { acl = vfile acl_defaults_from_inbox = yes acl_shared_dict = file:/srv/mail/dovecot/lib/shared-mailboxes.db acl_user = %n autocreate = Trash autocreate2 = Drafts autocreate3 = Sent autosubscribe = Trash autosubscribe2 = Drafts autosubscribe3 = Sent } protocols = " imap lmtp submission" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 0 } inet_listener imap_local { address = 127.0.0.1 port = 144 ssl = no } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 1 } service indexer-worker { vsz_limit = 2 G } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service submission-login { inet_listener submission { port = 465 ssl = yes } } ssl = required ssl_cert = </etc/dovecot/private/dovecot.pem ssl_cipher_list = EECDH+AESGCM:EDH+AESGCM ssl_client_ca_dir = /etc/ssl/certs ssl_curve_list = X25519:secp521r1:secp384r1:prime256v1 ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 submission_client_workarounds = whitespace-before-path submission_relay_host = localhost userdb { args = /etc/dovecot/ldap_user_domain.conf.ext driver = ldap result_success = continue } userdb { args = uid=vmail gid=vmail home=/srv/mail/vmail allow_all_users=yes driver = static } protocol lmtp { mail_plugins = zlib notify push_notification listescape acl } protocol lda { mail_plugins = zlib notify push_notification listescape acl } protocol imap { mail_max_userip_connections = 50 mail_plugins = zlib notify push_notification listescape acl imap_acl } Server-side logging: Feb 17 18:19:46 server dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured#011session=wnsM+TnYeNt/AAAB#011lip=127.0.0.1#011rip=127.0.0.1#011lport=144#011rport=56184#011resp=<hidden> Feb 17 18:19:46 server dovecot: auth: Debug: ldap(test1(a)example.com,127.0.0.1,<wnsM+TnYeNt/AAAB>): Performing passdb lookup Feb 17 18:19:46 server dovecot: auth: Debug: ldap(test1(a)example.com,127.0.0.1,<wnsM+TnYeNt/AAAB>): pass search: base=OU=User Accounts,OU=Interactive Users,OU=Groupware,DC=example,DC=com scope=subtree filter=(&(objectClass=user)(sAMAccountName=test1)(memberOf:1.2.840.113556.1.4.1941:=CN=mail_user-example.com,OU=Mail Domains,OU=Groups,DC=example,DC=com)(!(userAccountControl:1.2.840.113556.1.4.803:=2))) fields=userPrincipalName Feb 17 18:19:46 server dovecot: auth: Debug: ldap(test1(a)example.com,127.0.0.1,<wnsM+TnYeNt/AAAB>): result: userPrincipalName=test1(a)example.com; userPrincipalName unused Feb 17 18:19:46 server dovecot: auth: Debug: ldap(test1(a)example.com,127.0.0.1,<wnsM+TnYeNt/AAAB>): username changed test1(a)example.com -> test1 Feb 17 18:19:46 server dovecot: auth: Debug: ldap(test1,127.0.0.1,<wnsM+TnYeNt/AAAB>): Finished passdb lookup Feb 17 18:19:46 server dovecot: auth: Debug: static(test1,127.0.0.1,<wnsM+TnYeNt/AAAB>): Performing passdb lookup Feb 17 18:19:46 server dovecot: auth: Debug: static(test1,127.0.0.1,<wnsM+TnYeNt/AAAB>): lookup Feb 17 18:19:46 server dovecot: auth: Debug: static(test1,127.0.0.1,<wnsM+TnYeNt/AAAB>): allow_nets: Matching for network 127.0.0.1/32 Feb 17 18:19:46 server dovecot: auth: Debug: static(test1,127.0.0.1,<wnsM+TnYeNt/AAAB>): Finished passdb lookup Feb 17 18:19:46 server dovecot: auth: Debug: auth(test1,127.0.0.1,<wnsM+TnYeNt/AAAB>): Auth request finished Feb 17 18:19:46 server dovecot: auth: Debug: client passdb out: OK#0111#011user=test1#011k5principals=test1(a)example.com Feb 17 18:19:46 server dovecot: auth: Debug: master in: REQUEST#011674496513#011982757#0111#011bdc4ed95a66c86ed9e287682de2cc297#011session_pid=982760#011request_auth_token Feb 17 18:19:46 server dovecot: auth: Debug: ldap(test1,127.0.0.1,<wnsM+TnYeNt/AAAB>): Performing userdb lookup Feb 17 18:19:46 server dovecot: auth: Debug: ldap(test1,127.0.0.1,<wnsM+TnYeNt/AAAB>): user search: base=OU=User Accounts,OU=Interactive Users,OU=Groupware,DC=example,DC=com scope=subtree filter=(&(objectClass=user)(sAMAccountName=test1)(memberOf:1.2.840.113556.1.4.1941:=CN=mail_user-,OU=Mail Domains,OU=Groups,DC=example,DC=com)(!(userAccountControl:1.2.840.113556.1.4.803:=2))) fields= Feb 17 18:19:46 server dovecot: auth: Debug: auth client connected (pid=982759) Feb 17 18:19:46 server dovecot: auth: Debug: ldap(test1,127.0.0.1,<wnsM+TnYeNt/AAAB>): no fields returned by the server Feb 17 18:19:46 server dovecot: auth: ldap(test1,127.0.0.1,<wnsM+TnYeNt/AAAB>): unknown user Feb 17 18:19:46 server dovecot: auth: Debug: ldap(test1,127.0.0.1,<wnsM+TnYeNt/AAAB>): Finished userdb lookup Feb 17 18:19:46 server dovecot: auth: Debug: static(test1,127.0.0.1,<wnsM+TnYeNt/AAAB>): Performing userdb lookup Feb 17 18:19:46 server dovecot: auth: Debug: static(test1,127.0.0.1,<wnsM+TnYeNt/AAAB>): Finished userdb lookup Feb 17 18:19:46 server dovecot: auth: Debug: master userdb out: USER#011674496513#011test1#011uid=990#011gid=986#011home=/srv/mail/vmail#011auth_mech=PLAIN#011auth_token=7f5013248866ebfbfb636b8de817aad6ac5af767 Feb 17 18:19:46 server dovecot: imap-login: Login: user=<test1>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=982760, secured, session=<wnsM+TnYeNt/AAAB> Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: Effective uid=990, gid=986, home=/srv/mail/vmail Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: Namespace inbox: type=private, prefix=, sep=~, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/srv/mail/vmail/example.com/test1/store:LAYOUT=fs:FULLDIRN… Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: fs: root=/srv/mail/vmail/example.com/test1/store, index=/srv/mail/vmail/example.com/test1/index, indexpvt=, control=/srv/mail/vmail/example.com/test1/control, inbox=, alt= Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: acl: initializing backend with data: vfile Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: acl: acl username = test1 Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: acl: owner = 1 Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: acl vfile: Global ACLs disabled Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: Namespace : type=shared, prefix=shared~%n~, sep=~, inbox=no, hidden=no, list=children, subscriptions=no location=maildir:/srv/mail/vmail/example.com/%n/store:LAYOUT=fs:FULLDIRNAME… Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: shared: root=/run/dovecot, index=, indexpvt=, control=, inbox=, alt= Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: fts: Indexes disabled for namespace 'shared~%n~' Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: acl: initializing backend with data: vfile Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: acl: acl username = test1 Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: acl: owner = 0 Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: acl vfile: Global ACLs disabled Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: fs: root=/srv/mail/vmail/example.com/test2/INBOX/store, index=, indexpvt=/srv/mail/vmail/example.com/test1/index_shared/test2/INBOX, control=/srv/mail/vmail/example.com/test2/INBOX/control, inbox=, alt= Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: acl: initializing backend with data: vfile Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: acl: acl username = test2/INBOX Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: acl: owner = 1 Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: acl vfile: Global ACLs disabled Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: fs: root=/srv/mail/vmail/example.com/test2/INBOX/store, index=, indexpvt=/srv/mail/vmail/example.com/test1/index_shared/test2/INBOX, control=/srv/mail/vmail/example.com/test2/INBOX/control, inbox=, alt= Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: acl: initializing backend with data: vfile Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: acl: acl username = test1 Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: acl: owner = 0 Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: acl vfile: Global ACLs disabled Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: Mailbox shared~test2~INBOX: Mailbox opened because: SELECT Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Logged out in=245 out=1711 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Client-side logging: S[0x55ae80a7bb00]: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ STARTTLS AUTH=GSSAPI AUTH=GSS-SPNEGO AUTH=PLAIN] Dovecot ready. C[0x55ae808c12d0]: 1 login "test1" "" S[0x55ae80a7bb00]: 1 OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY PREVIEW=FUZZY STATUS=SIZE SAVEDATE LITERAL+ NOTIFY SPECIAL-USE ACL RIGHTS=texk] Logged in C[0x55ae808c12d0]: 2 capability S[0x55ae80a7bb00]: * CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY PREVIEW=FUZZY STATUS=SIZE SAVEDATE LITERAL+ NOTIFY SPECIAL-USE ACL RIGHTS=texk S[0x55ae80a7bb00]: 2 OK Capability completed (0.001 + 0.000 secs). C[0x55ae808c12d0]: 3 ID ("x-originating-ip" "192.168.10.106") S[0x55ae80a7bb00]: * ID ("name" "Dovecot") S[0x55ae80a7bb00]: 3 OK ID completed (0.001 + 0.001 secs). C[0x55ae808c12d0]: 4 namespace S[0x55ae80a7bb00]: * NAMESPACE (("" "~")) (("shared~" "~")) NIL S[0x55ae80a7bb00]: 4 OK Namespace completed (0.001 + 0.000 secs). C[0x55ae808c12d0]: 5 LIST "" "" S[0x55ae80a7bb00]: * LIST (\Noselect) "~" "" S[0x55ae80a7bb00]: 5 OK List completed (0.001 + 0.001 secs). C[0x55ae808c12d0]: 6 select "INBOX" S[0x55ae80a7bb00]: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) S[0x55ae80a7bb00]: * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. S[0x55ae80a7bb00]: * 1 EXISTS S[0x55ae80a7bb00]: * 0 RECENT S[0x55ae80a7bb00]: * OK [UIDVALIDITY 1637177527] UIDs valid S[0x55ae80a7bb00]: * OK [UIDNEXT 2] Predicted next UID S[0x55ae80a7bb00]: * OK [HIGHESTMODSEQ 10] Highest S[0x55ae80a7bb00]: 6 OK [READ-WRITE] Select completed (0.001 + 0.000 secs). C[0x55ae808c12d0]: 7 UID SEARCH (UNSEEN NOT DELETED) S[0x55ae80a7bb00]: * SEARCH S[0x55ae80a7bb00]: 7 OK Search completed (0.001 + 0.001 secs). C[0x55ae808c12d0]: 8 select "shared~test2~INBOX" S[0x55ae80a7bb00]: * OK [CLOSED] Previous mailbox closed. S[0x55ae80a7bb00]: 8 NO [CANNOT] Invalid mailbox name 'shared~test2~INBOX': Missing namespace prefix 'shared~test2/INBOX~' (0.001 + 0.001 secs). C[0x55ae808c12d0]: 9 logout S[0x55ae80a7bb00]: * BYE Logging out This issue I am facing is this: 8 NO [CANNOT] Invalid mailbox name 'shared~test2~INBOX': Missing namespace prefix 'shared~test2/INBOX~' The server-side seems to think everything is fine: Feb 17 18:19:46 server dovecot: imap(test1)<982760><wnsM+TnYeNt/AAAB>: Debug: Mailbox shared~test2~INBOX: Mailbox opened because: SELECT But I do not get to see any messages in test2's shared mailbox. How to debug this? Or better: how to fix it :-) ?? - Kees

2 2

mail-crypt and mbox format
by cincodemayo_67＠yahoo.com 17 Feb '22

17 Feb '22

Hi, My Dovecot server of many years has been set up to use mbox email folders. I want to implement mail-crypt and after banging my head against a wall for a few days trying to get mail-crypt to work I decided to try it against a test instance of my server that I reset to use Maildir format and mail-crypt worked instantly. Does mail-crypt work with mbox format mail folders, or am I wasting my time unless I switch over to Maildir? The documentation at https://doc.dovecot.org/configuration_manual/mail_crypt_plugin/ doesn't explicitly say Maildir is required. Thanks in advance, Doug

5 9

Mailbox sharing not working
by Kees van Vloten 17 Feb '22

17 Feb '22

Hi Team, I am trying to setup mailbox sharing. But although user test2 shares INBOX with test1, it is not visible for user1. doveadm acl get -u test2 INBOX ID Global Rights user=test1 admin create delete expunge insert lookup post read write write-deleted write-seen cat /srv/mail/dovecot/lib/shared-mailboxes.db shared/shared-boxes/user/test1/test2(a)example.com 1 Log output: Feb 16 20:12:42 server dovecot: imap-login: Login: user=<test1(a)example.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=900367, secured, session=<mDkSbyfYotF/AAAB> Feb 16 20:12:42 server dovecot: imap(test1(a)example.com)<900367><mDkSbyfYotF/AAAB>: Debug: Loading modules from directory: /usr/lib/dovecot/modules Feb 16 20:12:42 server dovecot: imap(test1(a)example.com)<900367><mDkSbyfYotF/AAAB>: Debug: Module loaded: /usr/lib/dovecot/modules/lib01_acl_plugin.so Feb 16 20:12:42 server dovecot: imap(test1(a)example.com)<900367><mDkSbyfYotF/AAAB>: Debug: Module loaded: /usr/lib/dovecot/modules/lib02_imap_acl_plugin.so Feb 16 20:12:42 server dovecot: imap(test1(a)example.com)<900367><mDkSbyfYotF/AAAB>: Debug: Module loaded: /usr/lib/dovecot/modules/lib15_notify_plugin.so Feb 16 20:12:42 server dovecot: imap(test1(a)example.com)<900367><mDkSbyfYotF/AAAB>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_fts_plugin.so Feb 16 20:12:42 server dovecot: imap(test1(a)example.com)<900367><mDkSbyfYotF/AAAB>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_listescape_plugin.so Feb 16 20:12:42 server dovecot: imap(test1(a)example.com)<900367><mDkSbyfYotF/AAAB>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_push_notification_plugin.so Feb 16 20:12:42 server dovecot: imap(test1(a)example.com)<900367><mDkSbyfYotF/AAAB>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_zlib_plugin.so Feb 16 20:12:42 server dovecot: imap(test1(a)example.com)<900367><mDkSbyfYotF/AAAB>: Debug: Module loaded: /usr/lib/dovecot/modules/lib21_fts_xapian_plugin.so Feb 16 20:12:42 server dovecot: imap(test1(a)example.com)<900367><mDkSbyfYotF/AAAB>: Debug: Module loaded: /usr/lib/dovecot/modules/lib95_imap_sieve_plugin.so Feb 16 20:12:42 server dovecot: imap(test1(a)example.com)<900367><mDkSbyfYotF/AAAB>: Debug: Effective uid=990, gid=986, home=/srv/mail/vmail Feb 16 20:12:42 server dovecot: imap(test1(a)example.com)<900367><mDkSbyfYotF/AAAB>: Debug: Namespace inbox: type=private, prefix=, sep=~, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/srv/mail/vmail/example.com/test1/store:LAYOUT=fs:FULLDIRN… Feb 16 20:12:42 server dovecot: imap(test1(a)example.com)<900367><mDkSbyfYotF/AAAB>: Debug: fs: root=/srv/mail/vmail/example.com/test1/store, index=/srv/mail/vmail/example.com/test1/index, indexpvt=, control=/srv/mail/vmail/example.com/test1/control, inbox=, alt= Feb 16 20:12:42 server dovecot: imap(test1(a)example.com)<900367><mDkSbyfYotF/AAAB>: Debug: acl: initializing backend with data: vfile Feb 16 20:12:42 server dovecot: imap(test1(a)example.com)<900367><mDkSbyfYotF/AAAB>: Debug: Mailbox INBOX~example.com: Mailbox opened because: SELECT Feb 16 20:12:42 server dovecot: imap(test1(a)example.com)<900367><mDkSbyfYotF/AAAB>: Debug: acl vfile: file /srv/mail/vmail/example.com/test1/store/INBOX/example.com/0_FolderContent/dovecot-acl not found Feb 16 20:12:42 server dovecot: imap(test1(a)example.com)<900367><mDkSbyfYotF/AAAB>: Logged out in=136 out=1584 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Feb 16 20:12:43 server dovecot: imap-login: Login: user=<test1(a)example.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=900369, secured, session=<82gfbyfYuNF/AAAB> <removed lines> Feb 16 20:12:43 server dovecot: imap(test1(a)example.com)<900369><82gfbyfYuNF/AAAB>: Debug: Namespace inbox: type=private, prefix=, sep=~, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/srv/mail/vmail/example.com/test1/store:LAYOUT=fs:FULLDIRN… Feb 16 20:12:43 server dovecot: imap(test1(a)example.com)<900369><82gfbyfYuNF/AAAB>: Debug: fs: root=/srv/mail/vmail/example.com/test1/store, index=/srv/mail/vmail/example.com/test1/index, indexpvt=, control=/srv/mail/vmail/example.com/test1/control, inbox=, alt= Feb 16 20:12:43 server dovecot: imap(test1(a)example.com)<900369><82gfbyfYuNF/AAAB>: Debug: acl: initializing backend with data: vfile Feb 16 20:12:43 server dovecot: imap(test1(a)example.com)<900369><82gfbyfYuNF/AAAB>: Debug: acl: acl username = test1(a)example.com Feb 16 20:12:43 server dovecot: imap(test1(a)example.com)<900369><82gfbyfYuNF/AAAB>: Debug: acl: owner = 1 Feb 16 20:12:43 server dovecot: imap(test1(a)example.com)<900369><82gfbyfYuNF/AAAB>: Debug: acl vfile: Global ACLs disabled Feb 16 20:12:43 server dovecot: imap(test1(a)example.com)<900369><82gfbyfYuNF/AAAB>: Debug: Namespace : type=shared, prefix=shared~%u~, sep=~, inbox=no, hidden=no, list=no, subscriptions=no location=maildir:/srv/mail/vmail/example.com/%n/store:LAYOUT=fs:FULLDIRNAME… Feb 16 20:12:43 server dovecot: imap(test1(a)example.com)<900369><82gfbyfYuNF/AAAB>: Debug: shared: root=/run/dovecot, index=, indexpvt=, control=, inbox=, alt= Feb 16 20:12:43 server dovecot: imap(test1(a)example.com)<900369><82gfbyfYuNF/AAAB>: Debug: fts: Indexes disabled for namespace 'shared~%u~' Feb 16 20:12:43 server dovecot: imap(test1(a)example.com)<900369><82gfbyfYuNF/AAAB>: Debug: acl: initializing backend with data: vfile Feb 16 20:12:43 server dovecot: imap(test1(a)example.com)<900369><82gfbyfYuNF/AAAB>: Debug: acl: acl username = test1(a)example.com Feb 16 20:12:43 server dovecot: imap(test1(a)example.com)<900369><82gfbyfYuNF/AAAB>: Debug: acl vfile: reading file /srv/mail/vmail/example.com/test1/store/INBOX/0_FolderContent/dovecot-acl Feb 16 20:12:43 server dovecot: imap(test1(a)example.com)<900369><82gfbyfYuNF/AAAB>: Debug: acl vfile: file /srv/mail/vmail/example.com/test1/store/Drafts/0_FolderContent/dovecot-acl not found Feb 16 20:12:43 server dovecot: imap(test1(a)example.com)<900369><82gfbyfYuNF/AAAB>: Debug: acl vfile: file /srv/mail/vmail/example.com/test1/store/Junk/0_FolderContent/dovecot-acl not found Feb 16 20:12:43 server dovecot: imap(test1(a)example.com)<900369><82gfbyfYuNF/AAAB>: Debug: acl vfile: file /srv/mail/vmail/example.com/test1/store/Trash/0_FolderContent/dovecot-acl not found Feb 16 20:12:43 server dovecot: imap(test1(a)example.com)<900369><82gfbyfYuNF/AAAB>: Debug: acl vfile: file /srv/mail/vmail/example.com/test1/store/Sent/0_FolderContent/dovecot-acl not found Feb 16 20:12:43 server dovecot: imap(test1(a)example.com)<900369><82gfbyfYuNF/AAAB>: Debug: acl vfile: file /srv/mail/vmail/example.com/test1/store/INBOX/example.com/0_FolderContent/dovecot-acl not found Feb 16 20:12:43 server dovecot: imap(test1(a)example.com)<900369><82gfbyfYuNF/AAAB>: Debug: Namespace shared~: Using permissions from : mode=0700 gid=default Feb 16 20:12:43 server dovecot: imap(test1(a)example.com)<900369><82gfbyfYuNF/AAAB>: Logged out in=130 out=1518 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Dovecot -n: # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 5.10.0-10-amd64 x86_64 Debian 11.2 ext4 # Hostname: server.example.com auth_default_realm = EXAMPLE.COM auth_gssapi_hostname = server.example.com auth_krb5_keytab = /etc/keytab/dovecot.keytab auth_master_user_separator = * auth_mechanisms = gssapi gss-spnego plain auth_realms = EXAMPLE.COM first_valid_gid = 601 first_valid_uid = 601 hostname = server.example.com imap_client_workarounds = tb-extra-mailbox-sep imap_max_line_length = 2 M login_greeting = Dovecot ready. mail_debug = yes mail_gid = 986 mail_location = maildir:/srv/mail/vmail/example.com/%n/store:LAYOUT=fs:FULLDIRNAME=0_Folder… mail_plugins = zlib notify push_notification listescape acl mail_shared_explicit_inbox = yes mail_uid = 990 namespace { hidden = no list = no location = maildir:/srv/mail/vmail/example.com/%%n/store:LAYOUT=fs:FULLDIRNAME=0_Folde… prefix = shared~%%u~ separator = ~ subscriptions = no type = shared } namespace inbox { hidden = no inbox = yes list = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Inbox { auto = subscribe } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = ~ subscriptions = yes type = private } passdb { args = username_format=%u /etc/dovecot/master-users driver = passwd-file master = yes } passdb { args = /etc/dovecot/ldap_user_to_principal.conf.ext driver = ldap pass = yes } passdb { args = nopassword=y allow_nets=127.0.0.1/32 driver = static } passdb { driver = pam } plugin { acl = vfile acl_defaults_from_inbox = yes acl_shared_dict = file:/srv/mail/dovecot/lib/shared-mailboxes.db acl_user = %u autocreate = Trash autocreate2 = Drafts autocreate3 = Sent autosubscribe = Trash autosubscribe2 = Drafts autosubscribe3 = Sent listescape_char = \ } postmaster_address = admin(a)example.com protocols = " imap lmtp submission" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 0 } inet_listener imap_local { address = 127.0.0.1 port = 144 ssl = no } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 1 } service indexer-worker { vsz_limit = 2 G } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service submission-login { inet_listener submission { port = 465 ssl = yes } } ssl = required ssl_cert = </etc/dovecot/private/dovecot.pem ssl_cipher_list = EECDH+AESGCM:EDH+AESGCM ssl_client_ca_dir = /etc/ssl/certs ssl_curve_list = X25519:secp521r1:secp384r1:prime256v1 ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 submission_client_workarounds = whitespace-before-path submission_relay_host = localhost userdb { args = /etc/dovecot/ldap_list_users.conf.ext driver = ldap result_success = continue } userdb { args = /etc/dovecot/ldap_user_domain.conf.ext driver = ldap result_success = continue } userdb { args = uid=vmail gid=vmail home=/srv/mail/vmail allow_all_users=yes driver = static } protocol lmtp { mail_plugins = zlib notify push_notification listescape acl } protocol lda { mail_plugins = zlib notify push_notification listescape acl } protocol imap { mail_max_userip_connections = 50 mail_plugins = zlib notify push_notification listescape acl imap_acl } Is there anything obviously wrong in the config? I suspect a mismatch between %u and %n somewhere but don't know how to figure out the culprit. How can I get more relevant debug log output about namespaces / mailbox sharing? Or can I run commands to check validity? - Kees

2 10

Replications ERROR
by Günther J. Niederwimmer 16 Feb '22

16 Feb '22

Hello, Can any Help me to find out the Problem with "sync failed" I have all disabled only one user is in the moment running? doveadm replicator status '*' username priority fast sync full sync success sync failed gjn(a)example.com none 00:01:47 23:37:43 - y gjn none 00:01:47 23:42:43 - y Could it be a Problem with this doveadm user '*' gjn(a)example.com What is the way to become logs what is going wrong ? Could it be, I have Problems with the Dovecot Variables in the LDAP Config ? Thanks very match for a answer, -- mit freundlichen Grüßen / best regards Günther J. Niederwimmer

2 3

Memory problems with config service
by Víctor Rubiella Monfort 16 Feb '22

16 Feb '22

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 }} }

2 1

mail.error listen_fd(7): Error: 22 46530 BYE
by Juerg Reimann 14 Feb '22

14 Feb '22

Hi there, What do the following logs mean and how do I resolve the problem? 2022-02-14T12:44:24+01:00 localhost dovecot: [ID 702911 mail.error] listen_fd(7): Error: 22 46519 BYE 2022-02-14T12:44:24+01:00 localhost dovecot: [ID 702911 mail.error] listen_fd(7): Error: 26 46529 BYE 2022-02-14T12:44:24+01:00 localhost dovecot: [ID 702911 mail.error] listen_fd(7): Error: 26 46531 BYE 2022-02-14T12:44:24+01:00 localhost dovecot: [ID 702911 mail.error] listen_fd(7): Error: 22 46530 BYE 2022-02-14T12:44:24+01:00 localhost dovecot: [ID 702911 mail.error] listen_fd(7): Error: 22 46532 BYE 2022-02-14T12:44:24+01:00 localhost dovecot: [ID 702911 mail.error] listen_fd(7): Error: 22 46537 BYE 2022-02-14T12:44:24+01:00 localhost dovecot: [ID 702911 mail.error] listen_fd(7): Error: 26 46535 BYE 2022-02-14T12:44:24+01:00 localhost dovecot: [ID 702911 mail.error] listen_fd(7): Error: 22 46536 BYE 2022-02-14T12:44:24+01:00 localhost dovecot: [ID 702911 mail.error] listen_fd(7): Error: 26 46534 BYE Thanks for your help, Juerg

1 0

JWT tokens, timestamps and doubles (microseconds)
by Aleš Krajník 14 Feb '22

14 Feb '22

Hi all, I am having troubles with OAuth2 setup with local introspection of JWT tokens. This happens, when the JWT tokens contain timestamps as doubles, with microseconds, for example with the following payload: { "aud": "caf65d650022e3eb7cce518e7526a39f", "jti": "8291efed41d2ce65ec5c59a4cbcaa285f2ca37d5b2785da56de66adbd1b8eef65495bc 599be5ac56", "iat": 1644833538.793359, "nbf": 1644833538.79336, "exp": 1644833838.773605, "sub": "ales(a)example.com", "scope": "email" } Such a JWT token produces the following error: dovecot_1 | Feb 14 10:10:46 auth: Info: oauth2(ales(a)example.com,192.168.224.2,<xWZFoffXYujAqOAC>): oauth2 failed: Local validation failed: Malformed 'exp' field According to the RFC, the timestamps seem to be allowed to contain non- integer values: NumericDate A JSON numeric value representing the number of seconds from 1970- 01-01T00:00:00Z UTC until the specified UTC date/time, ignoring leap seconds. This is equivalent to the IEEE Std 1003.1, 2013 Edition [POSIX.1] definition "Seconds Since the Epoch", in which each day is accounted for by exactly 86400 seconds, other than that non-integer values can be represented. See RFC 3339 [RFC3339] for details regarding date/times in general and UTC in particular. (https://datatracker.ietf.org/doc/html/draft-ietf-oauth-json-web-token-32#se…) After removing the fractions, the token works well. This seems to be happening here: https://github.com/dovecot/core/blob/master/src/lib-oauth2/oauth2-jwt.c#L41 If you agree for this to be a bug, can I fill in a bug report somewhere? Thank you! Best, Aleš

2 1

wondering if I configured sieve vacation correctly
by Marc 14 Feb '22

14 Feb '22

I have a user who feels compelled to use the vacation as autoreply to confirm that a message has been received. The down side is of course, that if spam/abuse messages get through the spam filters, this can get 'messy'. Currently I am getting these ndr's as postmaster(?). But I was not actually expecting this. I would expect that the mailbox with the autoreply would get this report. The vacation is configured like this[1], my question is. What am I doing wrong that this ndr is not ending up in the users mailbox? Can it be the from is not correctly configured/set at the time the vacation message is being sent? [1] require ["vacation"]; # rule:[cccccccccc] if true { vacation :addresses "test(a)test.com" :from "test(a)test.com" text: dddddddddddddd } [2] Return-Path: <> Received: from aaaaa (localhost [127.0.0.1]) by aaaaa (8.14.7/8.14.7) with ESMTP id 21BDgaPj014029 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <postyk(a)hm.edu>; Fri, 11 Feb 2022 14:42:36 +0100 Received: (from root@localhost) by aaaaa (8.14.7/8.14.7/Submit) id 21BDgamD014028 for postyk(a)hm.edu; Fri, 11 Feb 2022 14:42:36 +0100 X-Sieve: Pigeonhole Sieve 0.4.24 (124e06aa) Message-ID: <dovecot-sieve-1644586956-19320-0@bbbb> Date: Fri, 11 Feb 2022 14:42:36 +0100 From: test(a)test.com To: <postyk(a)hm.edu>

1 1

Backup procedures
by Jorge Bastos 13 Feb '22

13 Feb '22

Howdy, I have a particular situation where I have about 5 users using a large account in IMAP, and I have the need to backup the account daily or weekly or so. I was thinking about to copy the whole directory, each email is a file, it could probably work, but the dovecot index files would be damaged/wrong. Is there a tool that could perform a backup (ex: yesterday), and when I inserted that backup, it just insert the emails and folders that were deleted today? Thanks in advanced, Jorge

5 8

LMTP Crash with Dovecot 2.3.18
by Bryan Jacobs 13 Feb '22

13 Feb '22

Dear Dovecot Users, Upgrading from Dovecot 2.3.14 to 2.3.18 on Arch gives me the following dump immediately (100% of the time) on every LMTP handler invocation. Of course I'm using Squat for FTS (yes, I understand it's deprecated...). plugin { fts = squat fts_squat = partial=4 full=4 fts_autoindex = yes sieve = file:/mnt/mail/%Ln/sieve;active=/mnt/mail/%Ln/.dovecot.sieve master_user = %u } lmtp[592878]: segfault at 50 ip 00007f5355153eed sp 00007fff45b87ba0 error 4 in lib20_fts_plugin.so[7f5355153000+11000] Code: 00 4c 8d 05 f9 17 01 00 48 8d 0d ae 19 01 00 31 c0 ba 53 01 00 00 48 8d 35 f2 17 01 00 48 8d 3d 49 01 01 00 ff 15 53 7f 03 00 <48> 8b 04 25 50 00 00 00 0f 0b be 2a 01 00 00 8d 3d cf 17 01 00 > Feb 08 01:23:20 mail systemd-coredump[592880]: [🡕] Process 592878 (lmtp) of user 0 dumped core. > > Module linux-vdso.so.1 with build-id 0f9bd6468a3798a863048e6cd927830796809b46 > Module libffi.so.8 with build-id f90d8b734f6de9b25faedb8cbfab7054dafc0a42 > Module libp11-kit.so.0 with build-id cc372ea3c28c4d3dfc633b4d2e933c8584d2af16 > Module libcrypt.so.2 with build-id 5d45bdae438c16d52364b23d70bd5041ad070b0b > Module librt.so.1 with build-id 75484da2d6f1515189eefa076e0a40328834cd16 > Module libnss_systemd.so.2 with build-id 56da60140e2f0e47044a141378608146f6fd9bb8 > Module libnss_files.so.2 with build-id 1a36dfc01d3a1010b2ee79766a24a8090a3266d5 > Module libdovecot-sieve.so.0 with build-id a358da532b8ef09782b5a97a951df8ab5c8eb0db > Module lib90_sieve_plugin.so with build-id eb52835c5c3d1034617e745995b950484faed909 > Module lib21_fts_squat_plugin.so with build-id cc731fa9bf9cac2f890bbc1da598e958cb465d52 > Module libicudata.so.70 with build-id e1dcc2a88cfaafed882d09c90c668af0eed4efed > Module libgcc_s.so.1 with build-id 7f8508bb914546ada778809b64b99d234337d835 > Module libm.so.6 with build-id 2b8fd1f869ecab4e0b55e92f2f151897f6818acf > Module libstdc++.so.6 with build-id 9b5eeeb149bf3c4efe787fb398b44f00507aec87 > Module libicuuc.so.70 with build-id 2e245c2bf12f95fd8ab79b3a4be99524677cbd70 > Module libicui18n.so.70 with build-id 95af755fca990df26753a7d720b8e3ae24270e42 > Module lib20_fts_plugin.so with build-id 5b44deef3cd93f2cdac9a38ab3f5c4f1a2f48d40 > Module lib10_quota_plugin.so with build-id 5fa33175575dcf45f4aead56c701fe58a19f0df8 > Module libpthread.so.0 with build-id 07c8f95b4f3251d08550217ad8a1f31066229996 > Module libcrypto.so.1.1 with build-id 4c926b672d97886b123e03a008387aecf0786de4 > Module libssl.so.1.1 with build-id 1024424ab33a3767da03f4fdb1fc1b02479f160f > Module libssl_iostream_openssl.so with build-id ba2cf9015fbabf8459896bd584379f2f566aaa51 > Module ld-linux-x86-64.so.2 with build-id 040cc3dd10461562f177df39e3be2f3704258c3c > Module libdl.so.2 with build-id 5abc547e7b0949f89f3c0e21ab0c8331a7440a8a > Module libc.so.6 with build-id 4b406737057708c0e4c642345a703c47a61c73dc > Module libdovecot.so.0 with build-id 3f68ab1f1e0bffceea1c130e6b46f799eea45522 > Module libdovecot-storage.so.0 with build-id 3bf1e7c355c0c6184165e209f67b3a6627355401 > Module libdovecot-lda.so.0 with build-id 54cc9d9face18809a95ccd5ee643330eed997d8b > Module lmtp with build-id 7cc9238bb78e35771572aa3e31bdecf1cda5d754 > Stack trace of thread 592878: > #0 0x00007f5355153eed n/a (lib20_fts_plugin.so + 0x9eed) > #1 0x00007f535515db30 fts_mailbox_allocated (lib20_fts_plugin.so + 0x13b30) > #2 0x00007f535595eb6d hook_mailbox_allocated (libdovecot-storage.so.0 + 0x60b6d) > #3 0x00007f53559598ec mailbox_alloc (libdovecot-storage.so.0 + 0x5b8ec) > #4 0x00007f5355959b5e mailbox_alloc_for_user (libdovecot-storage.so.0 + 0x5bb5e) > #5 0x00007f5355a6d790 mail_deliver_save_open (libdovecot-lda.so.0 + 0x4790) > #6 0x00007f5355a6dbdc mail_deliver_save (libdovecot-lda.so.0 + 0x4bdc) > #7 0x00007f5355a6e39a mail_deliver (libdovecot-lda.so.0 + 0x539a) > #8 0x0000563d3a90bc2d lmtp_local_default_deliver (lmtp + 0x8c2d) > #9 0x0000563d3a90c39f lmtp_local_data (lmtp + 0x939f) > #10 0x0000563d3a90acc1 client_default_cmd_data (lmtp + 0x7cc1) > #11 0x0000563d3a90aa31 cmd_data_continue (lmtp + 0x7a31) > #12 0x00007f535579c3bf n/a (libdovecot.so.0 + 0x6d3bf) > #13 0x00007f535579cc46 n/a (libdovecot.so.0 + 0x6dc46) > #14 0x00007f53557a023e smtp_server_command_call_hooks (libdovecot.so.0 + 0x7123e) > #15 0x00007f53557a07f1 smtp_server_command_next_to_reply (libdovecot.so.0 + 0x717f1) > #16 0x00007f53557a5b5b n/a (libdovecot.so.0 + 0x76b5b) > #17 0x00007f535584469f io_loop_call_io (libdovecot.so.0 + 0x11569f) > #18 0x00007f5355844787 io_loop_handler_run (libdovecot.so.0 + 0x115787) > #19 0x00007f5355844919 io_loop_run (libdovecot.so.0 + 0x115919) > #20 0x00007f53557b31d8 master_service_run (libdovecot.so.0 + 0x841d8) > #21 0x0000563d3a909606 main (lmtp + 0x6606) > #22 0x00007f535557bb25 __libc_start_main (libc.so.6 + 0x27b25) Thanks, Bryan Jacobs

2 1

Dovecot installation problem (libssl_iostream_openssl.so is not portable!)
by Dimitri 11 Feb '22

11 Feb '22

Hi there, i finally solved the problem. On my server i always used openssl compiled from source with the following configuration options: > ./config --prefix=/test/dep/openssl --openssldir=/test/dep/openssl no-deprecated no-ssl The error when i try to compile dovecot tell about undefined references: > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `OBJ_cleanup' > > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_CTX_need_tmp_RSA' > > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_load_error_strings' > > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `ENGINE_cleanup' > > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `ERR_free_strings' > > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `EVP_cleanup' > > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_library_init' > > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `CRYPTO_cleanup_all_ex_data' > > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_CTX_set_tmp_rsa_callback' > > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `OpenSSL_add_all_algorithms' for example "OBJ_cleanup". So i check these functions on the openssl documentation an saw the notice about "deprecated function since OpenSSL 1.1.0" Therefore i recompiled openssl with the following configuration options: > ./config --prefix=/test/dep/openssl --openssldir=/test/dep/openssl --api=1.0.0 After that the compilation of dovecot was successful. It seems that dovecot still uses now deprecated functions from openssl befor version 1.1.0 Can anyone tell me when dovecot doesn't need this deprecated functions anymore? Thanks!

1 0

Hanging doveadm-server processes with dsync replication
by Sebastian Marske 10 Feb '22

10 Feb '22

Dear Dovecot mailing list, after updating Dovecot from 2.3.16 to 2.3.18 on a dsync-replicated server there are hanging doveadm-server processes piling up over time, eventually resulting in some of the affected users being shown as out of sync. Our setup is based on FreeBSD 13, ZFS and Dovecot (we use custom packages built with poudriere) with master/master replication using dsync. However, we use a shared ip (Carp), so that only one server is actually active. Please see the output of "doveconf -n" at the end for our config. Starting from an in-sync state, I updated Dovecot on the inactive server. Occasionally, Dovecot logs messages like: Feb 8 15:02:15 myhost dovecot[99800]: doveadm(someuser)<2090><ZLayIal3AmIqCAAADKIhQg>: Error: write(<local>) failed: Timed out after 60 seconds These occur for an increasing number of users (maybe 30 after two days), but not for every user (there are >4800 users on that server) and also only once for every affected user. Here's some more information about the process/user from the log entry: # doveadm replicator dsync-status username type status someuser incremental Waiting for dsync to finish (the type is "incremental for most users, but "normal" and "full" show up as well) # doveadm replicator status someuser username priority fast sync full sync success sync failed someuser low 00:01:51 21:56:06 69:56:10 y (again, not all are in failed state) # top -abp 2090 PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 2090 sysdov 1 20 0 26M 15M kqread 12 0:01 0.00% doveadm-server: [<local>] (doveadm-server) (didn't change for >1d) # top -m io -abp 2090 PID USERNAME VCSW IVCSW READ WRITE FAULT TOTAL PERCENT COMMAND 2090 sysdov 363 58 0 271 2 273 0.00% doveadm-server: [<local>] (doveadm-server) (didn't change for >1d) # gdb -p 2090 ... (gdb stuff; gdb complaining about missing debug symbols) (gdb) bt full #0 0x00000000416a94ca in _kevent () from /lib/libc.so.7 No symbol table info available. #1 0x00000000419b94f3 in ?? () from /lib/libthr.so.3 No symbol table info available. #2 0x000000004152a645 in io_loop_handler_run_internal () from /usr/local/lib/dovecot/libdovecot.so.0 No symbol table info available. #3 0x00000000415282fa in io_loop_handler_run () from /usr/local/lib/dovecot/libdovecot.so.0 No symbol table info available. #4 0x0000000041528138 in io_loop_run () from /usr/local/lib/dovecot/libdovecot.so.0 No symbol table info available. #5 0x000000004148ac58 in master_service_run () from /usr/local/lib/dovecot/libdovecot.so.0 No symbol table info available. #6 0x0000000001086431 in main () No symbol table info available. (gdb) So I guess it's waiting for something that * doesn't happen on my system * or it didn't wait for in 2.3.16 >From what I've seen, mails from the active server (still on 2.3.16) are replicated to this server. For non-affected users, mails are also replicated from this server to the active one. I can't tell about "outgoing" replication for affected users, yet. After downgrading back to 2.3.16, things are fine again. Most affected users jump back to being successfully synced within a couple of minutes. If not, starting replication via doveadm get's them there. Testing 2.3.18 again, it seems that the same users are affected again. I also tested 2.3.17 when it came out and had the same issue, paired with the ioloop issue [1], which was fixed in 2.3.18 and which I don't see anymore. The hanging doveadm processes remain, though. Do you have any suggestions on how to resolve this? [1] https://dovecot.org/pipermail/dovecot/2022-January/123907.html Best regards Sebastian # doveconf -n # 2.3.18 (9dd8408c18): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.18 (0bc28b32) # OS: FreeBSD 13.0-RELEASE-p6 amd64 # Hostname: myhost... auth_cache_ttl = 0 auth_username_chars = abcdefghijklmnopqrstuvwxyz01234567890@.- auth_username_format = %n default_client_limit = 126000 default_process_limit = 50000 default_vsz_limit = 512 M doveadm_password = # hidden, use -P to show it first_valid_gid = 20 first_valid_uid = 20 imap_client_workarounds = tb-extra-mailbox-sep imap_logout_format = in=%i out=%o delflag=%{deleted} deleted=%{expunged} trashed=%{trashed} session=<%{session}> login_trusted_networks = # imap proxy ips... mail_gid = sysdov mail_location = maildir:~/maildir:INDEX=/addons/index/%u:CONTROL=~/control:LAYOUT=fs mail_plugins = acl notify replication mail_uid = sysdov 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 editheader namespace fremdeordner { list = yes location = maildir:%%h/maildir:INDEX=/addons/index/%u/FremdeOrdner/%%u:LAYOUT=fs prefix = FremdeOrdner/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes list = yes location = mailbox Archive { auto = no special_use = \Archive } mailbox Archives { special_use = \Archive } mailbox AutoCleanSpam { auto = subscribe } mailbox "Deleted Items" { special_use = \Trash } mailbox "Deleted Messages" { special_use = \Trash } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Entwürfe { special_use = \Drafts } mailbox "Gelöschte Elemente" { special_use = \Trash } mailbox "Gesendete Elemente" { special_use = \Sent } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Items" { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } mailbox name { special_use = \Drafts \Junk \Sent \Trash \Archive } prefix = separator = / subscriptions = yes type = private } passdb { args = /usr/local/etc/dovecot/deny-users deny = yes driver = passwd-file } passdb { args = failure_show_msg=yes dovecot driver = pam } plugin { acl = vfile acl_shared_dict = file:/addons/acl/shared-folder mail_replica = tcp:myreplica...:12345 sieve = /addons/sieve/%u.sieve sieve_dir = sieve_extensions = +imap4flags +editheader sieve_vacation_dont_check_recipient = yes } protocols = imap lmtp replication_dsync_parameters = -d -n 'inbox' -l 30 -U replication_max_conns = 150 service aggregator { fifo_listener replication-notify-fifo { user = sysdov } unix_listener replication-notify { user = sysdov } } service anvil { client_limit = 60003 unix_listener anvil-auth-penalty { mode = 00 } unix_listener anvil { group = nagios mode = 0660 } } service auth { client_limit = 126000 unix_listener auth-userdb { mode = 0644 user = sysdov } } service config { unix_listener config { user = sysdov } } service doveadm { inet_listener { port = 12345 } user = sysdov vsz_limit = 1 G } service imap-login { client_limit = 20000 process_limit = 10000 process_min_avail = 138 service_count = 0 } service imap { process_limit = 80000 process_min_avail = 10 vsz_limit = 512 M } service lmtp { client_limit = 1 executable = lmtp -L process_min_avail = 20 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = sysdov } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = sysdov } } ssl_cert = </usr/local/etc/letsencrypt/live/myhost/fullchain.pem ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { default_fields = mail_replica=tcp:myreplica...:12345 driver = passwd override_fields = uid=29 gid=29 blocking=yes } verbose_proctitle = yes protocol imap { login_trusted_networks = # imap proxy ips... mail_max_userip_connections = 25 mail_plugins = acl notify replication acl imap_acl } protocol lmtp { mail_plugins = acl notify replication sieve postmaster_address = postmaster@... sendmail_path = /usr/local/sbin/sendmail }

1 0

Different handling of upper and lower case while indexing/searching with Solr
by Patrik Peng 10 Feb '22

10 Feb '22

Hello there We stumbled upon an user account with Solr FTS, which returned no search results for any given search query. Further investigation revealed an issue between indexing mails and querying the index. The user name contains upper and lower case characters (eg. Some.User(a)domain.net) When new mail is indexed for this user, the user name used for Solr's `user` and `id` fields are transformed into lowercase, as shown in the Solr log: webapp=/solr path=/update params={...}{add=[8543/426f3b0348d03451a3fb00008ba2b673/some.user(a)domain.net (1724281617442144256), ... (162 adds)]} 0 44298 And can be confirmed by manually querying Solr. The Solr schema in use performs no transformation for the affected fields. When a search request is performed via IMAP, Dovecot queries Solr with the original user name: GET /solr/dovecot_fts_popimap/select?wt=json&f...&fq=%2Bbox:1a30ec359dce3451b8e600008ba2b673+%2Buser:Some.User@domain.net HTTP/1.1" Which (correctly) returns zero results. To summarize, I suspect dovecot transforms any user name to lower case while indexing mails, but not when querying for results. Is this a bug, or caused by misconfiguration? Regards Patrik

3 9

Outlook 2019 and push notifications
by Laura Smith 10 Feb '22

10 Feb '22

Is there some secret config sauce I'm unaware of to get IMAP push notifications working with Outlook ? My present situation is that non-Outlook users (e.g. Apple iOS, Apple Mail etc.) work perfectly with the config below. New emails get pushed, deletes get reflected, all is happy in the world. But with Outlook nothing. You send a user an email, nothing happens in their inbox until you manually refresh by checking for new mails or waiting for the auto-check to kick in (sometimes switching between IMAP folders also does the trick). I know Outlook has a long history of being a mess when it comes to standards compliance, but surely it can't be this bad ? doveconf -n : # 2.3.18 (9dd8408c18): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.18 (0bc28b32) # OS: Linux 5.10.0-11-amd64 x86_64 Debian 11.2 xfs # Hostname: foobar.example.com auth_verbose = yes auth_verbose_passwords = sha1:7 doveadm_password = # hidden, use -P to show it imap_capability = +SPECIAL-USE imapc_features = rfc822.size fetch-headers fetch-bodystructure imapc_port = 993 imapc_ssl = imaps mail_location = maildir:/foo_data/mail/%d/%n/Maildir mail_plugins = notify replication push_notification 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 imapsieve vnd.dovecot.imapsieve namespace inbox { inbox = yes location = mailbox "Deleted Messages" { auto = no special_use = \Trash } mailbox Drafts { special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/local_sql_users.conf driver = sql } plugin { imapsieve_mailbox1_before = file:/etc/dovecot/imap_sieve/spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/etc/dovecot/imap_sieve/ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * sieve = file:~/sieve;active=~/.dovecot.sieve sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_pipe_bin_dir = /etc/dovecot/imap_sieve sieve_plugins = sieve_imapsieve sieve_extprograms } protocols = imap lmtp sieve service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } vsz_limit = 2 G } service doveadm { inet_listener { port = 11867 ssl = yes } } service imap-login { process_min_avail = 5 service_count = 1 } service lmtp { process_min_avail = 5 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } user = foo_virtmail } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieves { address = port = 5190 ssl = yes } } ssl = required ssl_ca = </etc/foobar/ssl/certificates/_.example.com.issuer.crt ssl_cert = </etc/foobar/ssl/certificates/_.example.com.crt ssl_cipher_list = ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384 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/local_sql_users.conf default_fields = uid=foo_virtmail gid=foo_virtmail home=/foo_data/mail/%d/%n driver = sql } protocol lmtp { mail_plugins = notify replication push_notification sieve postmaster_address = foo(a)foobar.com } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = notify replication push_notification sieve postmaster_address = postmaster quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r } protocol imap { mail_max_userip_connections = 20 mail_plugins = notify replication push_notification imap_sieve }

2 1

Certificate and showing a sign-cert not there
by Wayne Spivak 10 Feb '22

10 Feb '22

Hi - I am running Postfix 3.6.4 with Dovecot 2.3.17.1 (476cd46418). I have a multi-signed cert from Entrust. The cert works fine on port 25. However, on Port 587 I get an error: c [root@mcq wbs]# openssl s_client -connect mcq.sbanetweb.com:993 -servername mcq.sbanetweb.com CONNECTED(00000003) depth=0 C = US, ST = New York, L = Bellmore, O = SBA Consulting LTD, CN = mcq.sbanetweb.com verify error:num=20:unable to get local issuer certificate verify return:1 depth=0 C = US, ST = New York, L = Bellmore, O = SBA Consulting LTD, CN = mcq.sbanetweb.com verify error:num=21:unable to verify the first certificate verify return:1 depth=0 C = US, ST = New York, L = Bellmore, O = SBA Consulting LTD, CN = mcq.sbanetweb.com verify return:1 --- Certificate chain 0 s:C = US, ST = New York, L = Bellmore, O = SBA Consulting LTD, CN = mcq.sbanetweb.com i:C = US, O = "Entrust, Inc.", OU = See www.entrust.net/legal-terms <http://www.entrust.net/legal-terms> , OU = "(c) 2012 Entrust, Inc. - for authorized use only", CN = Entrust Certification Authority - L1K [root@mcq wbs]# dovecot -n # 2.3.17.1 (476cd46418): /etc/dovecot/dovecot.conf # OS: Linux 5.16.5-200.fc35.x86_64 x86_64 Fedora release 35 (Thirty Five) # Hostname: mcq.sbanetweb.com auth_mechanisms = plain login disable_plaintext_auth = no mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = postfix mode = 0666 user = postfix } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service submission-login { inet_listener submission { port = 587 } } ssl = required ssl_cert = </etc/postfix/tls/ServerCertificate.pem ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-G CM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AE S128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA25 6:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE- ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES1 28-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE -DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES12 8-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNUL L:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-D ES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_client_ca_dir = /etc/postfix/tls/ ssl_client_ca_file = ChainBundle.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { driver = passwd } protocol imap { mail_max_userip_connections = 15 } Any ideas? Wayne Spivak SBANETWEB.com

5 9

Config for filtering (ignoring) specific mbox mail folders?
by John Hardin 08 Feb '22

08 Feb '22

Folks: I'm migrating to Dovecot to provide IMAP services for my personal network. I have more than a couple of decades of mail in multiple (1000+) mbox mail files, but I don't care to expose all of those to IMAP. Is there any way to filter out what mail folders Dovecot will LIST and provide access to using globs or regular expressions? I'd prefer to avoid rearranging the mbox files (e.g. to subdirectories) if possible. I looked through the Dovecot documentation and didn't see anything promising, and I couldn't find any discussion of the topic online. The feature that looked like it might be closest was Namespaces, but I couldn't see how to use that to ignore specific mbox files. Is there any facility within Dovecot (or a plugin) to filter out / ignore mail folders by name, RE or file glob? Thanks in advance! -- John Hardin KA7OHZ http://www.impsec.org/~jhardin/ jhardin(a)impsec.org pgpk -a jhardin(a)impsec.org key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79

1 0

Re: On mailbox full, retry for 4 days or similar instead of reject
by Jorge Bastos 08 Feb '22

08 Feb '22

Hi Lucas, Oh, it's so damn simple! Thank you!! Thank you all others aswell, i've read all info sent, thanks!! Jorge On 2022-02-07 22:57, Lucas Rolff wrote: > An option is to use > https://doc.dovecot.org/settings/core/#core_setting-quota_full_tempfail > - you can configure it e.g. > > protocol lda { > quota_full_tempfail = yes > } > >> On 7 Feb 2022, at 23:41, Jorge Bastos <mysql.jorge(a)decimal.pt> wrote: >> >> Howdy, >> >> I don't know if this is dovecot specific and i guess it may not be at >> 100% so I ask for help. >> >> I want postfix not to discard the message imediatly when a mailbox is >> full, i mean when postfix tries to deliver it to dovecot lmtp. >> Is it possible to change the behavior to something like what postfix >> does when he tries to deliver a message to an external server and the >> server is unaccessible for 4 days (the default i guess), and if in >> that period discard it. >> >> Does this exists? At least i know gmail does something similar to >> this. >> >> I've tried to google a bit but didn't found info that could lead me to >> this configuration. >> >> Thanks in advanced, >> Jorge

1 1

sieve: destination folder lookup in database?
by Hadmut Danisch 08 Feb '22

08 Feb '22

Hi, is there a way to lookup the action for an incoming mail, especially which folder to move the mail in, in a database? Given Problem: I want to replace the mda mailfilter/maildrop with dovecot/sieve. The mailfilter script is rather short, but looksup the destination folder by querying a berkeley database file with the sender's address to find the target folder, using the sender's address as an index. This way, it can store the target folder for hunders or thousands of senders, without needing to compare every single one of them by if == elsif == else... Is there a similar method for dovecot / sieve? I found that dovecot's sieve has some database connections, e.g. LDAP or https://doc.dovecot.org/configuration_manual/sieve/dict/ but rather to receive the whole sieve script for a given recipient as the owner of the mailbox. Is there a way to determine the target folder where to drop a mail into quickly by the sender's address, even for thousands, without the need to compare every single one of them? regards Hadmut

2 2

sieve script to alter subject of incoming message after lookup
by Marc 08 Feb '22

08 Feb '22

Is it possible with sieve to : 1. get sender of an email 2. lookup if this sender is present in an mailbox 3. if the sender is known, change the subject of the email. if the sender is not known, do nothing. 4. put/leave message in inbox. or maybe use dictionary (not really familiar with this) 1. get sender of an email 2. lookup if this sender is present in an dictionary 3. if the sender is known, change the subject of the email. if the sender is not known, do nothing. 4. put/leave message in inbox. But then I need something like 1. if message is dragged into a specific mailbox/folder 2. add sender to dictionary 1. if message is removed from a specific mailbox/folder 2. remove sender from dictionary

1 0

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

07 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): 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?

1 0

Lucene support for FTS - EOL date.
by Jacek Grabowski 07 Feb '22

07 Feb '22

Hello Actually on the https://doc.dovecot.org/configuration_manual/fts/lucene/ site we can read about lucene fts plugin: "This plugin is no longer maintained in Dovecot (as of 2.3+) and will be removed in the future." Does anyone know about approximate EOL date for lucene plugin support in Dovecot? -- Pozdrawiam. Jacek Grabowski.

6 8

Dovecot v2.3.17.1 Released
by Aki Tuomi 07 Feb '22

07 Feb '22

We are happy to announce 2.3.17.1 patch release of Dovecot. This contains some fixes for issues found after 2.3.17 release. https://dovecot.org/releases/2.3/dovecot-2.3.17.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.17.1.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Aki Tuomi Open-Xchange oy -- - dsync: Add back accidentically removed parameters. - lib-ssl-iostream: Fix assert-crash when OpenSSL returned syscall error without errno. - master: Dovecot failed to start if ssl_ca was too large.

7 8

test-file-cache.c needs #ifdef HAVE_RLIMIT_AS
by Rupert Gallagher 07 Feb '22

07 Feb '22

test-file-cache.c:259:24: error: use of undeclared identifier 'RLIMIT_AS' test_assert(getrlimit(RLIMIT_AS, &rl_cur) == 0); ^ test-file-cache.c:267:24: error: use of undeclared identifier 'RLIMIT_AS' test_assert(setrlimit(RLIMIT_AS, &rl_new) == 0); ^ test-file-cache.c:270:24: error: use of undeclared identifier 'RLIMIT_AS' test_assert(setrlimit(RLIMIT_AS, &rl_cur) == 0); ^ test-file-cache.c:276:24: error: use of undeclared identifier 'RLIMIT_AS' test_assert(setrlimit(RLIMIT_AS, &rl_new) == 0); ^ test-file-cache.c:279:24: error: use of undeclared identifier 'RLIMIT_AS' test_assert(setrlimit(RLIMIT_AS, &rl_cur) == 0); ^

3 9

v2.3.17 quota-dict related sql errors
by Pascal Volk 06 Feb '22

06 Feb '22

Hi there, I've updated Dovecot from v2.3.14 (cee3cbc0d) to v2.3.17 (e2aa53df5b). Right after the update, dovecot begun flooding the mail.log and PostgreSQL's log. My dict sql configuration: ,--[ .../dovecot/dovecot-dict-sql.conf.ext ]-- | map { | pattern = priv/quota/storage | table = userquota | username_field = uid | value_field = bytes | } | map { | pattern = priv/quota/messages | table = userquota | username_field = uid | value_field = messages | } `-- This worked for decades. Since the update dovecot is passing the user's email address, instead the user's UID to the query. And therefor I have lots of errors in the log files: see attached `mail.log' and `postgresql-14-main.log' excerpts. The `userquota' table looks like this: Table "public.userquota" Column | Type | Collation | Nullable | Default ----------+---------+-----------+----------+--------- uid | bigint | | not null | bytes | bigint | | not null | 0 messages | integer | | not null | 0 ... Foreign-key constraints: "fkey_userquota_uid_users" FOREIGN KEY (uid) REFERENCES users(uid) ON DELETE CASCADE (full database structure: https://bitbucket.org/pvo/vmm/src/vmm-0.7.0/pgsql/create_tables.pgsql) Regards, Pascal -- Ubuntu is an ancient African word meaning “I can’t install Debian.” -- unknown

3 4

Can't get it to work with conf.d files
by Ruben Safir 06 Feb '22

06 Feb '22

I am trying to set up dovecot to be a sasl auithenticator for postfix but it can't get it to function even on the most fundemental level /usr/bin/dovecot -a -F -c /etc/dovecot/dovecot.conf # 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/15-mailboxes.conf line 48: Unknown setting: service { namespace { namespace and before this, when I tried to get 10-ssl to work it said the same thing - unknonw setting Somewhere it is messed up in the syntax of the config files and I don't know where or how to run it down in a debugger. Here is the config file mail2:[root]:/etc/dovecot# grep "^#" -v /etc/dovecot/dovecot.conf|grep -v "^$" protocols = pop3 submission base_dir = /var/run/dovecot/ dict { #quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } !include conf.d/*.conf !include_try local.conf mail2:[root]:/etc/dovecot# -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and extermination camps, but incompatible with living as a free human being. -RI Safir 2013

1 0

Can't get it to work with conf.d files
by Ruben Safir 06 Feb '22

06 Feb '22

I am trying to set up dovecot to be a sasl auithenticator for postfix but it can't get it to function even on the most fundemental level /usr/bin/dovecot -a -F -c /etc/dovecot/dovecot.conf # 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/15-mailboxes.conf line 48: Unknown setting: service { namespace { namespace and before this, when I tried to get 10-ssl to work it said the same thing - unknonw setting Somewhere it is messed up in the syntax of the config files and I don't know where or how to run it down in a debugger. -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and extermination camps, but incompatible with living as a free human being. -RI Safir 2013

1 0

Received invalid SSL certificate: unable to get certificate CRL
by Laura Smith 06 Feb '22

06 Feb '22

I'm having a frustrating problem trying to use "doveadm sync" to pull mails off a server for migration purposes. # 2.3.17.1 (476cd46418): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.17.1 (a1a0b892) # OS: Linux 5.10.0-11-amd64 x86_64 Debian 11.2 I have tried both explicit "ssl_client_ca_dir = /etc/ssl/certs" and commenting it out (i.e. relying on OpenSSL default per the docs) I always get the same: Info: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Internet Security Research Group/CN=ISRG Root X1 (check ssl_client_ca_* se ttings?) Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Internet Sec urity Research Group/CN=ISRG Root X1 (check ssl_client_ca_* settings?) - disconnecting openssl s_client -starttls imap -servername $name -connect $name:143 is happy though: --- Certificate chain 0 s:CN = <REDACTED> i:C = US, O = Let's Encrypt, CN = R3 1 s:C = US, O = Let's Encrypt, CN = R3 i:C = US, O = Internet Security Research Group, CN = ISRG Root X1 2 s:C = US, O = Internet Security Research Group, CN = ISRG Root X1 i:O = Digital Signature Trust Co., CN = DST Root CA X3 --- --- No client certificate CA names sent Peer signing digest: SHA256 Peer signature type: RSA-PSS Server Temp Key: X25519, 253 bits --- SSL handshake has read 4954 bytes and written 412 bytes Verification: OK --- New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384 Server public key is 2048 bit Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE No ALPN negotiated Early data was not sent Verify return code: 0 (ok) ---

4 10

How to "activate" a mail directory?
by Peter Nabbefeld 06 Feb '22

06 Feb '22

Hello, as I need a mailbox locally only just for filtering, I've tried to manually create it (using Maildir as backend): 1. Created a folder in the appropriate location under /home/vmail with subfolders cur, new, tmp. 2. Set the same user:group as for the other folders (i.e. vmail:vmail). 3. Restarted Dovecot and Email-Client (Thunderbird). However, I cannot subscribe to the new folder. What am I missing here? Kind regards, Peter

2 2

Re: [EXT] AW: Re: Dovecot installation problem (libssl_iostream_openssl.so is not portable!)
by Aki Tuomi 04 Feb '22

04 Feb '22

I am not able to reproduce your issue, which makes it very hard to fix this.. Please keep responses on the list. Aki > On 04/02/2022 20:21 Dimitri <dimitri_emich(a)protonmail.com> wrote: > > > Hi Aki, > > yes, i even have reinstalled the whole OS, but still the same error. > > > Sent with ProtonMail Secure Email. > > ------- Original Message ------- > > Aki Tuomi <aki.tuomi(a)open-xchange.com> schrieb am Freitag, 4. Februar 2022 um 19:17: > > > On 04/02/2022 20:14 Dimitri dimitri_emich(a)protonmail.com wrote: > > > > No One? > > > > Nobody there who can help me? > > Did you ensure you cleaned up openssl 3.0 files before trying again? > > Aki

1 0

Dovecot installation problem (libssl_iostream_openssl.so is not portable!)
by Dimitri 04 Feb '22

04 Feb '22

No One? Nobody there who can help me?

2 1

Password Mismatch when connecting from Email Client
by Dr Francis Greaves 04 Feb '22

04 Feb '22

Dear All I have Postfix version 3.3.0, Dovecot Version 2.2.33.2 and PostfixAdmin version 3.3.10 using MySQL on a small device running Ubuntu VERSION="18.04.6 LTS (Bionic Beaver)" for my internal LAN Mail. I have a user mailto:admin@fsoft.nnet with a mailbox setup in PostfixAdmin with a password as 'Test75?' Everything is running fine, but I cannot get my Email Client Thunderbird to connect. I have setup the debugging to see that the correct password is being used, which it is, but I have this error: dovecot: auth-worker(26468): sql(mailto:admin@fsoft.nnet,10.6.10.10,<gB77wjLXGLsKBgoK>): Password mismatch (given password: Test75?) showing that dovecot disagrees!!! Why is this? Is it something to do with the permissions in PostfixAdmin? I did find https://serverfault.com/questions/696715/password-mismatch-in-dovecot-with-… where someone had the same problem. He just tried various passwords until he found one that worked!!!! I have not found any other post about this exact problem. Any help much appreciated. Regards Francis

7 12

Problem with chrooted user, manage-sieve plugin, lmtp and Thunderbird manage sieve extension: wrong symbolic link to active script
by Lev Serebryakov 04 Feb '22

04 Feb '22

I'm not sure, is it dovecot-managesieve plugin or Thunderbird extension. I have virtual users which are "chrooted" to their Maildirs, like this: user_query = SELECT '/usr/home/hosted/v-mail/%d/%n' AS chroot, \ '/' AS home, 'maildir:~/' AS mail, email.uid AS uid, email.gid AS gid FROM \ <snipped> It works perfectly. I'm using sieve and manage-sieve plugins for dovecot. `.dovecot.sieve` link is relative, like this: v-mail@onlyone:~/serebryakov.spb.ru/lev # ls -l .dovecot.sieve lrwxr-xr-x 1 root v-mail 17 Feb 4 18:19 .dovecot.sieve -> sieve/TOTAL.sieve It works. But when I deactivate/activate script via Manage sieve extension in Thunderbird link becomes absolute (with respect to chroot): v-mail@onlyone:~/serebryakov.spb.ru/lev # ls -l .dovecot.sieve lrwxr-xr-x 1 root v-mail 17 Feb 4 18:19 .dovecot.sieve -> /sieve/TOTAL.sieve and delivery agent (LMTP) start to complain: v-mail@onlyone:~/serebryakov.spb.ru/lev # grep .dovecot.sieve /var/log/dovecot.log Feb 04 18:18:42 lmtp(lev(a)serebryakov.spb.ru)<36054><iPQqEtJD/WHWjAAAlMIKZw>: Warning: sieve: file storage: Active sieve script symlink /usr/home/hosted/v-mail/serebryakov.spb.ru/lev/.dovecot.sieve is broken: Invalid/unknown path to storage (points to /sieve). I'm not sure, is it problem of manage-sieve plugin, lmtp sieve plugin or Thunderbird Sieve extension... -- // Black Lion AKA Lev Serebryakov

1 0

Feature request: use`openid_configuration_url` to guess OIDC endpoints and keys
by Éloi Rivard 04 Feb '22

04 Feb '22

Since version 2.3.16 dovecot has a openid_configuration_url [1] configuration parameter. Here is the documentation about this parameter: > Support for RFC 7628 OpenID Discovery (OIDC) can be achieved with > openid_configuration_url setting. Setting this causes Dovecot to report OIDC > configuration URL as openid-configuration element in error JSON. After reading the RFC I understand this brings some context to the error messages, but at first glance I would have expected more from this parameter. - Dovecot could read the userinfo_endpoint option [2] in the OIDC discovery endpoint to guess the IDP userinfo endpoint [3], and make the dovecot introspection_url parameter optional. - Dovecot could read the introspection_endpoint option [4] in the OIDC discovery endpoint to guess the IDP introspection endpoint [5], and make the dovecot tokeninfo_url parameter optional. RFC8414 is still a draft though, but there seems to be a convention about this parameter be called either token_introspection_endpoint or introspection_endpoint. Maybe both could be checked? - Dovecot could read the jwks_uri [4] option in the OIDC discovery endpoint to guess the IDP public keys, and make the local_validation_key_dict dovecot parameter optional. I would suggest to keep the values in introspection_url, tokeninfo_url and local_validation_key_dict if defined, but use the values found in the OIDC discovery endpoint by default. I think this would really help using OAUTH with dovecot. What do you think? [1] https://doc.dovecot.org/configuration_manual/authentication/oauth2/#openid-… [2] https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderMetadata [3] https://openid.net/specs/openid-connect-core-1_0.html#UserInfo [4] https://datatracker.ietf.org/doc/html/rfc8414#section-2 [5] https://datatracker.ietf.org/doc/html/rfc7662

1 0

Dovecot v2.3.18 released
by Aki Tuomi 04 Feb '22

04 Feb '22

Hi all! We are pleased to release v2.3.18 of Dovecot. Debian/Stretch support has now been dropped. CentOS 8 packages have been replaced with RedHat Enterprise Linux 8 packages. These should be compatible with all the various variants. https://dovecot.org/releases/2.3/dovecot-2.3.18.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.18.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Regards, Aki Tuomi Open-Xchange oy -- * Removed mail_cache_lookup_finished event. This event wasn't especially useful, but it increased CPU usage significantly. * fts: Don't index inline base64 encoded content in FTS indexes using the generic tokenizer. This reduces the FTS index sizes by removing input that is very unlikely to be searched for. See https://doc.dovecot.org/configuration_manual/fts/tokenization for details on how base64 is detected. Only applies when using libfts. * lmtp: Session IDs are now preserved through proxied connections, so LMTP sessions can be tracked. This slightly changes the LMTP session ID format by appending ":Tn" (transaction), ":Pn" (proxy connection) and ":Rn" (recipient) counters after the session ID prefix. + Events now have "reason_code" field, which can provide a list of reasons why the event is happening. See https://doc.dovecot.org/admin_manual/event_reasons/ + New events are added. See https://doc.dovecot.org/admin_manual/list_of_events/ + fts: Added fts_header_excludes and fts_header_includes settings to specify which headers to index. See https://doc.dovecot.org/settings/plugin/fts-plugin#plugin-fts-setting-fts-h… for configuration details. + fts: Initialize the textcat language detection library only once per process. This can reduce CPU usage if fts_languages setting has multiple languages listed and service indexer-worker { service_count } isn't 1. Only applies when using libfts. + lib-storage: Reduced CPU usage significantly for some operations that accessed lots of emails (e.g. fetching all flags in a folder, SORT, ...) + lib: DOVECOT_PREREQ() - Add micro version which enables compiling external plugins against different versions of Dovecot. + lmtp: Added new lmtp_verbose_replies setting that makes errors sent to the LMTP client much more verbose with details about why exactly backend proxy connections or commands are failing. + submission: Support implicit SASL EXTERNAL with submission_client_workarounds=implicit-auth-external. This allows automatically logging in when SSL client certificate is present. - *-login: Statistics were disabled if stats process connection was lost. - auth: Authentication master user login fails with SCRAM-* SASL mechanisms. - auth: With auth_cache_verify_password_with_worker=yes, passdb extra fields in the auth cache got lost. - doveadm: Fixed crash if zlib_save_level setting was specified, but zlib_save was unset. v2.3.15 regression. - doveadm: Proxying can panic when flushing print output. v2.3.17 regression. Fixes: Panic: file ioloop.c: line 865 (io_loop_destroy): assertion failed: (ioloop == current_ioloop) - doveadm: stats add --group-by parameter didn't work. - fts: Using email-address fts tokenizer could result in excessive memory usage with garbage email input. This could cause the indexer-worker processes to fail due to reaching the VSZ memory size limit. Only applies when using libfts. - imap: A SEARCH command timing out while fts returns indexes may timeout returning "NO [SERVERBUG]", while it should return "NO [INUSE]" instead. - imap: LIST-EXTENDED doesn't return STATUS for all folders. Sending LIST .. RETURN (SUBSCRIBED STATUS (...)) did not return STATUS for folders that are not subscribed when they have a child folder that is subscribed as mandated by IMAP RFCs. - imapc: Mailbox vsize calculation crashed with Panic: file index-mailbox-size.c: line 344 (index_mailbox_vsize_hdr_add_missing): assertion failed: (mails_left > 0) - indexer: If indexer-worker crashes, the request it was processing gets stuck in the indexer process. This stops indexing for the folder until indexer process is restarted. v2.3.14 regression. - indexer: Process was slowly leaking memory for each indexing request. - lib-event: Unnamed events were wrongly filtered out for event/metric filters like "event=abc OR something_independent_of_event_name". - lib-index: 64-bit big endian CPUs handle last_used field in dovecot.index.cache wrong. - lib-ssl-iostream: Fix buggy OpenSSL error handling without assert-crashing. If there is no error available, log it as an error instead of crashing. The previous fix for this in v2.3.11 was incomplete. Fixes Panic: file istream-openssl.c: line 51 (i_stream_ssl_read_real): assertion failed: (errno != 0) - lmtp: Out-of-memory issues can happen when proxying large messages to LMTP backend servers that accept the message data too slow. - master: HAProxy header parsing has read buffer overflow if provided header size is invalid. This happens only if inet_listener { haproxy=yes } is configured and only if the remote IP address is in haproxy_trusted_networks. - old_stats: Plugin kept increasing memory usage, which became noticeable with long-running imap sessions. - stats: Dynamically adding same metric multiple times causes multiple stats. - submission-login: Authentication does not accept OAUTH2 token (or other very long credentials) because it considers the line to be too long. - submission-login: Process can crash if HELO is pipelined with an invalid domain. - submission-proxy: Don't use SASL-IR if it would make the AUTH command line longer than 512 bytes. - submission: Service would crash if relay server authentication failed. - virtual: FTS search in a virtual folder could crash if there are duplicate mailbox GUIDs. This mainly happened when user had both INBOX and INBOX/INBOX folders and the namespace prefix was INBOX/. Fixes Panic: file hash.c: line 252 (hash_table_insert_node): assertion failed: (opcode == HASH_TABLE_OP_UPDATE) - virtual: If mailbox opening fails, the backend mailbox is leaked and process crashes when client disconnects. Fixes Panic: file mail-user.c: line 232 (mail_user_deinit): assertion failed: ((*user)->refcount == 1) - virtual: Searching headers in virtual folders didn't always use full-text search indexes, if fts_enforced=no or body.

2 1

posible guide
by d 03 Feb '22

03 Feb '22

2 1

Notification about branch and versioning changes
by Aki Tuomi 03 Feb '22

03 Feb '22

Dear subscribers, This year we will be releasing a new Dovecot major release. In preparations for this, we are doing some repository changes, which will affect you if you are using our git repositories. These changes will become effective after 14th of February. Following branch name changes are going to be implemented: - main => this is going to be the main branch in future - master => release-2.3 Note that Dovecot version number on main branch is going to change. The next major CE release will be 2.4.x. The change to a main branch and its version numbering also apply to Pigeonhole. We will also align Pigeonhole release version to match Dovecot, ie. the next major is 2.4.x and not 0.6. We will send more information about the upcoming major release as it progresses. Regards, Aki Tuomi Open-Xchange oy

1 0

Pigeonhole v0.5.18 released
by Aki Tuomi 03 Feb '22

03 Feb '22

Hi all! We are pleased to release v0.5.18 of Pigeonhole. Debian/Stretch support has now been dropped. CentOS 8 packages have been replaced with RedHat Enterprise Linux 8 packages. These should be compatible with all the various variants. https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.18.t… https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.18.t… Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Regards, Aki Tuomi Open-Xchange oy -- - duplicate: Users without a home directory can crash with Sieve when using duplicate database. v2.3.17 regression. - imapsieve: When mail was expunged when processing imapsieve events, a crash could occur. Fixes Panic: file mail-index-map.c: line 558 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0) - managesieve-login: Proxy didn't support forwarding the forward_* passdb fields. - redirect: Sieve would crash if redirect after keep-equivalent action failed. - sieve: Interpreter crashes when the Sieve index extension is used with index zero. - vnd.dovecot.filter: Envelope sender string may become corrupted when Sieve scripts are using vnd.dovecot.filter. This could end up corrupting mbox's From line and return wrong envelope sender string in

1 0

Re: dovecot Digest, Vol 212, Issue 56
by Steve 02 Feb '22

02 Feb '22

Greetings! A signed documentation you can find here: https://meta-calculator.com/tsaenauuovecumpttrqol/oieell-eiemnudai-mosboers… -----Original Message----- On Tuesday, 29 December 2020, 10:00 wrote: > Send dovecot mailing list submissions to dovecot(a)dovecot.org To subscribe > or unsubscribe via the World Wide Web, visit > https://dovecot.org/mailman/listinfo/dovecot or, via email, send a message > with subject or body 'help' to dovecot-request(a)dovecot.org You can reach > the person managing the list at dovecot-owner(a)dovecot.org When replying, > please edit your Subject line so it is more specific than "Re: Contents of > dovecot digest..." Today's Topics: 1. Re: .imap folders (Elise) 2. > dovecot+ldap with keepalive (Maciej Milaszewski) > ---------------------------------------------------------------------- > Message: 1 Date: Mon, 28 Dec 2020 17:16:30 +0100 From: Elise To: Aki Tuomi > Cc: Dovecot Mailing List Subject: Re: .imap folders Message-ID: > Content-Type: text/plain; charset=windows-1252; format=flowed Op 28-12-20 > om 12:56 schreef Aki Tuomi: > in your mail location, where you have > specified `mbox:~/...` > > We do not recommend using mbox mail format for > read-write, as the > support for that is limited. Noted, that did the > trick, thanks. /Elise ------------------------------ Message: 2 Date: Mon, > 28 Dec 2020 22:48:19 +0100 From: Maciej Milaszewski To: dovecot(a)dovecot.org > Subject: dovecot+ldap with keepalive Message-ID: Content-Type: text/plain; > charset=utf-8 Hi I have dovecot-2.36.4 (director +5 nodes) - backend to > auth is openldap+keepalived to second ldap For test i shutdown my ldap > server - keepalive? works perfectly VIP switched - ldapserach works ok (all > connect to second ldap) but I noticed strange dovecot behavior - some user > get "no response" or "waiting waiting" in dovecot i use: > auth_cache_negative_ttl = 5 mins auth_cache_size = 20 M auth_cache_ttl = 5 > mins service lmtp { ? inet_listener lmtp { ??? address = 127.0.0.1 > 10.0.100.4 ??? port = 24 ? } ? process_min_avail = 5 protocol lmtp { ? > auth_socket_path = director-userdb ? mail_plugins = quota expire notify > mail_log ? passdb { ??? args = proxy=y nopassword=y port=24 ??? driver = > static ??? name = ? } ? syslog_facility = local3 } in ldap server i have: > idletimeout???? 256 Any idea ? ------------------------------ Subject: > Digest Footer _______________________________________________ dovecot > mailing list dovecot(a)dovecot.org > https://dovecot.org/mailman/listinfo/dovecot ------------------------------ > End of dovecot Digest, Vol 212, Issue 56 > ****************************************

1 0

How to use virtual "All" and "Flagged" mailbox?
by A B 01 Feb '22

01 Feb '22

Hello, I'm trying to use the virtual "All" and "Flagged" mailboxes as described in 15-mailboxes.conf. The information here ( https://doc.dovecot.org/configuration_manual/virtual_plugin/) doesn't really touch on how to actually interact with the virtual mailboxes. My presumption is that when I mark an email message in the Inbox as FLAGGED (and I can confirm the \Flagged flag has been set) then I should then be able to either (1) see a copy of that message in the virtual.Flagged folder, or (2) when I use an imap command to get the message nums or whatever from the virtual.Flagged folder/mailbox, it should return the message that is flagged in the inbox as a result. Additionally, I'm presuming that for each new user that automatically gets added, I would have to create my own script that would add the dovecot-virtual file, dovecot doesn't do that on its own. When I view the user's directory I see these folders were created: --- [snippet] drwxrwx---. 5 vmail vmail 135 Jan 25 17:01 .virtual.All/ drwxrwx---. 5 vmail vmail 158 Jan 25 17:14 .virtual.Flagged/ [.virtual.Flagged]# ll total 20 drwxrwx---. 5 vmail vmail 158 Jan 25 17:14 ./ drwxrwx---. 20 vmail vmail 4096 Jan 25 17:33 ../ drwxrwx---. 2 vmail vmail 6 Jan 25 16:58 cur/ -rw-rw----. 1 vmail vmail 868 Jan 25 16:58 dovecot.index.cache -rw-rw----. 1 vmail vmail 384 Jan 25 17:01 dovecot.index.log -rw-rw----. 1 vmail vmail 51 Jan 25 17:01 dovecot-uidlist -rw-r--r--. 1 vmail vmail 8 Jan 25 17:14 dovecot-virtual -rw-rw----. 1 vmail vmail 0 Jan 25 16:58 maildirfolder drwxrwx---. 2 vmail vmail 6 Jan 25 16:58 new/ drwxrwx---. 2 vmail vmail 6 Jan 25 16:58 tmp [.virtual.Flagged]# cat dovecot-virtual * flagged --- Side note: This set-up uses the php-imap library to interact with Dovecot. Any help, or just concept of how the virtual/All virtual/Flagged directories work would be really appreciated. CONFIGURATION: dovecot -n # 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf # OS: Linux 4.18.0-348.2.1.el8_5.x86_64 x86_64 CentOS Linux release 8.5.2111 xfs # Hostname: [DOMAIN REDACTED] auth_debug = yes auth_verbose = yes auth_verbose_passwords = yes first_valid_uid = 1000 lda_mailbox_autocreate = yes log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/home/vmail/%d/%n/Maildir mail_plugins = " quota" mbox_write_locks = fcntl namespace { location = virtual:/home/vmail/%d/%n/Maildir/virtual:LAYOUT=maildir++ prefix = virtual. separator = . type = private } namespace inbox { inbox = yes location = mailbox Archive { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } mailbox virtual.All { auto = create comment = All my messages special_use = \All } mailbox virtual.Flagged { auto = create comment = All my flagged messages special_use = \Flagged } prefix = INBOX. separator = . type = private } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { driver = pam } plugin { quota = maildir:User quota quota_grace = 10%% quota_max_mail_size = 30M quota_rule = *:storage=100M quota_rule2 = INBOX.Trash:storage=+10M quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO } protocols = imap pop3 service auth-worker { user = root } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-master { mode = 0600 user = vmail } unix_listener auth-userdb { mode = 0600 user = vmail } user = dovecot } service imap-login { inet_listener imaps { port = 993 ssl = yes } } service pop3-login { inet_listener pop3s { port = 995 ssl = yes } } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { port = 12340 } } service stats { unix_listener stats-reader { group = vmail mode = 0660 user = vmail } unix_listener stats-writer { group = vmail mode = 0660 user = vmail } } ssl = required ssl_cert = </etc/letsencrypt/live/[DOMAIN REDACTED]/fullchain.pem ssl_cipher_list = PROFILE=SYSTEM ssl_key = # hidden, use -P to show it userdb { args = uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes driver = static } userdb { driver = passwd } protocol lda { auth_socket_path = /var/run/dovecot/auth-master log_path = /home/vmail/dovecot-deliver.log postmaster_address = postmaster@[DOMAIN REDACTED] } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } protocol imap { mail_plugins = " quota imap_quota virtual" }

2 4

Quota: read how much diskspace is available?
by Hans van Zijst 01 Feb '22

01 Feb '22

Hi, I've been trying to get domain quotas to work for a while, but to no avail so far. Is there a way to let Dovecot simply check how much space is still available in a directory? I'm using GlusterFS as my mailstore, so I can configure quotas per directory. All I need is a way to let Dovecot check quota in a way like "df /var/vmail/<domain>". Kind regards, Hans

1 0

Set mail crypt private password with OAUTH?
by Max Kostikov 31 Jan '22

31 Jan '22

We currently use Dovecot and mailbox encryption via the mail-crypt-plugin. With standard password authentication, we set the value of the individual password to encrypt the contents of the userdb_mail_crypt_private_password mailbox in the SQL query. Is it possible to set the userdb_mail_crypt_private_password value when authenticating via OAUTH2 ? -- Best regards, Max Kostikov

3 16

PLAIN password scheme issue with {}
by Kris von Mach 31 Jan '22

31 Jan '22

Hello, Using PLAIN password scheme and a user having a password with {} for example {RnDR8DaD} causes the authentication to fail: auth-worker(85632): Error: conn unix:auth-worker (uid=143): auth-worker<3333>: sql(user(a)domain.com,123.45.68.78,<EBh0ouPWULvTF5AQ>): Unknown scheme RnDR8DaD Is there some sort of a workaround for this other than requesting user not to use {} at beginning and end of their password?

2 1

silly quesiton
by steph.mag220＠netcourrier.com 31 Jan '22

31 Jan '22

Hi, Up to now, I used PAM of each user in order to send and receive email. ( BTW, sending email, a use authentication was required and we used the login and passwd of the user on the system Now, for dovecot, I start to use MD5 passwrd.. and that sounds to be OK auth_mechanisms = plain login cram-md5 passdb { driver = passwd-file # Path for passwd-file. Also set the default password scheme. args = scheme=cram-md5 /etc/cram-md5.pwd } But changing the passwrd for the user1.. he can retrieve emails from dovecot, but cannot send anymore, because sending emails kept the old passwrd. ( using the PAM) 1) How can I says sendmail to use the same passwd file ( with MD5) than dovecot ? 2) Ideally, I would like to create virtual users for the same mailbox Is that possible ? like 2 files Users and PAsswrds pointing out the mailbox : maildir :/home/mailbox/user1 ex : user1(a)foo.com passwrd1 /home/mailbox/generic_mails and user2 passwrd2 home/mailbox/generic_mails How can I do that ? Thanks for your help

14 35

Re: dovecot Digest, Vol 225, Issue 73
by David Matthews 31 Jan '22

31 Jan '22

> 5. Re: can't authenticate (Christian Mack) hi Christian log with debugging resulting from a login attempt pasted at end - to try and make it more readable I removed everything in each line up to "dovecot:" At no point is a password revealed, even in hashed form. Should also say that the problem is identical on a backup laptop also running devuan 4; I'm not sure if I ever used that machine with dovecot before it was upgraded from devuan 3. Also I tried creating a new user to see if that account could authenticate; it cannot. >So you only can increase the logging in dovecot for authentication to >debugging. >auth_debug=yes ________________________________________________________________________________ auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth auth: Debug: Module loaded: /usr/lib/dovecot/modules/auth/lib20_auth_var_expand_crypt.so auth: Debug: Read auth token secret from /run/dovecot/auth-token-secret.dat auth: Debug: auth client connected (pid=2467) auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured#011session=osv6w6PW4tB/AAAB#011lip=127.0.0.1#011rip=127.0.0.1#011lport=143#011rport=53474#011resp=<hidden> auth: Debug: pam(fred,127.0.0.1,<osv6w6PW4tB/AAAB>): Performing passdb lookup auth-worker(2469): Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth auth-worker(2469): Debug: Module loaded: /usr/lib/dovecot/modules/auth/lib20_auth_var_expand_crypt.so auth-worker(2469): Debug: conn unix:auth-worker (pid=2468,uid=118): Server accepted connection (fd=13) dovecot: auth-worker(2469): Debug: conn unix:auth-worker (pid=2468,uid=118): Sending version handshake auth-worker(2469): Debug: conn unix:auth-worker (pid=2468,uid=118): auth-worker<1>: Handling PASSV request auth-worker(2469): Debug: conn unix:auth-worker (pid=2468,uid=118): auth-worker<1>: pam(fred,127.0.0.1,<osv6w6PW4tB/AAAB>): Performing passdb lookup auth-worker(2469): Debug: conn unix:auth-worker (pid=2468,uid=118): auth-worker<1>: pam(fred,127.0.0.1,<osv6w6PW4tB/AAAB>): lookup service=dovecot auth-worker: Error: fatal error: failed to reserve page summary memory auth-worker(2469): Debug: conn unix:auth-worker (pid=2468,uid=118): auth-worker<1>: pam(fred,127.0.0.1,<osv6w6PW4tB/AAAB>): #1/1 style=1 msg=Password: auth-worker: Error: auth-worker: Error: runtime stack: auth-worker: Error: runtime.throw(0x7f3b2a6a8292, 0x25) auth-worker: Error: #011runtime/panic.go:1116 +0x74 fp=0x7f3b2a3b5b30 sp=0x7f3b2a3b5b00 pc=0x7f3b2a4d6474 auth-worker: Error: runtime.(*pageAlloc).sysInit(0x7f3b2a894428) auth-worker: Error: #011runtime/mpagealloc_64bit.go:80 +0x185 fp=0x7f3b2a3b5bc0 sp=0x7f3b2a3b5b30 pc=0x7f3b2a4ccb25 auth-worker: Error: runtime.(*pageAlloc).init(0x7f3b2a894428, 0x7f3b2a894420, 0x7f3b2a8aeb18) auth-worker: Error: #011runtime/mpagealloc.go:317 +0x77 fp=0x7f3b2a3b5be8 sp=0x7f3b2a3b5bc0 pc=0x7f3b2a4ca517 auth-worker: Error: runtime.(*mheap).init(0x7f3b2a894420) auth-worker: Error: #011runtime/mheap.go:743 +0x24b fp=0x7f3b2a3b5c10 sp=0x7f3b2a3b5be8 pc=0x7f3b2a4c74cb auth-worker: Error: runtime.mallocinit() auth-worker: Error: #011runtime/malloc.go:480 +0x109 fp=0x7f3b2a3b5c38 sp=0x7f3b2a3b5c10 pc=0x7f3b2a4acc09 auth-worker: Error: runtime.schedinit() auth-worker: Error: #011runtime/proc.go:563 +0x65 fp=0x7f3b2a3b5c90 sp=0x7f3b2a3b5c38 pc=0x7f3b2a4d9e25 auth-worker: Error: runtime.rt0_go(0x7ffd65c5e428, 0x2, 0x7ffd65c5e428, 0x7f3b2a3b6700, 0x7f3b2af22ea7, 0x0, 0x7f3b2a3b6700, 0x7f3b2a3b6700, 0xbe848d2612a1e5f4, 0x7ffd65c5cabe, ...) auth-worker: Error: #011runtime/asm_amd64.s:214 +0x129 fp=0x7f3b2a3b5c98 sp=0x7f3b2a3b5c90 pc=0x7f3b2a508c09 auth: Error: auth worker: Aborted PASSV request for fred: Worker process died unexpectedly auth: Debug: pam(fred,127.0.0.1,<osv6w6PW4tB/AAAB>): Finished passdb lookup dovecot: auth: Debug: auth(fred,127.0.0.1,<osv6w6PW4tB/AAAB>): Auth request finished auth-worker(2469): Fatal: master: service(auth-worker): child 2469 returned error 2 auth-worker(2471): Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth dovecot: auth-worker(2471): Debug: Module loaded: /usr/lib/dovecot/modules/auth/lib20_auth_var_expand_crypt.so auth-worker(2471): Debug: conn unix:auth-worker (pid=2468,uid=118): Server accepted connection (fd=13) auth-worker(2471): Debug: conn unix:auth-worker (pid=2468,uid=118): Sending version handshake auth: Debug: client passdb out: FAIL#0111#011user=fred#011code=temp_fail imap-login: Disconnected (auth service reported temporary failure): user=<fred>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, session=<osv6w6PW4tB/AAAB> ________________________________________________________________________________ >Perhaps you also want to set >auth_debug_passwords=yes >for getting the actual password in plain text. >(Don't forget to disable that afterwards!) ________________________________________________________________________________ auth-worker: Error: fatal error: failed to reserve page summary memory auth-worker: Error: auth-worker: Error: runtime stack: auth-worker: Error: runtime.throw(0x7fc7df48b292, 0x25) auth-worker: Error: #011runtime/panic.go:1116 +0x74 fp=0x7fc7df198b30 sp=0x7fc7df198b00 pc=0x7fc7df2b9474 auth-worker: Error: runtime.(*pageAlloc).sysInit(0x7fc7df677428) auth-worker: Error: #011runtime/mpagealloc_64bit.go:80 +0x185 fp=0x7fc7df198bc0 sp=0x7fc7df198b30 pc=0x7fc7df2afb25 auth-worker: Error: runtime.(*pageAlloc).init(0x7fc7df677428, 0x7fc7df677420, 0x7fc7df691b18) auth-worker: Error: #011runtime/mpagealloc.go:317 +0x77 fp=0x7fc7df198be8 sp=0x7fc7df198bc0 pc=0x7fc7df2ad517 auth-worker: Error: runtime.(*mheap).init(0x7fc7df677420) auth-worker: Error: #011runtime/mheap.go:743 +0x24b fp=0x7fc7df198c10 sp=0x7fc7df198be8 pc=0x7fc7df2aa4cb auth-worker: Error: runtime.mallocinit() auth-worker: Error: #011runtime/malloc.go:480 +0x109 fp=0x7fc7df198c38 sp=0x7fc7df198c10 pc=0x7fc7df28fc09 auth-worker: Error: runtime.schedinit() auth-worker: Error: #011runtime/proc.go:563 +0x65 fp=0x7fc7df198c90 sp=0x7fc7df198c38 pc=0x7fc7df2bce25 auth-worker: Error: runtime.rt0_go(0x7ffc6c109f48, 0x2, 0x7ffc6c109f48, 0x7fc7df199700, 0x7fc7dfd05ea7, 0x0, 0x7fc7df199700, 0x7fc7df199700, 0x1de9f8dc88f21cc1, 0x7ffc6c1085de, ...) auth-worker: Error: #011runtime/asm_amd64.s:214 +0x129 fp=0x7fc7df198c98 sp=0x7fc7df198c90 pc=0x7fc7df2ebc09 auth: Error: auth worker: Aborted PASSV request for fred: Worker process died unexpectedly auth: Debug: pam(fred,127.0.0.1,<RFd4WqPWytB/AAAB>): Finished passdb lookup auth: Debug: auth(fred,127.0.0.1,<RFd4WqPWytB/AAAB>): Auth request finished auth-worker(2282): Fatal: master: service(auth-worker): child 2282 returned error 2 auth-worker(2284): Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth auth-worker(2284): Debug: Module loaded: /usr/lib/dovecot/modules/auth/lib20_auth_var_expand_crypt.so auth-worker(2284): Debug: conn unix:auth-worker (pid=2281,uid=118): Server accepted connection (fd=13) auth-worker(2284): Debug: conn unix:auth-worker (pid=2281,uid=118): Sending version handshake auth: Debug: client passdb out: FAIL#0111#011user=fred#011code=temp_fail imap-login: Disconnected (auth service reported temporary failure): user=<fred>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, session=<RFd4WqPWytB/AAAB> -- David Matthews mail(a)dmatthews.org

2 1

Dovecot installation problem (libssl_iostream_openssl.so is not portable!)
by Dimitri 31 Jan '22

31 Jan '22

Hi there, i try to install dovecot from source with the following configuration: > ./configure --prefix=/test/core/dovecot --with-ssldir=/test/core/dovecot/tls the configuration runs fine with the following output at the end: > Install prefix . : /test/core/dovecot > File offsets ... : 64bit > I/O polling .... : epoll > I/O notifys .... : inotify > SSL ............ : yes (OpenSSL) > GSSAPI ......... : no > passdbs ........ : static passwd passwd-file shadow checkpassword > : -pam -bsdauth -ldap -sql > userdbs ........ : static prefetch passwd passwd-file checkpassword > : -ldap -sql > CFLAGS ......... : -std=gnu99 -g -O2 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -mfunction-return=keep -mindirect-branch=keep -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/test/dep/openssl/include > SYSTEMD ........ : notify - /lib/systemd/system/dovecot.service > SQL drivers .... : > : -pgsql -mysql -sqlite -cassandra > Full text search : squat > : -lucene -solr But when i start to build (make) after a while i get the following error: > *** Warning: Linking the executable test-iostream-ssl against the loadable module > *** libssl_iostream_openssl.so is not portable! > libtool: link: gcc -std=gnu99 -g -O2 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -mfunction-return=keep -mindirect-branch=keep -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/test/dep/openssl/include -o .libs/test-iostream-ssl test-iostream-ssl.o ./.libs/libssl_iostream_openssl.so ./.libs/libssl_iostream.a ../lib-test/.libs/libtest.a ../lib/.libs/liblib.a -L/test/dep/openssl/lib64 -lssl -lcrypto -ldl -Wl,-rpath -Wl,/test/core/dovecot/lib/dovecot > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `ERR_free_strings' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `ENGINE_cleanup' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_library_init' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `OBJ_cleanup' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `CRYPTO_cleanup_all_ex_data' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `OpenSSL_add_all_algorithms' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_CTX_set_tmp_rsa_callback' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `EVP_cleanup' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_load_error_strings' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_CTX_need_tmp_RSA' > collect2: error: ld returned 1 exit status > make[3]: *** [Makefile:655: test-iostream-ssl] Error 1 > make[3]: Leaving directory '/test/tmp/dovecot-2.3.17.1/src/lib-ssl-iostream' > make[2]: *** [Makefile:573: all-recursive] Error 1 > make[2]: Leaving directory '/test/tmp/dovecot-2.3.17.1/src' > make[1]: *** [Makefile:702: all-recursive] Error 1 > make[1]: Leaving directory '/test/tmp/dovecot-2.3.17.1' > make: *** [Makefile:546: all] Error 2 I've searched for the error and find some posts about set explicitly CPPFLAGS and LDFLAGS and something about missing shared libraries of openssl. My openssl have shared libraries (libcrypto.so libssl.so ...) and the explicit use of CPPFLAGS and LDFLAGS to my openssl hasn't changed anything I use Openssl 3.0 but i've tested also 1.1.1m and 1.1.1g for example, same error! Dovecot is the latest 2.3.17.1 My OS is Ubuntu 21.04 Can anyone help me with this please? Thanks!

2 1

Sync via ssh fails when ssl is active
by Johan 31 Jan '22

31 Jan '22

I have computers at two different locations and one computer running dovecot at each place. I sync my emails between these two servers using ssh and I haven't had any problems with this lately until I upgraded dovecot recently. I now get the following error at location "alfa" when trying to sync with dovecot at location "delta" Jan 20 16:13:09 doveadm: Error: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 16: ssl_cert: Can't open file /etc/letsencrypt/live/delta.oxyl.net/fullchain.pem: Permission denied Jan 20 16:13:09 dsync-local(johan(a)oxyl.net)<FWBVNQN86WH52iQA1AGq6A>: Error: read(vmail(a)192.168.119.12) failed: EOF (version not received) Jan 20 16:13:09 dsync-local(johan(a)oxyl.net)<FWBVNQN86WH52iQA1AGq6A>: Error: Remote command returned error 89: ssh -q -p 22 -o StrictHostKeyChecking=no -i /datastorage/epost/vmail/.ssh/id_ecdsa -lvmail 192.168.119.12 doveadm dsync-server -ujohan(a)oxyl.net Trying to sync from "delta" i get the same error but the domain is changed in the error-message to 'alfa.oxyl.net' I can read mail at both locations using STARTTLS. There is no error in dovecot.log when I restart the service. If I disable ssl and comment out ssl_cert/ssl_key in 10-ssl.conf I have no trouble performing sync between servers. If I run the ssh-command in the error-message as user vmail I get the same ssl-error as above. Any ideas how to solve this? /Johan Pålsson

4 6

Dsync replication - delayed replication (Sync lock)
by Daniel Botting 31 Jan '22

31 Jan '22

Hi, *Our setup:* Two Debian 10 machines that are setup to replicate mail between them, we have round robin DNS setup so a user can connect to either server. *What should happen:* Mail is delivered to either server and replicated across straight away to their mailbox on the other server so it does not matter which one they are connected to they will receive it fairly soon after delivery. *What actually happens:* In some instances the user will experience a delayed receipt of messages if they are not connected to the server that the message is initially delivered to, sometimes the delay is 5/10 minutes, we had a recent support ticket submitted where it was over an hour. Error message seen in mail.err: Sep 1 10:16:15 <host name> dovecot: dsync-local(<username>)<WELSGEERTl8FEAAAZJ7A9A>: Error: Couldn't lock /path/to/mailbox/.dovecot-sync.lock: fcntl(/path/to/mailbox/.dovecot-sync.lock, write-lock, F_SETLKW) locking failed: Timed out after 30 seconds (WRITE lock held by pid 3697) Process 3697 is dovecot/doveadm-server. *Doveconf -n output:* # 2.3.10.1 (a3d0e1171): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.10 (67bf5bd7) # OS: Linux 4.19.0-10-amd64 x86_64 Debian 10.5 # Hostname: <server hostname> auth_verbose = yes default_vsz_limit = 0 doveadm_password = # hidden, use -P to show it first_valid_gid = 8 first_valid_uid = 8 last_valid_gid = 8 last_valid_uid = 8 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_gid = 8 mail_location = maildir:~/Maildir mail_plugins = " notify replication" mail_uid = 8 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex im ap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext editheader imapfla gs namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { mail_replica = tcps:<server being replicated to>:<port being used> sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +editheader +imapflags } postmaster_address = postmaster@<domain address> protocols = " imap sieve pop3" replication_max_conns = 12 service aggregator { fifo_listener replication-notify-fifo { user = mail } unix_listener replication-notify { user = mail } } service auth { unix_listener /var/run/dovecot-exim-bridge { mode = 0660 user = Debian-exim } } service doveadm { inet_listener { port = <port being used for replication> ssl = yes } } service imap-login { inet_listener imap { port = 143 } } inet_listener imaps { port = 993 ssl = yes } process_limit = 512 process_min_avail = 4 service_count = 1 } service imap { process_limit = 1024 } service managesieve-login { inet_listener sieve { port = <sieve port> } process_min_avail = 1 service_count = 8 vsz_limit = 256 M } service managesieve { process_limit = 1024 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl = required ssl_cert = </path/to/ssl/cert/fullchain.pem ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL ssl_client_ca_dir = /etc/ssl/certs ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap override_fields = home=/var/mail/%u uid=mail gid=mail } protocol lda { mail_plugins = " notify replication sieve" } protocol imap { mail_max_userip_connections = 32 mail_plugins = " notify replication" } protocol sieve { mail_max_userip_connections = 10 managesieve_logout_format = bytes=%i/%o managesieve_max_line_length = 65536 } Kind regards Daniel

3 3

NTLM fails: dovecot: auth: Fatal: Unknown authentication mechanism 'NTLM'
by David Koski 31 Jan '22

31 Jan '22

After upgrading Debian to 11 I found Dovecot at version 2.3.13 (89f716dc2). Now auth method NTLM fails and is not even listed: # doveadm pw -l SHA1 SSHA512 SCRAM-SHA-256 BLF-CRYPT PLAIN HMAC-MD5 OTP SHA512 SHA DES-CRYPT CRYPT SSHA MD5-CRYPT PLAIN-MD4 PLAIN-MD5 SCRAM-SHA-1 SHA512-CRYPT CLEAR CLEARTEXT ARGON2I ARGON2ID SSHA256 MD5 PBKDF2 SHA256 CRAM-MD5 PLAIN-TRUNC SHA256-CRYPT SMD5 DIGEST-MD5 LDAP-MD5 /var/log/dovecot.log Jan 22 16:20:32 auth: Fatal: Unknown authentication mechanism 'NTLM' Jan 22 16:20:32 master: Error: service(auth): command startup failed, throttling for 2.000 secs Jan 22 16:20:34 auth: Fatal: Unknown authentication mechanism 'NTLM' Jan 22 16:20:34 master: Error: service(auth): command startup failed, throttling for 4.000 secs Jan 22 16:20:38 auth: Fatal: Unknown authentication mechanism 'NTLM' Jan 22 16:20:38 master: Error: service(auth): command startup failed, throttling for 8.000 secs Jan 22 16:20:46 auth: Fatal: Unknown authentication mechanism 'NTLM' Jan 22 16:20:46 master: Error: service(auth): command startup failed, throttling for 16.000 secs # doveconf -n # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 5.10.0-11-amd64 x86_64 Debian 11.2 # Hostname: imail.khmfdbyekekelj1rmytwnfh1bc.dx.internal.cloudapp.net auth_mechanisms = plain login ntlm debug_log_path = /var/log/dovecot-debug.log info_log_path = /var/log/dovecot-info.log log_path = /var/log/dovecot.log maildir_stat_dirs = yes 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 compat { alias_for = hidden = yes inbox = no list = no location = prefix = INBOX. separator = . } 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 = separator = . } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { mail_plugins = " quota trash sieve" sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap sieve" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-client { mode = 0660 } } 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/letsencrypt/live/imail1.sutinen.com/fullchain.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-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = " quota trash sieve" postmaster_address = admin-kosmosisland.com(a)kosmosisland.com } protocol lda { mail_plugins = " quota trash sieve" } Regards, David Koski

3 4

LMTP error on trying to find passwd-file for Postfix recipient validation
by Narcis Garcia 28 Jan '22

28 Jan '22

Hello everyone, I have following configurations (and more) at /etc/dovecot/local.conf in a "/VirtualUserFlatFilesPostfix/" setup : [partial file content begins] protocols = imap pop3 lmtp sieve mail_location = maildir:~/data:INBOX=~/data/.INBOX service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { user = vmail group = vmail mode = 0660 } } protocol lmtp { postmaster_address = postmaster(a)example.net mail_plugins = $mail_plugins sieve } userdb { driver = passwd-file args = username_format=%u /srv/vmail/domains.d/%d/users.d/%n/etc/passwd } passdb { driver = passwd-file args = username_format=%u /srv/vmail/domains.d/%d/users.d/%n/etc/shadow.%Ls } service auth { unix_listener /var/spool/postfix/private/auth { user = postfix group = postfix mode = 0660 } } [/partial file content ends] Everyting works (IMAP mail is stored, IMAP/POP3 mail is retrieved, incoming SMTP mail from Postfix is delivered, Outgoing SMTP senders are authenticated from Postfix~SASL) BUT: When incoming mail goes to a mailbox that does not exist, an error is logged by Dovecot, letter remains at Postfix queue, and no rejection message to sender (here host is /mail.example.net/): [partial]$ cat /var/log/mail.log 2022-01-28T08:52:00.851751+01:00 correo postfix/smtpd[1853]: CFDA63A174B: client=mail.example.com[1.2.3.4] 2022-01-28T08:52:00.872248+01:00 correo postfix/cleanup[1881]: CFDA63A174B: message-id=<83c79ee1-6e2e-4e15-307e-17cdc7e2b814(a)example.com> 2022-01-28T08:52:00.884100+01:00 correo postfix/qmgr[1529]: CFDA63A174B: from=<johndoe(a)example.com>, size=854, nrcpt=1 (queue active) 2022-01-28T08:52:00.884507+01:00 correo postfix/smtpd[1853]: disconnect from mail.example.com[1.2.3.4] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 2022-01-28T08:52:00.969275+01:00 correo postfix/lmtp[1882]: CFDA63A174B: to=<wronguser(a)example.net>, relay=mail.example.net[private/dovecot-lmtp], delay=0.43, delays=0.35/0.02/0.02/0.05, dsn=4.3.0, status=deferred (host mail.example.net[private/dovecot-lmtp] said: 451 4.3.0 <wronguser(a)example.net> Temporary internal error (in reply to RCPT TO command)) [partial]$ cat /var/log/dovecot.log 2022-01-28 08:52:00 lmtp(1883): Info: Connect from local 2022-01-28 08:52:00 auth: Error: passwd-file(wronguser(a)example.net): stat(/srv/vmail/domains.d/example.net/users.d/wronguser/etc/passwd) failed: Address family not supported by protocol 2022-01-28 08:52:00 lmtp(wronguser(a)example.net)<1883><xbrsNqCg82FbBwAAzZSvjA>: Error: user wronguser(a)example.net: Auth USER lookup failed 2022-01-28 08:52:00 lmtp(1883): Error: Failed to lookup user wronguser(a)example.net: Internal error occurred. Refer to server log for more information. 2022-01-28 08:52:00 lmtp(1883): Info: Disconnect from local: Client has quit the connection (state=READY) Thank you for any help in debugging configuration or suggestion to enhance Postfix/Dovecot parameters. Postfix 3.4 Dovecot 2.3 -- Narcis Garcia __________ I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors.

2 2

Non-unique Message ID in mail messages
by Daniel Ryšlink 28 Jan '22

28 Jan '22

Hello! I apologize for bringing perhaps trivial/well-known matter, but I am interested in your opinion. RFC 5322 clearly states that mail messages SHOULD contain a Message ID identifier, but if the do contain it, it MUST be globally unique. Despite this requirement, I have encountered senders (namely Spamcop) that sends obviously different (albeit related) messages called "Alert" and "Summary" (they are always related to the same incident and have the same Message ID). This creates all sorts of problems when processing these mails, namely with users that have local forwards from one domain to another (our mailserver hosts multiple domains), because for example Dovecot refuses to forward the second message, flagging it as a duplicate. My question to you is - did you also encounter similar incorrect (according to RFC standards) problem, and if so, is there a way to persuade dovecot to perhaps determine the uniqueness of a message by other means than just checking the message ID (i.e. look at other identifiers, Subject, perhaps)? Because according to the log records, Spamcop does not seem to be the only offender. Thanks in advance for any reactions, and if I did something wrong by writing this message, I apologize again in advance. If required, I can provide samples of the Spamcop messages. -- --===============-- --== Best Regards! ==-- --===============-- Daniel Ryšlink Sysadmin @ Quantcom.cz Czech Republic

4 3

Re: dovecot Digest, Vol 225, Issue 71
by David Matthews 28 Jan '22

28 Jan '22

hi Christian >Did the password hash algorithm change between devuan 3 and 4? >You can check that in your /etc/shadow file. As I understand, devuan is pretty much debian without systemd? And that if you were prepared to do a fair bit of work you could start with debian installed, hack it about and end up with something like devuan? I doubt devuan has done anything to deviate from debian at this level and both machines were recently dist-upgraded. Dovecot needed no tinkering with at all on the debian machine. >The start of the password field should be the same something like $6$... > Yes it is on devuan 4. I no longer have anything with devuan 3 to check that, but it shouldn't have changed in a dist-upgrade? Interestingly, although it's the same user and password on both machines, I notice that the hashes in /etc/shadow are not identical after the commencing $6$. But then I don't know how these hashes are derived, so maybe that is not unexpected? -- David Matthews mail(a)dmatthews.org

2 1

Errors: Failed to map transaction log, Corrupted transaction log, imeout (180s) while waiting for lock for transaction log
by absolutely_free＠libero.it 28 Jan '22

28 Jan '22

Hi, no, it is a single mail server, no replication at all. Thank you > Hello > > We only saw such errors with replication between two machines, when new > emails where errornously deliverd to both of them or clients connected > to both simultaniously. > > Do you have such a setup? > Kind regards, > Christian Mack

1 0

doveadm backup : Warning: Deleting mailbox GUID= is missing locally
by Laura Smith 28 Jan '22

28 Jan '22

Hi, As per the docs (https://wiki.dovecot.org/Tools/Doveadm/Sync) I'm presently running doveadm backup multiple times with a view to eventual server migration. I am seeing messages such as this: Warning: Deleting mailbox 'Junk': UID=1826 GUID= is missing locally Is it anything to worry about ? If so, how should I be dealing with it. I also have a further question. It is not clear from the docs what the role of the "-R" flag is in relation to "doveadm backup" ? Surely by definition backup = remote -> local ? Thanks ! Laura

2 3

Question regarding delivery from Postfix via LMTP proxy
by Vlad Sedov 28 Jan '22

28 Jan '22

Hello, I'm using Postfix with Dovecot 2.3.13, and trying to get LMTP proxy to work for authentication and delivery in the following scenario: Incoming Mail -> Postfix (server A) -> LMTP to Dovecot (server A) -> LMTP to Dovecot (server B) I'm using MySQL for authentication. I've created a user on both server A and server B, test(a)domain.tld On server A, host parameter in password_query for test(a)domain.tld is set to server B's address, and proxy_maybe is enabled. Delivery and authentication to Server A works fine. Authentication and IMAP proxy to server B works fine as well. I can connect to IMAP on server A with credentials for test(a)domain.tld and access the maildir on server B. This works surprisingly well, and is about half the battle for me.. What I can't figure out, is how can I get Postfix to deliver mail using LMTP via server A to server B.. Currently, mail still gets delivered to the user's maildir on server A. Is this possible with Dovecot alone, or do I need to use another method to get messages to hop to server B via server A? Any help would be appreciated.. cheers, Vlad

1 0

Re: dovecot Digest, Vol 225, Issue 70
by David Matthews 27 Jan '22

27 Jan '22

hi Christian Same user and password on both machines, users with shell accounts; exactly the same; in fact I'm struggling to see anything different that might be relevant. On one machine dovecot just works on the other, it stopped working after a dist-upgrade. One machine (where it works) is a debian 11 VPS, the other is real PC hardware running devuan 4, but their dovecot is a debian package. I can't see why either of that should matter and dovecot also just worked on the PC with devuan 3. I've tried purging dovecot-core and dovecot-imapd and reinstalling to no effect. > > 1. Re: can't authenticate (Christian Mack) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Thu, 27 Jan 2022 11:42:22 +0100 >From: Christian Mack >christian.mack(a)uni-konstanz.de> >To: dovecot(a)dovecot.org >Subject: Re: can't authenticate >Message-ID: >a2fbca25-75c7-4e19-a084-5e8d4d8cc645(a)uni-konstanz.de> >Content-Type: text/plain; charset="utf-8" > >Hello > >> passdb { >> driver = pam >> } > >Is user fred defined on your development machine? >Does the password match the one from the production machine? > > >Kind regards, >Christian Mack > >On 26.01.22 21:14, David Matthews wrote: >> My live mail exchanger and development machines have identical dovecot setups, yet I cannot login on the development machine:- >> >> dovecot --version >> 2.3.13 (89f716dc2) >> >>> telnet localhost 143 >> Trying 127.0.0.1... >> Connected to bulawayo. >> Escape character is '^]'. >> * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ STARTTLS AUTH=PLAIN] Dovecot (Debian) ready. >> a login fred xxxxxxxxxxx >> a NO [UNAVAILABLE] Temporary authentication failure. [bulawayo:2022-01-26 20:02:14] >> >> same if I try openssl s_client to 993 >> >>> tail /var/log/mail.log >> Jan 26 20:03:28 bulawayo dovecot: imap-login: Disconnected (auth service reported temporary failure): user=>fred>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, session=>1MRorYHWwOp/AAAB> >> >> doveconf -n >> # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf >> # Pigeonhole version 0.5.13 (cdd19fe3) >> # OS: Linux 5.10.0-10-amd64 x86_64 Debian 11.1 >> # Hostname: bulawayo >> mail_location = mbox:~/mail:INBOX=/var/mail/%u >> mail_privileged_group = mail >> namespace inbox { >> inbox = yes >> location = >> mailbox Drafts { >> special_use = \Drafts >> } >> mailbox Junk { >> special_use = \Junk >> } >> mailbox Sent { >> special_use = \Sent >> } >> mailbox "Sent Messages" { >> special_use = \Sent >> } >> mailbox Trash { >> special_use = \Trash >> } >> prefix = >> } >> passdb { >> driver = pam >> } >> protocols = " imap" >> service imap-login { >> inet_listener imap { >> port = 143 >> } >> inet_listener imaps { >> port = 993 >> ssl = yes >> } >> } >> 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 { >> driver = passwd >> } >> >> -- >> David Matthews >> mail(a)dmatthews.org >> > > >-- >Christian Mack >Universit?t Konstanz >Kommunikations-, Informations-, Medienzentrum (KIM) >Abteilung IT-Dienste Forschung und Lehre >78457 Konstanz >+49 7531 88-4416 > >

2 1

can't authenticate
by David Matthews 27 Jan '22

27 Jan '22

My live mail exchanger and development machines have identical dovecot setups, yet I cannot login on the development machine:- dovecot --version 2.3.13 (89f716dc2) >telnet localhost 143 Trying 127.0.0.1... Connected to bulawayo. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ STARTTLS AUTH=PLAIN] Dovecot (Debian) ready. a login fred xxxxxxxxxxx a NO [UNAVAILABLE] Temporary authentication failure. [bulawayo:2022-01-26 20:02:14] same if I try openssl s_client to 993 >tail /var/log/mail.log Jan 26 20:03:28 bulawayo dovecot: imap-login: Disconnected (auth service reported temporary failure): user=<fred>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, session=<1MRorYHWwOp/AAAB> doveconf -n # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 5.10.0-10-amd64 x86_64 Debian 11.1 # Hostname: bulawayo mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_privileged_group = mail namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } protocols = " imap" service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } 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 { driver = passwd } -- David Matthews mail(a)dmatthews.org

2 1

Errors: Failed to map transaction log, Corrupted transaction log, imeout (180s) while waiting for lock for transaction log
by absolutely_free＠libero.it 27 Jan '22

27 Jan '22

Hi all, I am using dovecot-2.3.17_1 on FreeBSD system. This server offers webmail, pop3 and imap access for users. Today I am receiving several complaints from users about slowness and/or access issues. I checked on my /var/log/maillog and I see lots of: Error: Timeout (180s) while waiting for lock for transaction log file /var/domains/domain.it/username/Maildir/dovecot.list.index.log (WRITE lock held by pid 84939) Error: Corrupted transaction log file /var/domains/domain.it/otherusername/Maildir/dovecot.list.index.log seq 2: indexid changed: 1643184505 -> 1643205059 (sync_offset=0) Error: Transaction log file /var/domains/otherdomain.net/otheruser/Maildir/dovecot.list.index.log: marked corrupted Not all users seem affected. My mailbox, for example, is working fine. I checked on my disks (this is a ZFS volume) and I didn't find errors/warnings. Any suggestion? This is my dovecot configuration: # dovecot -n # 2.3.17 (e2aa53df5b): /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 13.0-RELEASE-p6 amd64 zfs # Hostname: mailserver.domain.it auth_debug = yes auth_mechanisms = plain login auth_verbose = yes default_client_limit = 2000 default_process_limit = 500 default_vsz_limit = 512 M disable_plaintext_auth = no first_valid_gid = 125 first_valid_uid = 125 imap_id_log = * mail_gid = 1003 mail_location = maildir:/mail/domains mail_privileged_group = postfix mail_uid = 1003 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 = /usr/local/etc/dovecot/dovecot-sql-crypt.conf.ext driver = sql } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = postfix mode = 0600 user = postfix } } service imap { process_limit = 1536 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl_cert = </etc/ssl/wildcard.domain.net_bundle.crt ssl_key = # hidden, use -P to show it userdb { args = /usr/local/etc/dovecot/dovecot-sql-crypt.conf.ext driver = sql } protocol imap { mail_max_userip_connections = 100 } Thank you very much

2 1

sieve-filter ignores -u argument
by Андрей Куницын 27 Jan '22

27 Jan '22

Hello I try to test my sieve script, but found out that it is impossible to use a sieve-filter tool with virtual mail users. It always uses a real user name instead of passed via -u argument. # sieve-filter -v -u postmaster(a)domain.tld ~/sieve/managesieve.sieve INBOX sieve-filter(root): Fatal: Unknown user sudo -u vmail sieve-filter -u postmaster(a)domain.tld ~/sieve/managesieve.sieve INBOX sieve-filter(vmail): Fatal: Unknown user Also there is the same question on serverfault, but without an answer. https://serverfault.com/questions/1055407/how-to-make-sieve-filter-use-virt… My environment is Ubuntu 20.04 dovecot --version 2.3.7.2 (3c910f64b) -- Sincerely, Andrey Kunitsyn

4 5

Dovecot installation problem (libssl_iostream_openssl.so is not portable!)
by Dimitri 27 Jan '22

27 Jan '22

Hi there, i try to install dovecot from source with the following configuration: > ./configure --prefix=/test/core/dovecot --with-ssldir=/test/core/dovecot/tls the configuration runs fine with the following output at the end: > Install prefix . : /test/core/dovecot > File offsets ... : 64bit > I/O polling .... : epoll > I/O notifys .... : inotify > SSL ............ : yes (OpenSSL) > GSSAPI ......... : no > passdbs ........ : static passwd passwd-file shadow checkpassword > : -pam -bsdauth -ldap -sql > userdbs ........ : static prefetch passwd passwd-file checkpassword > : -ldap -sql > CFLAGS ......... : -std=gnu99 -g -O2 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -mfunction-return=keep -mindirect-branch=keep -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/test/dep/openssl/include > SYSTEMD ........ : notify - /lib/systemd/system/dovecot.service > SQL drivers .... : > : -pgsql -mysql -sqlite -cassandra > Full text search : squat > : -lucene -solr But when i start to build (make) after a while i get the following error: > *** Warning: Linking the executable test-iostream-ssl against the loadable module > *** libssl_iostream_openssl.so is not portable! > libtool: link: gcc -std=gnu99 -g -O2 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -mfunction-return=keep -mindirect-branch=keep -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/test/dep/openssl/include -o .libs/test-iostream-ssl test-iostream-ssl.o ./.libs/libssl_iostream_openssl.so ./.libs/libssl_iostream.a ../lib-test/.libs/libtest.a ../lib/.libs/liblib.a -L/test/dep/openssl/lib64 -lssl -lcrypto -ldl -Wl,-rpath -Wl,/test/core/dovecot/lib/dovecot > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `ERR_free_strings' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `ENGINE_cleanup' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_library_init' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `OBJ_cleanup' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `CRYPTO_cleanup_all_ex_data' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `OpenSSL_add_all_algorithms' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_CTX_set_tmp_rsa_callback' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `EVP_cleanup' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_load_error_strings' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_CTX_need_tmp_RSA' > collect2: error: ld returned 1 exit status > make[3]: *** [Makefile:655: test-iostream-ssl] Error 1 > make[3]: Leaving directory '/test/tmp/dovecot-2.3.17.1/src/lib-ssl-iostream' > make[2]: *** [Makefile:573: all-recursive] Error 1 > make[2]: Leaving directory '/test/tmp/dovecot-2.3.17.1/src' > make[1]: *** [Makefile:702: all-recursive] Error 1 > make[1]: Leaving directory '/test/tmp/dovecot-2.3.17.1' > make: *** [Makefile:546: all] Error 2 I've searched for the error and find some posts about set explicitly CPPFLAGS and LDFLAGS and something about missing shared libraries of openssl. My openssl have shared libraries (libcrypto.so libssl.so ...) and the explicit use of CPPFLAGS and LDFLAGS to my openssl hasn't changed anything I use Openssl 3.0 but i've tested also 1.1.1m and 1.1.1g for example, same error! Dovecot is the latest 2.3.17.1 Can anyone help me with this please? Thanks!

1 0

doveadm stateful backup
by Christian 26 Jan '22

26 Jan '22

Hi all, first: I'm using version 2.3.4.1 I manage some rather large imap mailboxes which I want to backup on a regular basis. Some of them have relatively heavy traffic and one of them is greater than 30GB in size. I studied the docs for doveadm backup (https://wiki2.dovecot.org/Tools/Doveadm/Sync) and even did some code research to better understand the process. The docs state that using stateful synchronization is the most efficient way to synchronize mailboxes, therefore I chose this approach. Highlevel overview: - store a copy of the whole maildir in a separate directory (/var/vmail/backup) - backup to this directory once a minute (trying to make most use of transaction logs) using the last state stored within a file - create a backup once a day using tar (full, differential and incremental ones) blocking the backup process of the before mentioned step I quite often receive notifications that doveadm backup returned an exit code of 2, which should be quite normal. These notifications look like that: dsync(another_address(a)my.domain): Warning: Failed to do incremental sync for mailbox INBOX, retry with a full sync (Modseq 171631 no longer in transaction log (highest=177818, last_common_uid=177308, nextuid=177309)) dsync(another_address(a)my.domain): Warning: Mailbox changes caused a desync. You may want to run dsync again: Remote lost mailbox GUID e9149d0ae4e02d532505000026ca4352 (maybe it was just deleted?) Synced another_address(a)my.domain successfully but missing some changes. Took 3 seconds. Starting retry 1... The first message seems to point out that the transaction log got rolled and no more contains the messages from the backup dir, right? I thought about setting mail_index_log_rotate_min_age to 1hour to prevent rolling transaction logs too often, but abandoned this thought and increased the backup interval to once a minute. The warnings still appear so maybe my thoughts about transactions logs are wrong. The second message seems less alarming to me. How does doeveadm backup behave in such situations? Does it directly fall back to a less efficient way of syncing mails? Does the state store the information "retry with a full sync" and the next run uses this mode? To investigate on this I simply measured runtimes an saw that the second/retry run takes a bit longer (up to about 15 seconds) to sync the dir. I'm afraid of losing messages using my approach. Is it safe to always use doveadm backup -s $state? Simply counting one maildirs files within the live directory and the backup copy shows a 100 fewer files within the backup dir although the script runs only since a few days. For reference, see my backup script below. Regards Christian #!/bin/bash # * * * * * /root/bin/backup.sh --sync-only # 12 2 1-7 * * test $(date +\%u) -eq 6 && /root/bin/backup.sh --full # 12 2 8-31 * * test $(date +\%u) -eq 6 && /root/bin/backup.sh --differential # 12 2 * * * test $(date +\%u) -ne 6 && /root/bin/backup.sh synconly=0 differential=0 fullbackup=0 if [ $# -gt 0 ] ; then if [ "$1" == "--sync-only" ] ; then synconly=1 elif [ "$1" == "--differential" ] ; then differential=1 elif [ "$1" == "--full" ] ; then fullbackup=1 fi fi basedir="/var/vmail/backup" targetdir="/var/vmail/backup/done" mailaddresses="one_address(a)my.domain another_address(a)my.domain yet_another(a)my.domain" if [ ! -d "$basedir" ] ; then mkdir -p "$basedir" chown vmail:vmail "$basedir" fi if [ ! -d "$targetdir" ] ; then mkdir -p "$targetdir" chown vmail:vmail "$targetdir" fi for mailaddr in ${mailaddresses} ; do #echo "Creating backup for $mailaddr." domainpart=${mailaddr#*@} localpart=${mailaddr%%@*} lockfile="$basedir/$mailaddr.lock" statefile="$basedir/$mailaddr.state" backupdir="$domainpart/$localpart/Maildir" snapshotfile_full="$basedir/$mailaddr.full.snar" snapshotfile="$basedir/$mailaddr.snar" backup_basename="$basedir/${mailaddr}_$(date '+%Y%m%d_%H%M%S')" ( if [ $synconly -eq 1 ] ; then flock -xn 200 if [ $? -eq 1 ] ; then # failed to acquire lock. Skip mailbox silently. exit fi fi # try to acquire exclusive lock for one minute flock -xw 60 200 if [ $? -eq 1 ] ; then echo "Failed to acquire write lock within 60 seconds. Skipping $mailaddr." exit fi retries=0 retval=1 until [ $retval -eq 0 ] || [ $retries -ge 3 ] ; do let 'retries++' if [ -f "$statefile" ] ; then oldstate=$(head -1 "$statefile") else oldstate="" fi start_time=$(date +%s) ERROR=$((doveadm backup -u "$mailaddr" -s "$oldstate" "maildir:$basedir/$backupdir") 2>&1 > "$statefile") retval=$? end_time=$(date +%s) let 'duration=end_time-start_time' if [ $retval -eq 2 ] ; then #if [ $retries -gt 1 ] ; then echo "$ERROR" echo "Synced $mailaddr successfully but missing some changes. Took $duration seconds. Starting retry $retries..." #fi elif [ $retval -ne 0 ] ; then echo "$ERROR" echo "Syncing $mailaddr failed. Return code $retval. Took $duration seconds. Removing backup directory and starting retry $retries..." rm -rf "$basedir/$backupdir" rm -f "$statefile" "$snapshotfile" elif [ $retries -gt 1 ] ; then echo "Successful sync took $duration seconds." fi done # downgrade lock to shared lock flock -sn 200 [ $synconly -eq 1 ] && exit if [ $retval -ne 0 ] ; then echo "Too many retries. Aborting backup of $mailaddr." exit fi cd "$basedir" if [ $fullbackup -eq 1 ] || [ ! -f "$snapshotfile_full" ] ; then tar -cpzf "${backup_basename}_full.tar.gz" --level=0 -g "$snapshotfile_full" "$backupdir" cp -f "$snapshotfile_full" "$snapshotfile" else suffix="" if [ $differential -eq 1 ] ; then cp -f "$snapshotfile_full" "$snapshotfile" suffix="_diff" fi tar -cpzf "${backup_basename}${suffix}.tar.gz" -g "$snapshotfile" "$backupdir" fi cd - > /dev/null mv "${basedir}/"*.tar.gz "$targetdir" ) 200>"$lockfile" [ $synconly -eq 1 ] && continue # housekeeping newest_full=$(ls -1 "${targetdir}/${mailaddr}_"*_full.tar.gz 2>/dev/null | sort | tail -1) if [ -n "$newest_full" ] ; then #echo "Cleaning up files older than $newest_full..." find "$targetdir" -depth -maxdepth 1 -name "${mailaddr}_*" ! -newer "$newest_full" ! -samefile "$newest_full" -printf 'Deleting %p...\n' -delete fi done

1 1

pop3-login logging double Disconencted
by Noel Butler 26 Jan '22

26 Jan '22

Hi all, Wondering if anyone else is seeing this double Disconnected in the logs with current stable version, it only happens for pop3-login, and only with Too many commands... other pop3-login logging with Disconnected like Connection closed (no auth attempts... etc are fine Example of anomaly - pop3-login: Info: Disconnected: Disconnected: Too many bad commands (no auth attempts in ... If anyone running 2.3.17.1 sees this or does not see it on Too many bad... or at all, kindly mind letting me know, not sure if something has gone haywire here or its a bug that needs reporting since logs indicate this only occurred after updating to the point 1 release. -- Regards, Noel Butler This Email, including attachments, may contain legally privileged information, therefore at all times remains confidential and subject to copyright protected under international law. You may not disseminate this message without the authors express written authority to do so. If you are not the intended recipient, please notify the sender then delete all copies of this message including attachments immediately. Confidentiality, copyright, and legal privilege are not waived or lost by reason of the mistaken delivery of this message.

2 1

noob maildir question
by mikfum 25 Jan '22

25 Jan '22

I would like to ask if it is an acceptable practice to manage messages in the maildir as a file (move them from one folder to another) while dovecot is in stop state thinking that it will be rebuild to the next imap user login thanks for your patience:) mik

5 10

Re: noob maildir question
by mikfum 24 Jan '22

24 Jan '22

thanks ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ Il lunedì 24 gennaio 2022 5:15 AM, Ted Hatfield <ted(a)io-tx.com> ha scritto: > I do this all the time on my server. From one user mailbox to another or > > from one maildir folder to another. On my platform I need to make certain > > owner/group of the moved messages is correct for the user I've moved them > > to. Other than that dovecot appears to re-index on the fly. > > Be aware that this is observed information. Others more knowledgeable may > > have concerns that I'm not aware of or just can't see on my system. > > Ted > > On Mon, 24 Jan 2022, mikfum wrote: > > > I would like to ask if it is an acceptable practice to manage messages in the maildir as a file (move them from > > > > one folder to another) while dovecot is in stop state thinking that it will be rebuild to the next imap user login > > > > thanks for your patience:) > > > > mik

1 0

zlib.read errors after upgrade from 2.3.15 to 2.3.17.1
by Arno Schneider 24 Jan '22

24 Jan '22

After upgrading my mailserver from buster to bullseye and dovecot 2.3.15 to 2.3.17.1 I got the following errors: Jan 22 14:22:32 Warning: doveadm(user1)<2953060><49b0NRQF7GFkDy0ALVPUUA>: mdbox /local/mail/user1/storage: rebuilding indexes Jan 22 14:22:39 Error: doveadm(user2)<2953112><awsPGB8F7GGYDy0ALVPUUA>: dsync(2nd.dovecot.server): read(compress(/local/mail/user2/storage/m.4650)) failed: read(/local/mail/user2/storage/m.4650) failed: zlib.read(/local/mail/user2/storage/m.4650): unexpected EOF at 7038367 (last sent=mail, last recv=mail_request (EOL)) I have 2 dovecot servers in a multi-master configuration. The both servers are synced with dsync and the users are routed through a dovecot directors. Any hints where I can continue to investigate / solve this issue? best regards, arno

1 0

Why would dovecot not be answering
by Ruben Safir 23 Jan '22

23 Jan '22

I am really lost as to why dovecot is not authenticating I have smtpd_sasl_type = dovecot in main.cf and # Postfix smtp-auth unix_listener /var/spool/postfix/private/auth { mode = 0666 user = postfix group = postfix } in /etc/dovecot/conf.d/10-master.conf I want it to authenticate on submition only Everything I read says this should do it, but I am up against a wall. I have no debugging information or log at all to confirm what postfix is doing. -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and extermination camps, but incompatible with living as a free human being. -RI Safir 2013

3 5

S3 integration w Dovecot
by Martin Olsen 21 Jan '22

21 Jan '22

Good morning, day, evening :P As stated on documentation S3-compatible Storages — Dovecot documentation <https://doc.dovecot.org/configuration_manual/mail_location/obox/s3/> only AWS S3 is officially supported. However, we know that Scality has been successfully integrated at some larger corporations. Particularly curious if anyone has integrated with Pure S3 object storage solution, or any other for that matter? Just looking at some different options. - Sincerely, Martin.

4 3

Stop used or not
by mauric＠gmx.ch 21 Jan '22

21 Jan '22

Sieve scripts running fine, but please what would mean the "Stop", if I have multiple Policy that will run true, I need one stop to finish this per section? if header :is ["from","bcc","to"] ["Email-Address-one", "Email-Address-Two", "and so on"] { fileinto ".\Magic-FolderName"; stop; } thanks

3 4

Upgrade only piegenhole to 0.5.17?
by mauric＠gmx.ch 20 Jan '22

20 Jan '22

Please it's possible to update only piegenhole to 0.5.17, on existing Dovecot installation? Downloading dovecot-2.3-pigeonhole-0.5.17.1 Here I found the update-version, its this the possible way? And why I don't found any Informations on any readme, please point me to the right place. installed version, I think this it's the right view? Please on witch place I can check the Sieve installed module? doveconf | head # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5 () Also found in file pieg-config /* Define to the version of Pigeonhole for Dovecot. */ #define PIGEONHOLE_VERSION "0.5.4" On Debian 10 I have this installed. dovecot-managesieved 1:2.3.4.1-5+deb10u6 amd64 secure POP3/IMAP server - ManageSie dovecot-sieve 1:2.3.4.1-5+deb10u6 amd64 secure POP3/IMAP server - Sieve filters support also checking the folder /usr/include/dovecot/sieve with intention so found any possible version? Thanks for any update

2 2

sockets created for lmtp
by Mike 20 Jan '22

20 Jan '22

Was recently configuring lmtp to listen in the postfix spool for mail. I set the socket as suggested in the documentation, however, when I look at what sockets were created there was an additional one for dovecot. Since I made the change, my expectation would have been just the one that I set up. I doubt it impacts it negatively, but I wanted to understand if I configured things correctly or not. Thanks. Mike

4 6

FTS Tokenization filters normalizer-icu vs lowercase
by Alessio Cecchi 20 Jan '22

20 Jan '22

Hi, I'm trying to setup fts-flatcurve with tokenization. What are the differences/benefits with "fts_filters = normalizer-icu" vs "fts_filters = lowercase"? Reading the Doc I found about normalizer-icu "This is potentially very resource intensive." and about lowercase "Supports UTF8, when compiled with libicu". So, using lowercase is almost the same that normalizer-icu but faster? FYI for using fts-flatcurve with dovecot RPM packages from repo.dovecot.org you have to rebuild with --with-icu --with-stemmer --with-textcat and related library. Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice

2 1

Save of messages slow when replica unavailable
by Jörg Faudin Schulz 20 Jan '22

20 Jan '22

We have a setup with a dovecot server + replica. This works fine as long as the replica is available. When the replica is not available for some reason, the clients can work normally with one exception: the saving of sent messages to their inboxes takes ages. Thunderbird times out and complains (and duplicates the message), mail.app just waits until it's done. Is there any setting that helps here? For the time being, I deactivated replication; but this isn't a long time solution. Thank you for all your work&support, appreciating the doc as well.

1 0

dovecot-2.3.17: "Panic: file ioloop.c: line 865"
by Christian Küppers 20 Jan '22

20 Jan '22

Hello, we got the same backtrace in dovecot-ee version 2:2.3.17-8+ubuntu20.04 as Andreas Piper mentioned in November 2021 https://dovecot.org/pipermail/dovecot/2021-November/123468.html after installing dovecot package updates. Panic: file ioloop.c: line 865 (io_loop_destroy): assertion failed: (ioloop == current_ioloop) Error: Raw backtrace: #0 t_askpass[0x7fc609b0eba0] -> #1 backtrace_append[0x7fc609b0ee00] -> #2 backtrace_get[0x7fc609b0ef70] -> #3 i_syslog_error_handler[0x7fc609b1bfa0] -> #4 i_syslog_fatal_handler[0x7fc609b1c0d0] -> #5 i_panic[0x7fc609a6f1af] -> #6 i_error[0x7fc609a72906] -> #7 doveadm_http_server_deinit[0x55abd194af90] -> #8 doveadm_print_stream[0x55abd19447b0] -> #9 doveadm_print_istream[0x55abd1944810] -> #10 expunge_search_args_check[0x55abd1936a00] -> #11 expunge_search_args_check[0x55abd1935860] -> #12 doveadm_dsync_main[0x55abd1932900] -> #13 doveadm_cmd_ver2_to_mail_cmd_wrapper[0x55abd1933890] -> #14 doveadm_cmd_run_ver2[0x55abd1943fb0] -> #15 doveadm_server_deinit[0x55abd1948760] -> #16 io_loop_call_io[0x7fc609b32440] -> #17 io_loop_handler_run_internal[0x7fc609b33a00] -> #18 io_loop_handler_run[0x7fc609b32500] -> #19 io_loop_run[0x7fc609b32680] -> #20 master_service_run[0x7fc609aa4780] -> #21 main[0x55abd1923820] -> #22 __libc_start_main[0x7fc60970efc0] -> #23 _start[0x55abd1923980] Error: doveadm server disconnected before handshake: EOF Command fetch failed for <mailbox>: EOF We got it during doveadm fetch of a mail on multiple mailboxes. Is there any progress on this? Will it be fixed in next release? Kind regards, Christian Küppers Expert Administrator onOffice GmbH Charlottenburger Allee 5 | 52068 Aachen Tel. +49 (0)241 446 86-0 | Fax. +49 (0)241 446 86-250 E-Mail:c.kueppers@onoffice.de| Web:www.onOffice.com Registergericht: Amtsgericht Aachen, HRB 21420 Geschäftsführer: Dipl.-Kfm. Stefan Mantl Prokuristen: Janosch Reuschenbach, Kristina Andresen, Christian Mähringer

2 1

lmtp_save_to_detail_mailbox
by dovecot＠ptld.com 19 Jan '22

19 Jan '22

lmtp_save_to_detail_mailbox: " If the recipient address includes a detail element / role (as in user+detail format), save the message to the detail mailbox. " Im not understanding this, what is the "detail mailbox"? I tried testing this feature by setting "lmtp_save_to_detail_mailbox = yes" and sending an email to user+test(a)example.com. The email still ended up in the default inbox folder. So what does lmtp_save_to_detail_mailbox do or is there another setting that also needs to be set to use this feature?

3 5

Outlook vs. Dovecot experience
by Vladislav Kurz 18 Jan '22

18 Jan '22

Dear colleagues, what is your experience regarding using outlook (2016/365) as IMAP client and dovecot on server side? We have sync issues with outlook vs. cyrus IMAP server, and we consider moving to dovecot. But before that I'd like to hear from others if this combination works well. Especially if users have large and bushy mailboxes (>10 GB, >100 mailboxes), two mailboxes (accounts) on the same server. I don't want to do the migration just to find out that it is general issue of outlook vs. any IMAP server. -- Best regards Vladislav Kurz

7 10

JA3/JA3S as a Dovecot plugin?
by Sidsel Jensen 18 Jan '22

18 Jan '22

Hi We have been looking a bit into JA3 (https://engineering.salesforce.com/tls-fingerprinting-with-ja3-and-ja3s-247… <https://engineering.salesforce.com/tls-fingerprinting-with-ja3-and-ja3s-247…> and https://blog.squarelemon.com/tls-fingerprinting/ <https://blog.squarelemon.com/tls-fingerprinting/> ) for possible threat actor identifications. Roughly speaking you can think of JA3 as the TLS equivalent of the User-Agent string. Has anybody been looking into the possibility of building an open source dovecot JA3 plugin? I’d also like to hear the technical pros/cons of doing so…and perhaps the ethical deliberations also :-) Kind Regards, Sidsel

1 0

FTS flatcurve not index messages when SEARCH run on Virtual Mailboxes
by Alessio Cecchi 18 Jan '22

18 Jan '22

Hi, I'm testing FTS flatcurve plugin in order to understand if I can switch from FTS Solr to flatcurve. In my configuration I have enabled Virtual mailboxes and for search in all folders I just SEARCH on Virtual/All folder. I this (virtual) folder is not indexed with FTS Solr Dovecot start to index it (or all real folders). But with FTS flatcurve when I SEARCH on Virtual/All for the first time the indexer process does not start and the search return empty. Only if I run manually "doveadm index -q -u alessio(a)email.net '*'" flatcurve find messages. Can flatcurve have the same feature as Solr for Virtual mailboxes? Here a sample of my configuration: namespace Virtual { hidden = yes list = no location = virtual:/etc/dovecot/virtual:INDEX=~/Maildir/virtual prefix = Virtual/ separator = / subscriptions = no } namespace inbox { [...] mailbox virtual/All { comment = All my messages special_use = \All } } # cat /etc/dovecot/virtual/All/dovecot-virtual * all Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice

3 6

Extracting CLIENTID information from checkpassword or postlogin scripting
by Dan Conway 18 Jan '22

18 Jan '22

Hello, When extracting client_id information from the client connection (i.e. setting imap_id_log = *) the information is directly logged by Dovecot as such: ID sent: name=Thunderbird, version=91.5.0 My question is, Is it possible to export/set this information in a checkpassword script or a postlogin script? client_id If|imap_id_retain| <https://doc.dovecot.org/settings/core/#core_setting-imap_id_retain>is enabled this variable is populated with the client ID request as IMAP arglist. I've enabled both checkpassword and postlogin on a test server, as well as 'imap_id_retain' set to 'yes'. I wrote a simple Perl script that dumps everything in %ENV as well as @ARGV for checkpassword and postlogin, but I don't see any occurrences of ID information. I've also tried to see if I could supply that variable in dovecot.conf by setting 'client_id' as a parameter, but that didn't seem to do the trick either. passdb { ... # Doesn't work args = /usr/local/bin/checkpassword.pl client_id # Doesn't work args = /usr/local/bin/checkpassword.pl %{client_id} ... } What am I missing? Is it possible to get these variables into an external script that checkpassword or postlogin executes? Thanks.

3 2

Order of loading and checking userdb on Ubuntu
by Mike 16 Jan '22

16 Jan '22

When using the lmtp service for local delivery, I'd like to change the user lookup to only use the user portion of the email address. I think I do that in the 20-lmtp.conf file, but not exactly sure how. From what I've found on the web, I just need to change the auth_username_format=%n. I feel confident that I'm not doing it right. older posts implied that the order things are loaded is an issue, but not sure if that is the case anymore. My goal is to set username_format for only lmtp. Thanks for any help.

1 1

Wrong timestamp value in name of file
by Ervin Hegedüs 14 Jan '22

14 Jan '22

Hi there, Debian 10, Dovecot 2.3.4 (1:2.3.4.1-5+deb10u6), ext4 mailstore. A user on our server reorganized the sent items: he moved few items from the old sent folder into a new one. After that, he noticed me that he does not see every mail, but when he starts a search, then he finds it. I looked up the mail, and found this situation: # ls -la 1642152396.M997381P21341.mail2\,S\=473164\,W\=479469\:2\,S -rw-r--r-- 1 vmail vmail 473164 aug 24 10:21 '1642152396.M997381P21341.mail2,S=473164,W=479469:2,S' # grep Date '1642152396.M997381P21341.mail2,S=473164,W=479469:2,S' Date: Tue, 24 Aug 2021 10:21:39 +0200 # date -d @1642152396 Fri Jan 14 10:26:36 CET 2022 As you can see that mail had sent on 24 Aug, 2021, but after the reorganization it got a new timestamp with the date of today. I assume the client (iPhone) orders the mail by the name of files - am I right? Why did this happen? How can I fix that? I mean, is there any way to rename this files (a few hundred...) to the "real" timestamp? Thanks, a.

1 0

ssl=required per user?
by Arkadiusz Miśkiewicz 13 Jan '22

13 Jan '22

Can ssl=required be forced on per user setting? Right now I could modify password_query to check if %c (%{secured}) is empty and return appropriate error as "reason" like in https://doc.dovecot.org/configuration_manual/authentication/nologin/#authen… example. Unfortunately password_query is a bit too late. I would like to deny access as soon as possible, so just after user sends his login. (that won't help much in cases when client sends password early like "AUTH PLAIN b64loginpass" but will help in all other cases) user_query doesn't have this capability that password_query it seems. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

1 0

Is Diffie-Hellman needed?
by dovecot＠ptld.com 13 Jan '22

13 Jan '22

Is Diffie-Hellman needed on a modern new dovecot setup? ssl_dh is empty by default. Both ssl_cert and ssl_key on my setup are pointing to let's encrypt certs. However i see Diffie-Hellman related warnings in logs: dovecot[1073]: imap-login: Error: Diffie-Hellman key exchange requested, but no DH parameters provided. Set ssl_dh=</path/to/dh.pem Am i causing issues for some users by not setting up ssl_dh or is this something being phased out?

4 6

source code doesn't compile
by Ruben Safir 12 Jan '22

12 Jan '22

I downloaded the dovecot source and it doesn't compile. The install script fails in auth because it makes a file and then tries to make a directory over it make[2]: Entering directory '/home/ruben/src/dovecot-2.3.17.1/src/auth' make[3]: Entering directory '/home/ruben/src/dovecot-2.3.17.1/src/auth' /usr/bin/mkdir -p '/usr/local/lib/dovecot' /bin/sh ../../libtool --mode=install /usr/bin/install -c auth checkpassword-reply '/usr/local/lib/dovecot' libtool: warning: 'libstats_auth.la' has not been installed in '/usr/local/lib/dovecot/old-stats' libtool: install: /usr/bin/install -c .libs/auth /usr/local/lib/dovecot/auth libtool: install: /usr/bin/install -c .libs/checkpassword-reply /usr/local/lib/dovecot/checkpassword-reply /usr/bin/mkdir -p '/usr/local/lib/dovecot/auth' I am running an older version of dovecott and would really like to upgrade it and there is no package for this linux version -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and extermination camps, but incompatible with living as a free human being. -RI Safir 2013

7 14

Migrate mail_location
by hello＠reox.at 11 Jan '22

11 Jan '22

Hi! I have a dovecot installation, with the following configuration: mail_home = /var/vmail/%d/%n mail_location = maildir:~ I would like to migrate the mail_location to maildir:~/mail, to get around the issues described in the documentation. But I can not really find a good way to do that. I played around with doveadm sync/backup, but I can only copy everything into a new location (i.e. doveadm sync maildir:~/mail), but this does not really untangle the mail_home and location. My other idea was to migrate the maildir manually, i.e. move the maildir related folders and files (new, cur, tmp, all folders starting with a dot and containing itself {new,cur,tmp}, dovecot.* files, subscriptions file) into the ~/mail folder, but I'm not sure if this is a safe method. Is there any safe method to do this using dovecot tools? If the only way is a offline migration, I'm fine with that. Best, Sebastian

2 3

2.17.1 Fatal: master: service(doveadm): child 43879 killed with signal 6 (core dumped)
by Salatiel Filho 10 Jan '22

10 Jan '22

Hi, my dovecot 2.17.1 instance is crashing a lot. Quick question: The coredump should contain some private data, am I correct ? Assuming so, should it be posted on a public maillist? Panic: file dsync-ibc.c: line 166 (dsync_ibc_send_mail_request): assertion failed: (request->guid != NULL || request->uid != 0) ... Fatal: master: service(doveadm): child 43879 killed with signal 6 (core dumped) Using gdb/bt over the coredump I get: Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `dovecot/doveadm-server'. Program terminated with signal SIGABRT, Aborted. #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 50 return ret; (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x00007f612d382db5 in __GI_abort () at abort.c:79 #2 0x00007f612db04485 in default_fatal_finish (status=0, type=LOG_TYPE_PANIC) at failures.c:459 #3 fatal_handler_real (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at failures.c:471 #4 0x00007f612dbb10f7 in i_internal_fatal_handler (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at failures.c:872 #5 0x00007f612db04126 in i_panic (format=format@entry=0x5641e4c16ba8 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:524 #6 0x00005641e4bcfcb2 in dsync_ibc_send_mail_request (ibc=0x5641e50a5990, request=0x5641e51dcc70) at dsync-ibc.c:166 #7 0x00005641e4bfe0bc in dsync_brain_send_mail_request (brain=0x5641e50a8538) at dsync-brain-mails.c:215 #8 dsync_brain_sync_mails (brain=brain@entry=0x5641e50a8538) at dsync-brain-mails.c:418 #9 0x00005641e4bf9ad8 in dsync_brain_run_real (changed_r=0x7ffcd2397a47, brain=0x5641e50a8538) at dsync-brain.c:716 #10 dsync_brain_run (changed_r=0x7ffcd2397a47, brain=0x5641e50a8538) at dsync-brain.c:749 #11 dsync_brain_run (brain=0x5641e50a8538, changed_r=0x7ffcd2397a47) at dsync-brain.c:737 #12 0x00005641e4bfa13e in dsync_brain_run_io (context=0x5641e50a8538) at dsync-brain.c:110 #13 0x00005641e4c0b3c3 in dsync_ibc_stream_input (ibc=0x5641e50a5990) at dsync-ibc-stream.c:232 #14 0x00007f612dbc78ad in io_loop_call_io (io=0x5641e5040510) at ioloop.c:737 #15 0x00007f612dbc8f19 in io_loop_handler_run_internal (ioloop=ioloop@entry=0x5641e4f89ce0) at ioloop-epoll.c:222 #16 0x00007f612dbc7950 in io_loop_handler_run (ioloop=0x5641e4f89ce0) at ioloop.c:789 #17 0x00007f612dbc7ad0 in io_loop_run (ioloop=0x5641e4f89ce0) at ioloop.c:762 #18 0x00005641e4bddafa in cmd_dsync_run_remote (user=<optimized out>, user=<optimized out>) at doveadm-dsync.c:496 #19 cmd_dsync_run (_ctx=0x5641e4f89fe8, user=<optimized out>) at doveadm-dsync.c:703 #20 0x00005641e4bdfc26 in doveadm_mail_next_user (ctx=0x5641e4f89fe8, error_r=0x7ffcd2397de8) at doveadm-mail.c:462 #21 0x00005641e4be0d74 in doveadm_mail_cmd_exec (wildcard_user=0x0, ctx=0x5641e4f89fe8) at doveadm-mail.c:654 #22 doveadm_cmd_ver2_to_mail_cmd_wrapper (cctx=<optimized out>) at doveadm-mail.c:983 #23 0x00005641e4bf17c7 in doveadm_cmd_run_ver2 (argc=argc@entry=10, argv=argv@entry=0x5641e4fa3788, cctx=cctx@entry=0x7ffcd2397f40) at doveadm-cmd.c:465 #24 0x00005641e4bf5d1a in doveadm_cmd_server_run_ver2 (cctx=0x7ffcd2397f40, argv=0x5641e4fa3788, argc=10, conn=0x5641e4f81328) at client-connection-tcp.c:187 #25 doveadm_cmd_handle (cctx=0x7ffcd2397f40, argv=<optimized out>, argc=<optimized out>, cmd_name=<optimized out>, conn=0x5641e4f81328) at client-connection-tcp.c:214 #26 client_handle_command (args=<optimized out>, conn=0x5641e4f81328) at client-connection-tcp.c:284 #27 client_connection_tcp_input (conn=0x5641e4f81328) at client-connection-tcp.c:436 #28 0x00007f612dbc78ad in io_loop_call_io (io=0x5641e4f88ee0) at ioloop.c:737 #29 0x00007f612dbc8f19 in io_loop_handler_run_internal (ioloop=ioloop@entry=0x5641e4f3df40) at ioloop-epoll.c:222 #30 0x00007f612dbc7950 in io_loop_handler_run (ioloop=0x5641e4f3df40) at ioloop.c:789 #31 0x00007f612dbc7ad0 in io_loop_run (ioloop=0x5641e4f3df40) at ioloop.c:762 #32 0x00007f612db39287 in master_service_run (service=0x5641e4f3dda0, callback=<optimized out>) at master-service.c:863 #33 0x00005641e4bd09f2 in main (argc=<optimized out>, argv=<optimized out>) at main.c:124 # 2.3.17.1 (476cd46418): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.17.1 (a1a0b892) # OS: Linux 4.18.0-348.7.1.el8_5.x86_64 x86_64 AlmaLinux release 8.5 (Arctic Sphynx) xfs # Hostname: redacted auth_username_format = %Ln doveadm_password = # hidden, use -P to show it first_valid_uid = 1000 mail_home = /var/spool/imap/%n mail_location = maildir:/var/spool/imap/%n/mail:VOLATILEDIR=/var/spool/imap/%n 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 { list = children location = maildir:/var/spool/imap/redacted/mail/:INDEXPVT=/var/spool/imap/%n/pub-seen-idx/ mailbox * { autoexpunge = 60 days } prefix = redacted/ separator = / subscriptions = no type = public } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / } passdb { args = scheme=CRYPT username_format=%n /etc/dovecot/users driver = passwd-file } passdb { args = failure_show_msg=yes dovecot driver = pam } plugin { mail_replica = tcps:10.111.1.1:26 sieve = file:/var/spool/imap/%n/sieve;active=/var/spool/imap/%n/.dovecot.sieve sieve_before = /var/lib/dovecot/sieve.d/ sieve_global = /var/lib/dovecot/sieve.d/ } protocols = imap lmtp sieve replication_dsync_parameters = -d -N -l 60 -U service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = dovecot } unix_listener replication-notify { mode = 0666 user = dovecot } } service doveadm { inet_listener { port = 26 ssl = yes } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 user = dovecot } } ssl = required ssl_cert = </etc/ssl/certs/cluster-redacted.crt ssl_key = # hidden, use -P to show it userdb { args = username_format=%n /etc/dovecot/users default_fields = uid=vmail gid=mail home=/var/spool/imap driver = passwd-file } userdb { driver = passwd override_fields = uid=vmail gid=mail home=/var/spool/imap/%n } protocol lmtp { mail_plugins = " notify replication sieve" } protocol imap { ssl_cert = </etc/ssl/certs/redacted.crt ssl_key = # hidden, use -P to show it } Atenciosamente/Kind regards, Salatiel

1 0

Spamassassin fails
by Hans Brage 10 Jan '22

10 Jan '22

Hi! I've been running a server with Dovecot, Sieve, Spamassassin and getmail to handle my emails for several years now. Just before christmas I did one of these regular updates and since then I got problems with spamassassin. Quite a lot of spam is not been filtered out. I can see a lot of errors like these in the mail-log. spamd: failed to create readable default_prefs: /home/vmail/.spamassassin/user_prefs Vmail is the user that is running my scripts that retrieves email and executes spamc. Any ideas? Regards, Hans

2 3

Dovecot 2.3.17 on FreeBSD 12.2 panic
by Bert JW Regeer 10 Jan '22

10 Jan '22

Hello, I have dovecot 2.3.17 running on FreeBSD 12.2 and it keeps panicking: Jan 10 03:04:07 strida dovecot[55198]: imap(xistence(a)0x58.com)<56382><dx4KlzHVQecmAQKCQwA50VytdgLnsQSr>: Panic: file array.c: line 10 (array_idx_modifiable_i): assertion failed: (idx < array->buffer->used / array->element_size) Jan 10 03:04:07 strida dovecot[55198]: imap(xistence(a)0x58.com)<56382><dx4KlzHVQecmAQKCQwA50VytdgLnsQSr>: Fatal: master: service(imap): child 56382 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps) Ignore the core not dumped, this is happening over and over, and I got one process to core dump: # lldb /usr/local/libexec/dovecot/imap -c imap.core (lldb) target create "/usr/local/libexec/dovecot/imap" --core "imap.core" Core file '/usr/local/vmail/domains/0x58.com/xistence/imap.core' (x86_64) was loaded. (lldb) bt * thread #1, name = 'imap', stop reason = signal SIGABRT * frame #0: 0x0000000011588c2a libc.so.7`__sys_thr_kill + 10 frame #1: 0x0000000011587084 libc.so.7`__raise + 52 frame #2: 0x00000000114fd279 libc.so.7`abort + 73 frame #3: 0x00000000113736f3 libdovecot.so.0`___lldb_unnamed_symbol873$$libdovecot.so.0 + 147 frame #4: 0x0000000011371eaf libdovecot.so.0`___lldb_unnamed_symbol862$$libdovecot.so.0 + 47 frame #5: 0x0000000011372c71 libdovecot.so.0`___lldb_unnamed_symbol864$$libdovecot.so.0 + 33 frame #6: 0x00000000113720bb libdovecot.so.0`i_panic + 187 frame #7: 0x0000000011363d3f libdovecot.so.0`array_idx_modifiable_i + 79 frame #8: 0x0000000011ef7c68 lib20_fts_plugin.so`fts_user_autoindex_exclude + 72 frame #9: 0x0000000011ef550f lib20_fts_plugin.so`fts_mailbox_allocated + 239 frame #10: 0x000000001113ed5a libdovecot-storage.so.0`hook_mailbox_allocated + 154 frame #11: 0x00000000111381e1 libdovecot-storage.so.0`mailbox_alloc + 449 frame #12: 0x0000000001043db4 imap`cmd_select_full + 356 frame #13: 0x000000000104c582 imap`command_exec + 178 frame #14: 0x000000000104ae8a imap`___lldb_unnamed_symbol58$$imap + 58 frame #15: 0x000000000104af91 imap`___lldb_unnamed_symbol58$$imap + 321 frame #16: 0x00000000010499e7 imap`client_handle_input + 471 frame #17: 0x0000000001048178 imap`client_input + 120 frame #18: 0x000000001138ca9f libdovecot.so.0`io_loop_call_io + 111 frame #19: 0x000000001138f45b libdovecot.so.0`io_loop_handler_run_internal + 347 frame #20: 0x000000001138cffa libdovecot.so.0`io_loop_handler_run + 346 frame #21: 0x000000001138ce58 libdovecot.so.0`io_loop_run + 88 frame #22: 0x00000000112f11c8 libdovecot.so.0`master_service_run + 24 frame #23: 0x000000000105a417 imap`main + 1383 frame #24: 0x000000000103bed2 imap`_start + 226 (lldb) ^D I was able to generate a core dump by issue a doveadm command too: (lldb) bt * thread #1, name = 'doveadm', stop reason = signal SIGABRT * frame #0: 0x00000008017b1c2a libc.so.7`__sys_thr_kill + 10 frame #1: 0x00000008017b0084 libc.so.7`__raise + 52 frame #2: 0x0000000801726279 libc.so.7`abort + 73 frame #3: 0x000000080159c6f3 libdovecot.so.0`___lldb_unnamed_symbol873$$libdovecot.so.0 + 147 frame #4: 0x000000080159aeaf libdovecot.so.0`___lldb_unnamed_symbol862$$libdovecot.so.0 + 47 frame #5: 0x000000080159ae71 libdovecot.so.0`default_fatal_handler + 33 frame #6: 0x000000080159b0bb libdovecot.so.0`i_panic + 187 frame #7: 0x000000080158cd3f libdovecot.so.0`array_idx_modifiable_i + 79 frame #8: 0x0000000802236c68 lib20_fts_plugin.so`fts_user_autoindex_exclude + 72 frame #9: 0x000000080223450f lib20_fts_plugin.so`fts_mailbox_allocated + 239 frame #10: 0x0000000801367d5a libdovecot-storage.so.0`hook_mailbox_allocated + 154 frame #11: 0x00000008013611e1 libdovecot-storage.so.0`mailbox_alloc + 449 frame #12: 0x000000080222d5fc lib20_fts_plugin.so`fts_backend_rescan + 60 frame #13: 0x000000080227c1a3 lib20_doveadm_fts_plugin.so`___lldb_unnamed_symbol15$$lib20_doveadm_fts_plugin.so + 99 frame #14: 0x000000000107172f doveadm`___lldb_unnamed_symbol134$$doveadm + 479 frame #15: 0x000000000107252c doveadm`doveadm_cmd_ver2_to_mail_cmd_wrapper + 2492 frame #16: 0x0000000001083c98 doveadm`doveadm_cmd_run_ver2 + 1416 frame #17: 0x00000000010836d7 doveadm`doveadm_cmd_try_run_ver2 + 71 frame #18: 0x0000000001086da3 doveadm`main + 835 frame #19: 0x000000000105fa92 doveadm`_start + 226 (lldb) # doveadm fts rescan -u xistence(a)0x58.com doveadm(xistence(a)0x58.com): Panic: file array.c: line 10 (array_idx_modifiable_i): assertion failed: (idx < array->buffer->used / array->element_size) Abort (core dumped) # dovecot-sysreport Gathering configurations ... grep: The -P option is not supported grep: The -P option is not supported grep: The -P option is not supported Gathering system informations ... Creating archive ... All done! Please report file dovecot-sysreport-strida.0x58.com-1641784164.tar.gz Removing temp files at /tmp/tmp.z5qJkwrW … While reading about fts/fts_squat I came across the page noting it was deprecated. I am running a mail server for myself, and have avoided installing Solr this entire time, but I guess its time to upgrade. In the mean time hopefully this core dump can help figure out what is going on. Bert JW Regeer

2 3

outlook 2019 not working
by postmaster 10 Jan '22

10 Jan '22

Just tried connecting a Windows 10 client with Outlook 2019 but it fail's on both POP3 or IMAP - i knew it was working when i tested it after the server setup about a year ago because i documented everything with screenshots. All other devices we use (Thunderbird, iPhone/iPad, Android devices, RoundCube) are working without any issue, just Outlook won't connect anymore. We don't have much Windows/Outlook experience - any help/hints appreciated. This what i have in the logs, but doesn't see anything that helps: 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x10, ret=1: before SSL initialization 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: before SSL initialization 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read client hello 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server hello 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write certificate 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write key exchange 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read client key exchange 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read change cipher spec 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read finished 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write session ticket 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write change cipher spec 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write finished 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x20, ret=1: SSL negotiation finished successfully 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully 2022.01.10 02:22:25 pop3-login: Info: Login: user=<user1(a)mail-server.cc>, method=PLAIN, rip=178.189.103.34, lip=195.88.238.13, mpid=1694, TLS, TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Loading modules from directory: /usr/lib/dovecot/modules 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib01_acl_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib15_notify_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_mail_log_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_replication_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_virtual_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_zlib_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Added userdb setting: plugin/quota_rule=*:bytes=10240000 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Effective uid=5000, gid=5000, home=/srv/vmail/mail-server.cc/user1/ 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(file): dict created (uri=file:/srv/vmail/shared-mailboxes.db, base_dir=/var/run/dovecot) 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota root: name=User Quota backend=dict args=:proxy::sqluserquota 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota rule: root=User Quota mailbox=* bytes=10240000 messages=0 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota rule: root=User Quota mailbox=Trash bytes=+1024000 (10%) messages=0 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota rule: root=User Quota mailbox=Sent bytes=+1024000 (10%) messages=0 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota warning: bytes=10240000 (100%) messages=0 reverse=no command=quota-warning 100 user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota warning: bytes=9728000 (95%) messages=0 reverse=no command=quota-warning 95 user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota warning: bytes=9216000 (90%) messages=0 reverse=no command=quota-warning 90 user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota warning: bytes=8192000 (80%) messages=0 reverse=no command=quota-warning 80 user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota grace: root=User Quota bytes=1024000 (10%) 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: quota-dict: user=user1(a)mail-server.cc, uri=proxy::sqluserquota, noenforcing=0 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(proxy): dict created (uri=proxy::sqluserquota, base_dir=/var/run/dovecot) 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/srv/vmail/mail-server.cc/user1/maildir 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: maildir++: root=/srv/vmail/mail-server.cc/user1/maildir, index=, indexpvt=, control=, inbox=/srv/vmail/mail-server.cc/user1/maildir,alt= 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: initializing backend with data: vfile 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: acl username = user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: owner = 1 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl vfile: Global ACLs disabled 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Namespace : type=shared, prefix=shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=yes location=maildir:/srv/vmail/%d/%n/maildir:INDEX=~/maildir/shared/%u:CONTROL=~/maildir/shared/%u 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: shared: root=/var/run/dovecot, index=, indexpvt=, control=, inbox=, alt= 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: initializing backend with data: vfile 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: acl username = user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: owner = 0 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl vfile: Global ACLs disabled 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: quota: quota_over_flag check: quota_over_script unset - skipping 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Mailbox INBOX: Mailbox opened because: POP3 INBOX 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl vfile: file /srv/vmail/mail-server.cc/user1/maildir/dovecot-acl not found 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Info: Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0, bytes=12/43 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(proxy): Waiting for dict to finish pending operations 2022.01.10 02:22:25 pop3-login: Debug: SSL alert: close notify 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(file): dict destroyed 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(proxy): Waiting for dict to finish pending operations 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(proxy): dict destroyed 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x10, ret=1: before SSL initialization 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=-1: before SSL initialization 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read client hello 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server hello 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write certificate 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write key exchange 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read client key exchange 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read change cipher spec 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read finished 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write session ticket 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write change cipher spec 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write finished 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x20, ret=1: SSL negotiation finished successfully 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully 2022.01.10 02:23:00 imap-login: Info: Login: user=<user1(a)mail-server.cc>, method=PLAIN, rip=178.189.103.34, lip=195.88.238.13, mpid=1696, TLS, TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Loading modules from directory: /usr/lib/dovecot/modules 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib01_acl_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib02_imap_acl_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib11_imap_quota_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib15_notify_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_mail_log_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_replication_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_virtual_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_zlib_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib95_imap_sieve_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Added userdb setting: plugin/quota_rule=*:bytes=10240000 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Effective uid=5000, gid=5000, home=/srv/vmail/mail-server.cc/user1/ 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: dict(file): dict created (uri=file:/srv/vmail/shared-mailboxes.db, base_dir=/var/run/dovecot) 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota root: name=User Quota backend=dict args=:proxy::sqluserquota 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota rule: root=User Quota mailbox=* bytes=10240000 messages=0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota rule: root=User Quota mailbox=Trash bytes=+1024000 (10%) messages=0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota rule: root=User Quota mailbox=Sent bytes=+1024000 (10%) messages=0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota warning: bytes=10240000 (100%) messages=0 reverse=no command=quota-warning 100 user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota warning: bytes=9728000 (95%) messages=0 reverse=no command=quota-warning 95 user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota warning: bytes=9216000 (90%) messages=0 reverse=no command=quota-warning 90 user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota warning: bytes=8192000 (80%) messages=0 reverse=no command=quota-warning 80 user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota grace: root=User Quota bytes=1024000 (10%) 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: quota-dict: user=user1(a)mail-server.cc, uri=proxy::sqluserquota, noenforcing=0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: dict(proxy): dict created (uri=proxy::sqluserquota, base_dir=/var/run/dovecot) 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/srv/vmail/mail-server.cc/user1/maildir 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: maildir++: root=/srv/vmail/mail-server.cc/user1/maildir, index=, indexpvt=, control=, inbox=/srv/vmail/mail-server.cc/user1/maildir,alt= 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: initializing backend with data: vfile 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: acl username = user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: owner = 1 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl vfile: Global ACLs disabled 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Namespace : type=shared, prefix=shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=yes location=maildir:/srv/vmail/%d/%n/maildir:INDEX=~/maildir/shared/%u:CONTROL=~/maildir/shared/%u 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: shared: root=/var/run/dovecot, index=, indexpvt=, control=, inbox=, alt= 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: initializing backend with data: vfile 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: acl username = user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: owner = 0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl vfile: Global ACLs disabled 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: quota: quota_over_flag check: quota_over_script unset - skipping 2022.01.10 02:23:00 imap-login: Debug: SSL error: Connection closed 2022.01.10 02:23:00 imap-login: Debug: SSL alert: close notify 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl vfile: file /srv/vmail/mail-server.cc/user1/maildir/dovecot-acl not found 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Info: Disconnected: Connection closed (IDLE running for 0.001 + waiting input for 0.001 secs, 2 B in + 10 B out, state=wait-input) in=11 out=461 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: dict(file): dict destroyed 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: dict(proxy): Waiting for dict to finish pending operations 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: dict(proxy): dict destroyed thx, Alex

2 1

Patch: assertion failed in doveadm fts lookup
by John Fawcett 09 Jan '22

09 Jan '22

Hi I'm reposting this patch, which I have been applying locally since I originally posted it. Hopefully it can be considered for inclusion in the official release. It was tested on dovecot 2.3.16 but applies against the latest version 2.3.17.1. This is the "assertion failed" that it addresses doveadm fts lookup -u john(a)voipsupport.it body "text to look for" doveadm(john(a)voipsupport.it): Panic: file mail-storage.c: line 2108 (mailbox_get_open_status): assertion failed: (box->opened) doveadm(john(a)voipsupport.it): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7ff624fa7072] -> /usr/local/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7ff624fa718e] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xffc3b) [0x7ff624fb3c3b] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xffc71) [0x7ff624fb3c71] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x5536f) [0x7ff624f0936f] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0x3fc31) [0x7ff6250bcc31] -> /usr/local/lib/dovecot/lib21_fts_solr_plugin.so(+0x540d) [0x7ff62244f40d] -> /usr/local/lib/dovecot/lib20_fts_plugin.so(fts_backend_lookup+0x4d) [0x7ff6246b624d] -> /usr/local/lib/dovecot/doveadm/lib20_doveadm_fts_plugin.so(+0x2e8c) [0x7ff62240ce8c] -> doveadm(+0x31ded) [0x55f0c7f3aded] -> doveadm(+0x32862) [0x55f0c7f3b862] -> doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x22d) [0x55f0c7f3c6fd] -> doveadm(doveadm_cmd_run_ver2+0x4d8) [0x55f0c7f4d158] -> doveadm(doveadm_cmd_try_run_ver2+0x3a) [0x55f0c7f4d1aa] -> doveadm(main+0x1f6) [0x55f0c7f2b606] -> /lib64/libc.so.6(__libc_start_main+0xd5) [0x7ff624bc8b75] -> doveadm(_start+0x2e) [0x55f0c7f2ba0e] Aborted (core dumped) Here's the patch: diff -ur dovecot-2.3.17.1-orig/src/plugins/fts/doveadm-fts.c dovecot-2.3.17.1-new/src/plugins/fts/doveadm-fts.c --- dovecot-2.3.17.1-orig/src/plugins/fts/doveadm-fts.c 2021-12-03 12:48:47.000000000 +0100 +++ dovecot-2.3.17.1-new/src/plugins/fts/doveadm-fts.c 2022-01-09 01:33:23.396342025 +0100 @@ -47,6 +47,14 @@ i_array_init(&result.scores, 16); box = mailbox_alloc(info->ns->list, info->vname, 0); + mailbox_set_reason(box,"fts search"); + if (mailbox_open(box) < 0) { + i_error("Couldn't open mailbox: %s", + mailbox_get_last_internal_error(box, NULL)); + doveadm_mail_failed_error(ctx, MAIL_ERROR_TEMP); + return -1; + } + if (fts_backend_lookup(backend, box, ctx->search_args->args, FTS_LOOKUP_FLAG_AND_ARGS, &result) < 0) { i_error("fts lookup failed"); John

2 1

Non-user logins?
by Ken Wright 09 Jan '22

09 Jan '22

My Dovecot issues continue. Right now I see at least two issues: first, my logs consistently show non-users trying (and failing) to log in, and I'm still unable to log in from my email client (Evolution or Roundcube, either one). I'll post about the second issue later; right now I wonder why I'm getting so many non-users trying to log in. Am I the subject of concerted hacking attacks, or is there something else going on? Some of the attempted logins are more-or-less random names claiming to be @mydomain, but at least one is a username that's really on my server, to wit: Jan 7 22:52:01 grace dovecot: lmtp(776281): Error: lmtp-server: conn unix:pid=776262,uid=117 [3]: rcpt www-data(a)mydomain.com: Failed to lookup user www-data(a)mydomain.com: Internal error occurred. Refer to server log for more information. (Another quick question: which server log should I check?) So, if anyone can tell me what's going on with all these logins, I'd be much obliged! Ken

9 16

Patch: enhancements for solr/tika integration
by John Fawcett 09 Jan '22

09 Jan '22

Hi here's a patch with some enhancements that I am applying locally for solr/tika integration. Hopefully this can be considered for inclusion. I've tested up to 2.3.16 and this patch applies against latest version 2.3.17.1. The contents are: 1. Allow username and password in tika configuration (as is already supported for solr). For example: fts_tika = https://user:password@tika_host:tika_port/tika/tika This means that tika can be more easily located on a different server to dovecot. Locating Solr and Tika on separate servers can isolate the Dovecot server from issues that may happen on Solr or Tika (like out of memory). 2. Introduce an optional configurable limit on the size of emails whose message bodies will be indexed with solr via a new setting fts_max_size, to be put in the plugin section. For example plugin { ... fts_max_size = 2M ... } Message body indexing is skipped for messages that are larger than this setting. 3. Introduce an optional configurable limit on the size of emails whose attachments will be sent to tika for keyword extraction, via a new setting fts_max_size_tika, to be put in the plugin section. For example: plugin { ... fts_max_size_tika = 1M } I noticed that some very large attachments are being sent to tika and these often do not have any useful content to index. For simplicity the check is done on message size not individual or total attachment size. Here's the patch: diff -ur dovecot-2.3.17.1-orig/src/plugins/fts/fts-build-mail.c dovecot-2.3.17.1-new/src/plugins/fts/fts-build-mail.c --- dovecot-2.3.17.1-orig/src/plugins/fts/fts-build-mail.c 2021-12-03 12:48:47.000000000 +0100 +++ dovecot-2.3.17.1-new/src/plugins/fts/fts-build-mail.c 2022-01-09 01:33:23.398341998 +0100 @@ -17,6 +17,7 @@ #include "fts-filter.h" #include "fts-api-private.h" #include "fts-build-mail.h" +#include "settings-parser.h" /* there are other characters as well, but this doesn't have to be exact */ #define IS_WORD_WHITESPACE(c) \ @@ -25,6 +26,8 @@ wherever */ #define MAX_WORD_SIZE 1024 +static bool debug = FALSE; + struct fts_mail_build_context { struct mail *mail; struct fts_backend_update_context *update_ctx; @@ -34,6 +37,7 @@ buffer_t *word_buf, *pending_input; struct fts_user_language *cur_user_lang; + bool oversized_tika; }; static int fts_build_data(struct fts_mail_build_context *ctx, @@ -223,7 +227,7 @@ parser_context.user = mail_storage_get_user(storage); parser_context.content_disposition = ctx->content_disposition; - + parser_context.oversized_tika = ctx->oversized_tika; if (fts_parser_init(&parser_context, &ctx->body_parser)) { /* extract text using the the returned parser */ *binary_body_r = TRUE; @@ -496,7 +500,32 @@ bool binary_body; const char *error; int ret; - + uoff_t msg_size; + uoff_t fts_max_size = 0; + uoff_t fts_max_size_tika = 0; + const char * fts_max_size_setting; + const char * fts_max_size_tika_setting; + bool oversized_msg; + bool oversized_tika; + + fts_max_size_setting = mail_user_plugin_getenv(update_ctx->backend->ns->user, "fts_max_size"); + if (fts_max_size_setting != NULL) { + if (debug) i_debug("fts_max_size %s",fts_max_size_setting); + if (settings_get_size(fts_max_size_setting, &fts_max_size, &error) < 0) { + i_error("%s",error); + fts_max_size = 0; + } + if (debug) i_debug("fts_max_size (value) %"PRIuUOFF_T,fts_max_size); + } + fts_max_size_tika_setting = mail_user_plugin_getenv(update_ctx->backend->ns->user, "fts_max_size_tika"); + if (fts_max_size_tika_setting != NULL) { + if (debug) i_debug("fts_max_size_tika %s",fts_max_size_tika_setting); + if (settings_get_size(fts_max_size_tika_setting, &fts_max_size_tika, &error) < 0) { + i_error("%s",error); + fts_max_size_tika = 0; + } + if (debug) i_debug("fts_max_size_tika (value) %"PRIuUOFF_T,fts_max_size_tika); + } *may_need_retry_r = FALSE; if (mail_get_stream_because(mail, NULL, NULL, "fts indexing", &input) < 0) { if (mail->expunged) @@ -505,10 +534,21 @@ mailbox_get_last_internal_error(mail->box, NULL)); return -1; } - + oversized_msg = FALSE; + oversized_tika = FALSE; + i_stream_get_size(input,TRUE,&msg_size); + if (fts_max_size > 0 && msg_size > fts_max_size) { + i_info("Skipping message body indexing because size %"PRIuUOFF_T" exceeds setting fts_max_size %s",msg_size,fts_max_size_setting); + oversized_msg = TRUE; + } + if (fts_max_size_tika > 0 && msg_size > fts_max_size_tika) { + i_info("Skipping message attachment indexing because size %"PRIuUOFF_T" exceeds setting fts_max_size_tika %s",msg_size,fts_max_size_tika_setting); + oversized_tika = TRUE; + } i_zero(&ctx); ctx.update_ctx = update_ctx; ctx.mail = mail; + ctx.oversized_tika = oversized_tika; if ((update_ctx->backend->flags & FTS_BACKEND_FLAG_TOKENIZED_INPUT) != 0) ctx.pending_input = buffer_create_dynamic(default_pool, 128); @@ -563,7 +603,7 @@ message_decoder_set_return_binary(decoder, TRUE); body_part = TRUE; } else { - if (skip_body) + if (skip_body ||oversized_msg) continue; } @@ -597,7 +637,7 @@ else (void)fts_parser_deinit(&ctx.body_parser, NULL); } - if (ret == 0 && body_part && !skip_body && !body_added) { + if (ret == 0 && body_part && !skip_body && !oversized_msg && !body_added) { /* make sure body is added even when it doesn't exist */ block.data = NULL; block.size = 0; ret = fts_build_body_block(&ctx, &block, TRUE); diff -ur dovecot-2.3.17.1-orig/src/plugins/fts/fts-parser.h dovecot-2.3.17.1-new/src/plugins/fts/fts-parser.h --- dovecot-2.3.17.1-orig/src/plugins/fts/fts-parser.h 2021-12-03 12:48:47.000000000 +0100 +++ dovecot-2.3.17.1-new/src/plugins/fts/fts-parser.h 2022-01-09 01:33:23.399341985 +0100 @@ -10,6 +10,7 @@ /* Can't be NULL */ const char *content_type; const char *content_disposition; + bool oversized_tika; }; struct fts_parser_vfuncs { diff -ur dovecot-2.3.17.1-orig/src/plugins/fts/fts-parser-tika.c dovecot-2.3.17.1-new/src/plugins/fts/fts-parser-tika.c --- dovecot-2.3.17.1-orig/src/plugins/fts/fts-parser-tika.c 2021-12-03 12:48:47.000000000 +0100 +++ dovecot-2.3.17.1-new/src/plugins/fts/fts-parser-tika.c 2022-01-09 01:33:23.400341972 +0100 @@ -57,7 +57,7 @@ tuser = p_new(user->pool, struct fts_parser_tika_user, 1); MODULE_CONTEXT_SET(user, fts_parser_tika_user_module, tuser); - if (http_url_parse(url, NULL, 0, user->pool, + if (http_url_parse(url, NULL, HTTP_URL_ALLOW_USERINFO_PART, user->pool, &tuser->http_url, &error) < 0) { i_error("fts_tika: Failed to parse HTTP url %s: %s", url, error); return -1; @@ -148,6 +148,10 @@ if (tika_get_http_client_url(parser_context->user, &http_url) < 0) return NULL; + if (parser_context->oversized_tika) { + i_info("skipping tika parser due to oversized message"); + return NULL; + } if (http_url->path == NULL) http_url->path = "/"; @@ -159,6 +163,11 @@ http_url->host.name, t_strconcat(http_url->path, http_url->enc_query, NULL), fts_tika_parser_response, parser); + if (http_url->user != NULL) { + http_client_request_set_auth_simple( + http_req, http_url->user, http_url->password); + } + http_client_request_set_port(http_req, http_url->port); http_client_request_set_ssl(http_req, http_url->have_ssl); if (parser_context->content_type != NULL) John

1 0

Patch: safeguard against too large value for uid being sent to solr for single mailbox searches
by John Fawcett 09 Jan '22

09 Jan '22

Hi I'm reposting a patch for solr integration which I have been applying locally. It applies against 2.3.17.1. Dovecot already has a mechanism when doing solr fts searches on multiple mailboxes that prevents a too large value for maximum rows being sent to solr. #define SOLR_MAX_MULTI_ROWS 100000 (defined and used in plugins/fts-solr/fts-backend-solr.c) However on single mailbox searches Dovecot uses the last uid of the mailbox, which can be too large for solr. My suggested patch is to also limit maximum rows to return on single mailbox searches. Here is the patch: diff -ur dovecot-2.3.17.1-orig/src/plugins/fts-solr/fts-backend-solr.c dovecot-2.3.17.1-new/src/plugins/fts-solr/fts-backend-solr.c --- dovecot-2.3.17.1-orig/src/plugins/fts-solr/fts-backend-solr.c 2021-12-03 12:48:47.000000000 +0100 +++ dovecot-2.3.17.1-new/src/plugins/fts-solr/fts-backend-solr.c 2022-01-09 01:33:23.401341959 +0100 @@ -837,7 +837,7 @@ str = t_str_new(256); str_printfa(str, "wt=xml&fl=uid,score&rows=%u&sort=uid+asc&q=%%7b!lucene+q.op%%3dAND%%7d", - status.uidnext); + I_MIN(status.uidnext,SOLR_MAX_MULTI_ROWS)); prefix_len = str_len(str); if (solr_add_definite_query_args(str, args, and_args)) { John

1 0

Can't log in from Evolution or Roundcube
by Ken Wright 09 Jan '22

09 Jan '22

When I try to log in to my mail server (ubuntu 20.04, Postfix 3.4.13, Dovecot 2.3.7.2) I get a response saying "Source stream returned no data”. At least to me, that's not particularly informative. Is it any more informative to anyone else? Ken

3 10

Sv: banning
by Sebastian Nielsen 08 Jan '22

08 Jan '22

I would say, lock accounts to for example IP address, ASN or GeoIP. This can be accomplished simply by a custom login handler, which also checks IP against database. And first time users, and those who change country/ISP/IP have to simply logon to a web interface (where 2FA can be required and also Captcha) and add their IPs/ASNs/Geo's. For a larger user base, I would recommend GeoIP and no web interface, save country of first login to database, and subsequent logins must originate from same country. Users that want to reset have to contact support. If you are a web hotel who only sell service to a specific country at all, lock the ports in firewall to that GeoIP. For smaller user base, like 50-100 users, I would recommend locking to ASN and providing a web interface where multiple ASN can be added. So people syncing from mobile and home can succeed. For very small user base, like 10's of users, just plan lock to IP. By connecting IP to accounts, you greatly reduce the attack surface.

1 0

TLS connection closed unexpectedly
by Ken Wright 08 Jan '22

08 Jan '22

I reinstalled Dovecot this evening, because I haven't been able to receive emails recently. After configuring and adjusting for the use of PostfixAdmin, I get the following error message in Evolution:; Failed to open folder. The reported error was "Failed to authenticate: TLS connection closed unexpectedly". Does anyone recognize this error? Ken

6 8

Update from 2.3.16 to 2.3.17 Received invalid SSL certificate: unable to get certificate CRL
by Salatiel Filho 08 Jan '22

08 Jan '22

Hi, after updating from dovecot.x86_64 2:2.3.16-2 to 2:2.3.17.1-1 on AlmaLinux 8 my dovecot replication stopped working. Log is full of Error: doveadm server disconnected before handshake: Received invalid SSL certificate: unable to get certificate CRL: /CN=my.domain.redacted (check ssl_client_ca_* settings?) No configuration has changed on my side. My certificate is a wildcard certificate ( not sure if related ). I am also replicating over tcps. Anyone else facing this issue? Atenciosamente/Kind regards, Salatiel

1 0

Sieve scripts igniored
by Sam R 07 Jan '22

07 Jan '22

Hello, I have an issue with Sieve plugin, I can drive rules remotely with sieve:// myserver.fr:4190/?tls=YES, the rules are well created under /home/vmail/name.firstname, but these are never executed. I have also read https://doc.dovecot.org/configuration_manual/sieve/troubleshooting/, but I don't see any evident mistake. here is my dovecot -n : # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 5.10.0-8-amd64 x86_64 Debian 11.0 ext4 # Hostname: mail.xxx.fr auth_debug = yes auth_gssapi_hostname = $ALL auth_krb5_keytab = /etc/dovecot/dovecot.keytab auth_mechanisms = login plain gssapi mail_location = maildir:/home/vmail/%n/Maildir/ mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relationa l regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttex t namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } passdb { driver = pam } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap lmtp sieve pop3" service lmtp { executable = lmtp -L unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } ssl = required ssl_cert = </etc/letsencrypt/live/mail.xxx.fr/fullchain.pem ssl_client_ca_dir = /etc/ssl/certs ssl_client_ca_file = /etc/letsencrypt/live/mail.xxx.fr/chain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd } userdb { args = uid=vmail gid=vmail home=/home/vmail/%u allow_all_users=yes driver = static } userdb { driver = passwd } protocol lmtp { mail_plugins = " sieve" } protocol lda { mail_plugins = " sieve" } Thanks for helping. kind regards. Samuel

3 3

feature-request: make received-header on submission optional or at least drop the ip in it
by dc-ml＠dvl.werbittewas.de 07 Jan '22

07 Jan '22

hi. we're just trying to re-structure a system and want to use dovcots submission-ability. because the github-repository have no entry for any issues at all, we're sending this feature-fequest to this ML. unfortunately there doesn't seem to be any option to drop the received-header at all or at least hide the IP of the user. because the client-ip is covered by GDPR as personal data and so it should never shown to others without a certain reason, we want to hide it, but there's no "submission_add_received_header"-option like for lmtp and it doesn't seem to be any other option to hide this information. maybe this is possible to implement in near future? thanks a lot. best regards d.

8 18

Dovecot fixing maildir message size?
by Grant Keller 07 Jan '22

07 Jan '22

We recently updated dovecot from 2.1.17 to 2.3.10. It used to be when we encountered the following error: Jan 6 15:29:20 d.imapd.sonic.net dovecot: imap(momomo): session=aBd2O/LULMu4F6ia Error: Mailbox INBOX: UID=1: read(/var/spool/mail/07/00/momomo/cur/1510707300.12345_0.a.spam,S=1234:2,) failed: Cached message size larger than expected (1234 > 704, box=INBOX, UID=1) (read reason=) Dovecot would fix the size by renaming the file. Now this doesn't appear to be the case. Was there a change in behaviour, or is there an option I need to enable now to have dovecot auto fix this?

1 0

Re: Error: fts_solr: received invalid uid
by oliver.krone＠snoog.ch 07 Jan '22

07 Jan '22

Hello, I made serveral tests, never had a problemm woth dovecot version 2.3.4 with 2.3.13 things get worse and dovecot crashes. I might have read someting in the release notes of dovecot 2.3.13. that there is a problem. Regards Oliver > On 1/2/22 3:08 PM, John Fawcett wrote: >> unless I'm missing something that doesn't look like the type of query >> dovecot launches - dovecot sends various parameters including the >> request for xml results. The thing that looks odd to me is that the >> results fields should be single values not arrays enclosed in [], ie I >> would have expected >> "uid":21, >> >> instead of >> >> "uid":[21], >> >> I'd be interested to see the equivalent xml output produced by running >> a query that dovecot sends. >> > > This Solr instance is not configured properly for dovecot.? Most of the > fields are configured as multiValued (which is why you see an array > rather than a single value), and the response is JSON.? A Solr instance > that is properly configured for dovecot would return XML, not JSON. > > You're going to want to provide a proper solrconfig.xml and > managed-schema file, restart Solr or reload the core for dovecot, and > do > a full reindex.? At the following URL, you can find the shell script > that I use to do a full reindex: > > https://apaste.info/tK1B > > At the following URL are links to the solrconfig.xml and schema that > are > appropriate for dovecot.? These instructions say to name the schema > file > "schema.xml" ... this will work, as long as Solr has read-write access > to the conf directory so it can rename the file to "managed-schema".? > If > it doesn't, then you should name the file "managed-schema" yourself. > > https://doc.dovecot.org/configuration_manual/fts/solr/ > > Thanks, > Shawn

2 2

Doveadm auth test fails
by Ken Wright 07 Jan '22

07 Jan '22

I've been having trouble logging into my email server (postfix 3.4.13, dovecot 2.3.7.2, postfixadmin 3.3.8). I decided to try the doveadm auth test, and got the following result: kwright@grace:~$ sudo doveadm auth test me(a)mydomain.com Password: passdb: me(a)mydomain.com auth failed extra fields: user=me(a)mydomain.com I logged in to PostfixAdmin and made sure I was using the correct password, but got exactly the same result afterward. Should I have restarted Dovecot after changing the password? I'm totally confused by this problem; any and all suggestions will be gratefully received! Ken

3 6

Enable push notifications for all users
by Felix Ingram 06 Jan '22

06 Jan '22

Hello all, Is there a way to enable push notifications for all users, rather than having to enable them one by one? My thinking was to set mail_attribute_dict to a static file but I can’t work out what I would need to put in it. (I’ve now realised that that will not allow me to have other attributes to be different per user, but that’s not a real issue with my use case) If a flat file isn’t the answer, then is a SQL dict my best bet? Thanks in advance, Felix

2 4

Re: Expunged message reappeared
by Claudio Corvino 05 Jan '22

05 Jan '22

Hi Alex, thanks for your answer, I think this could be related to Dovecot version in use, in our case it is the same: 2.3.4.1 (f79e8e7e4). It could be useful to know if someone can confirm this assumption so we can try an upgrade to the latest version hoping this could solve our issue. Regards On 07/12/21 08:36, Joelly Alexander wrote: > > Don't have the issue with duplicate logs but same problem with > re-appearing of deleted messages very often in a two node setup with > dsync replication. > Messages sometimes have to be deleted multiple times until they stay > in the thrash folder. > > Running dovecot version 2.3.4.1 (f79e8e7e4) > > When i 'move' messages to the Trash folder they seem to stay there but > when i delete them they usually come back. > > Alex > > On 12/3/21 5:53 PM, Claudio Corvino wrote: >> >> I forgot to mention that sometimes users receive duplicate messages >> and Dovecot log: >> >> Dec 3 10:16:12 xxx dovecot: >> lmtp(xxx@xxx)<13468><OOFDAlXgqWGcNAAAIQnY6g:12>: Warning: >> /mnt/mail-storage-lv0007/xxx/Maildir/dovecot-uidlist: Duplicate file >> entry at line 2072: 1638522075.M489729P12338.xxx,S=5854,W=5943 (uid >> 71164 -> 71166) >> >> Thanks >> >> Regars >> >> On 03/12/21 17:50, Claudio Corvino wrote: >>> >>> Hi, >>> >>> I have two IMAP/LMTP Dovecot server in replica (version 2.3.4.1), I >>> use LDAP/AD for /userdb, /replica is working, but sometimes I get >>> these errors into log: >>> >>> Dec 3 15:47:15 xxx dovecot: imap(xxx)<28251><TOSxmj7SPRYloY5/>: >>> Warning: Maildir /mnt/mail-storage-lv0007/xxx/Maildir: Expunged >>> message reappeared, giving a new UID (old uid=233140, >>> file=1638540323.M588041P27708.xxx,S=84376,W=85507:2,) >>> >>> The user delete the message and then the message reappears into mail >>> client after one second. >>> >>> Does anybody knows how can I fix it? >>> >>> Thanks in advance >>> >>> Regards >>> >>

2 3

how to delete attachment and replace some words in subject
by lujie 05 Jan '22

05 Jan '22

hi, all, I need to filter email as follow rules: 1, delete the attachments; 2, replace some word in subject with code; 3, redirect to other email with the modified subject and original text in body. sieve and exrprograms used in my script. But error in run sieve script while try to set body text , which contains invalid character "cr lf". Thanks. -- Best Regards, Jessica

2 1

Doveadm auth fails
by Ken Wright 05 Jan '22

05 Jan '22

I'm still troubleshooting a faulty email server, and got the following results when I tried doveadm: kwright@grace:/etc/dovecot/conf.d$ doveadm auth lookup me(a)mydomain.com Error: auth-master: passdb lookup(me(a)mydomain.com): Auth PASS lookup failed Error: passdb lookup failed for me(a)mydomain.com kwright@grace:/etc/dovecot/conf.d$ doveadm auth test me(a)mydomain.com Password: Error: auth-client: conn unix:/var/run/dovecot/auth-client: connect(/var/run/dovecot/auth-client) failed: Permission denied (euid=1000(kwright) egid=1000(kwright) missing +r perm: /var/run/dovecot/auth-client, dir owned by 0:0 mode=0755) kwright@grace:/etc/dovecot/conf.d$ ls -la /var/run/dovecot/auth-client srw------- 1 dovecot root 0 Jan 4 19:09 /var/run/dovecot/auth-client I see /var/run/dovecot/auth-client only has read and write permissions for the owner and nothing for anyone else. Is this part of my problem? Ken

2 3

Re: Error: fts_solr: received invalid uid
by oliver.krone＠snoog.ch 04 Jan '22

04 Jan '22

Here is what solr sends to dovecot, the offending uid in this exmaple is '21' { "responseHeader":{ "status":0, "QTime":1, "params":{ "q":"body:Zeitserver"}}, "response":{"numFound":1,"start":0,"numFoundExact":true,"docs":[ { "uid":[21], "box":["2e60f3054059c95fbf580600eb1947e0"], "user":["oliver.krone(a)snoog.ch"], "id":"21/2e60f3054059c95fbf580600eb1947e0/oliver.krone(a)snoog.ch", "body":[" ... "], "hdr":[" ... "], "from":["..."], "subject":["..."], "to":["..."], "_version_":1720682332306800640}] }} Oliver >> I'm using dovecot 2.3.13,? solr 8.x. and roundcube 1.5.1. However when >> I do a search I get the the Error: fts_solr: received invalid uid, >> search results are ok. >> >> Thanks > Presumably one of the uid returned from solr could not be decoded (i.e. > converted to an int). The offending uid should have been printed as > part > of the message. If you need to get more info you could investigate what > is being returned by solr running the exact same query from a browser > if > you're able to retrieve it from the solr log. > > Alternatively you could set rawlog_dir in the fts_solr dovecot settings > and then look at what is being sent back from solr in the .in file that > is logged. > > https://doc.dovecot.org/settings/plugin/fts-solr-plugin/?highlight=fts%20do… > > John

3 2

Client Passdb out
by Ken Wright 03 Jan '22

03 Jan '22

I've been trying to log into Dovecot without success, and this is what I found in /var/log/mail.log: Jan 3 02:47:33 grace dovecot: auth: Debug: client passdb out: FAIL#0111#011user=me(a)mydomain.com Jan 3 02:47:33 grace dovecot: imap-login: Disconnected (auth failed, 1 attempts in 6 secs): user=<me(a)mydomain.com>, method=PLAIN, rip=192.168.1.1, lip=192.168.1.10, TLS, session=<bgBsu6jUhqzAqAEB> I know I provided the correct password, but I'm still having no joy. Ken

2 1

Re: Error: fts_solr: received invalid uid (John Fawcett)
by oliver.krone＠snoog.ch 03 Jan '22

03 Jan '22

Hi John, You are right this was not a dovecot solr query. It is really strange everything seems to work with Dovecot 2.3.4. E.g. search and rebuilding index from scratch using doveadm. As soon as I use version 2.3.13 things are getting wild: dovecot crashed when I re-scan the index using doveadm and search does not work anymore, after re-scan: Panic: file http-client-request.c: line 1240 (http_client_request_send_more): assertion failed: (req->payload_input != NULL) doveadm(krone(a)invectrix.ch): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7fc54cace4e2] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7fc54cace5fe] -> /usr/lib/dovecot/libdovecot.so.0(+0xfc49b) [0x7fc54cada49b] -> /usr/lib/dovecot/libdovecot.so.0(+0xfc4d1) [0x7fc54cada4d1] -> /usr/lib/dovecot/libdovecot.so.0(+0x53aee) [0x7fc54ca31aee] -> /usr/lib/dovecot/libdovecot.so.0(+0x4aec2) [0x7fc54ca28ec2] -> /usr/lib/dovecot/libdovecot.so.0(http_client_connection_output+0xee) [0x7fc54ca7ebde] -> /usr/lib/dovecot/libdovecot.so.0(+0x122171) [0x7fc54cb00171] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7fc54caeff59] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x132) [0x7fc54caf1592] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x50) [0x7fc54caf0000] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7fc54caf01c0] -> /usr/lib/dovecot/libdovecot.so.0(+0x9c4cd) [0x7fc54ca7a4cd] -> /usr/lib/dovecot/libdovecot.so.0(http_client_request_finish_payload+0x2c) [0x7fc54ca7a6dc] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0xf243) [0x7fc54c0a6243] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(fts_parser_more+0x25) [0x7fc54c0a5345] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0xbfcf) [0x7fc54c0a2fcf] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(fts_build_mail+0xa27) [0x7fc54c0a3a87] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0x11f0b) [0x7fc54c0a8f0b] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_precache+0x2e) [0x7fc54cbf14ae] -> doveadm(+0x3761f) [0x55d18bdbf61f] -> doveadm(+0x31bad) [0x55d18bdb9bad] -> doveadm(+0x32860) [0x55d18bdba860] -> doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x22d) [0x55d18bdbb4ad] -> doveadm(doveadm_cmd_run_ver2+0x4c8) [0x55d18bdcbb88] -> doveadm(doveadm_cmd_try_run_ver2+0x3a) [0x55d18bdcbbda] -> doveadm(main+0x1d0) [0x55d18bdaa450] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea) [0x7fc54c69fd0a] -> doveadm(_start+0x2a) [0x55d18bdaa92a] and solr: 2022-01-03 00:13:20.829 ERROR (qtp1991278377-21) [ x:dovecot] o.a.s.s.HttpSolrCall null:[com.ctc.wstx.exc.WstxLazyException] com.ctc.wstx.exc.WstxIOException: Early EOF .... Caused by: org.eclipse.jetty.io.EofException: Early EOF at org.eclipse.jetty.server.HttpInput$3.getError(HttpInput.java:1143) at org.eclipse.jetty.server.HttpInput$3.noContent(HttpInput.java:1131) at org.eclipse.jetty.server.HttpInput.read(HttpInput.java:318) Seems like dovecot is sending an empty query? Oliver > > Hi Oliver > > unless I'm missing something that doesn't look like the type of query > dovecot launches - dovecot sends various parameters including the > request for xml results. The thing that looks odd to me is that the > results fields should be single values not arrays enclosed in [], ie I > would have expected > > "uid":21, > > instead of > > "uid":[21], > > I'd be interested to see the equivalent xml output produced by running > a > query that dovecot sends. > > John >

2 2

Can't connect to database
by Ken Wright 03 Jan '22

03 Jan '22

Dovecot has been giving me problems for the past week or so. Today the error log showed me this: Jan 2 13:33:39 grace dovecot: auth-worker(3250): Error: mysql(localhost): Connect failed to database (postfix): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) - waiting for 5 seconds before retry The socket is there, showing full permissions (rwx for owner, group, and rest of the universe) so I can't understand why dovecot can't connect. Is there anyone who can help? Ken

3 3

master: service(imap): child xxxx killed with signal 11
by Lukas Matasovsky 02 Jan '22

02 Jan '22

Dear Maintainer, I have several dovecot installations, all of them stopped working with the upgrade from .16 to .17. Maybe I am missing something, or it's a bug. All I can see is a signal 11 after each login attempt. Attached you can find a sysreport plus a core dump, both from different states of configuration (I reverted the core-dump settings later on) of the same server, but the effect has been the same ever since upgrading. I have other servers that use pam (not mariadb) and local maildirs that show the same behavior. For now, I have downgraded all servers, if needed I could run some more tests. Thank you for checking & cheers, Lukas

2 3

Dovecot Docker Image Volumes
by Thomas Bellebaum 02 Jan '22

02 Jan '22

Hello there and happy new year, I have a question/request regarding the Docker Image hosted at https://hub.docker.com/r/dovecot/dovecot. The Dockerfile itself declares two volumes: - `/etc/dovecot` for configuration data - `/srv/mail` for mail storage It seems inconvenient in some cases to have the image create these volumes, especially in case of the former. Consider a minimal Dockerfile like the following: ``` FROM dovecot/dovecot:latest COPY dovecot.conf /etc/dovecot/dovecot.conf ``` This creates a new image building on top of the official one, which has statically configured configuration, and thus does not need to save its config in a volume. Yet currently, since the base image exports volumes, a config volume is created. A user might also choose to save mail in a different directory or even in a remote SQL database, rendering the second volume unnecessary. I would like to know a bit about the reasons for declaring the volumes, and suggest removing the line, should this be an option. Some impact considerations: - Removing the volumes for future image versions will not impact existing deployments building on tags other than `latest`. - As the default (example) configuration is not very useful for non-test-setups, most people have probably assigned the config volume explicitly, e.g. using docker's `-v` option. These people will also not be affected. - The description explicitly states to mount `/srv/mail/`, but some people might rely on the the automatic volume creation nonetheless. - Some obscure proprietary scripts may rely on the current behavior. In any case, if the volumes are no longer declared, the image description should mention that the mail storage location (the default being `/var/mail`) must be saved e.g. by using volumes, and probably also that the configuration is expected at `/etc/dovecot/dovecot.conf`. Stay healthy and have a nice day, -- Thomas Bellebaum <thomas(a)bellebaum.eu>

2 1

Permission denied
by Ken Wright 02 Jan '22

02 Jan '22

My server has been running just fine for over a year, until I upgraded PostfixAdmin and somehow messed things up. Now I can't log in, and my mail client (Evolution, if it matters) keeps popping up an authentication request. The server is Ubuntu 20.04, my Dovecot is version 2.3.7.2, and Evolution is 3.40.4-1. I've also tried logging in with Roundcube with no success. Any insight or suggestions will be gratefully received! Here's the most recent entry from /var/log/mail.err: Dec 28 22:05:02 grace dovecot: lmtp(me(a)mydomain.com)<910309><SOFiMl7Qy2Hl4w0AThsuZQ>: Error: lmtp- server: conn unix:pid=906625,uid=117 [6]: rcpt me(a)mydomain.com: Mailbox INBOX: open(/var/mail/vmail/me(a)mydomain.com/tmp/1640747102.M850878P910309.grac ) failed: Permission denied Any further information available upon request!

3 6

spf helo pass
by Benny Pedersen 02 Jan '22

02 Jan '22

would be nice to see added :=) talvi.dovecot.org txt "spfv1 a -all"

5 13

auth crashes when oauth2 passdb is enabled
by Sebastiano Degan 01 Jan '22

01 Jan '22

I've enabled both sql and oauth2 passdb, regardless of the method used by the client, I get the following error: Jan 1 15:38:56 mail dovecot[52828]: auth: Panic: file http-client.c: line 646 (http_client_context_close): assertion failed: (cctx->clients_list == NULL) Jan 1 15:38:56 mail dovecot[52826]: master: Error: service(auth): command startup failed, throttling for 2.000 secs Jan 1 15:38:56 mail dovecot[52828]: auth: Fatal: master: service(auth): child 52840 killed with signal 6 (core dumped) Jan 1 15:38:56 mail dovecot[52828]: imap-login: Disconnected: Auth process broken (disconnected before auth was ready, waited 0 secs): user=<>, rip=192.168.1.104, lip=192.168.1.101, TLS, session=<QW7rFYfUgcTAqAFo> If I remove the oauth2 passdb, there are no problems. This is the output of dovecot -n: # 2.3.17 (e2aa53df5b): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.17 (054dddfa) # OS: FreeBSD 13.0-RELEASE-p4 amd64 nullfs # Hostname: localhost auth_mechanisms = plain login oauthbearer xoauth2 default_internal_user = vmail first_valid_uid = 0 hostname = ***DELETED*** mail_location = maildir:/data/mailboxes/%d/%n mail_plugins = " fts fts_solr" mail_privileged_group = vmail 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 Archive { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { args = /usr/local/etc/dovecot/dovecot-oauth2.conf.ext driver = oauth2 mechanisms = xoauth2 oauthbearer } plugin { antispam_backend = pipe antispam_mail_notspam = learn_ham antispam_mail_sendmail = /usr/bin/rspamc antispam_mail_sendmail_args = -h;localhost:11334 antispam_mail_spam = learn_spam antispam_spam = Junk antispam_trash = Trash fts = solr fts_solr = url=http://localhost:8983/solr/dovecot sieve = ~/.dovecot.sieve sieve_before = /etc/dovecot/sieve/before.d sieve_dir = ~/sieve } postmaster_address = ***DELETED*** protocols = imap lmtp sieve pop3 service auth-worker { unix_listener auth-worker { user = vmail } } service auth { inet_listener { port = 1666 } unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } user = vmail } service imap-login { inet_listener imap { port = 0 } } service lmtp { inet_listener lmtp { port = 24 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } user = vmail } service pop3-login { inet_listener pop3 { port = 0 } } ssl = required ssl_cert = </usr/local/etc/letsencrypt/live/***DELETED***/fullchain.pem ssl_key = # hidden, use -P to show it userdb { args = uid=vmail gid=vmail home=/data/mailboxes/%d/%n driver = static } protocol lda { mail_plugins = " fts fts_solr sieve" } protocol imap { mail_plugins = " fts fts_solr imap_sieve" } protocol lmtp { mail_plugins = " fts fts_solr sieve" postmaster_address = ***DELETED*** }

1 0

Add arm64 support to docker image
by alpe 01 Jan '22

01 Jan '22

I think the issue is here: ADD https://github.com/krallin/tini/releases/download/v0.19.0/tini /sbin/tini # buildkit tini has arm64 (and others) version. So it should be easy to make the container work with arm.

1 0

How to set LMTP over TLS for incoming emails in exim and dovecot
by Zakaria 01 Jan '22

01 Jan '22

1 0

cumulative resource limit exceeded
by Mats Mellstrand 31 Dec '21

31 Dec '21

Hi I’m running dovecot-2.3.15 and dovecot-pigeonhole-0.5.15 on FreeBSD 13 To day i suddenly get errors in my personal logfile (.dovecot.sieve.log) sieve: info: started log at Dec 29 20:26:42. .dovecot: error: cumulative resource usage limit exceeded. Is there anything I can do about this error? /mm

3 2

modernizing dovecot.conf
by Laura Steynes 30 Dec '21

30 Dec '21

Happy Holidays, And if you like me are working throughout so more senior engineers get their holidays, my condolences hah Taking the time to bring our dovecot.conf into the 2021/22 era .since its quiet time of year, Do I read it right that where we have things like service imap { process_limit = 1024 executable = imap imap-postlogin are not needed now ? and process limit is a global option? things like pop3/imap_client_workarounds = fooy are now global options, not to be in protocol { } sections ? I am reading the example conf files and see these outside the protocol sections where they have in the past lived, this is what makes me think they are now global and not needed in sub sections. but I may be missing some linking going from file to file , we have forever updated our single config file, just fixing whatever breaks when major versions break something, easier to find options in one file, rather than trying to sift through 40 included files like I am looking at now :-)

4 7

Six failed tests on openindiana (Opensolaris derivative)
by Friedrich Kink 29 Dec '21

29 Dec '21

Hi all, I'm new to this list, so please forgive me if I violate netiquette (and let me know how to improve, because it is not at all my intent). I want to create two packages (dovecot and dovecot-2.3-pigeonhole) hosted by openindiana.org. First of all, everything compiles fine and works as expected, but (there is always a but ;-)) 6 out of 41540 tests failed. To build a clean package I'd like to understand the nature of the failed tests and even more would like to fix the tests. I tried to find some hints how to tackle down the issue but was not successful so far. dovecot version 2.3.17.1, gcc version (OpenIndiana 7.5.0-il-0) 7.5.0 configure options: --sysconfdir=/etc \ --with-gssapi=plugin \ --with-ldap=plugin \ --with-sql=plugin \ --with-lua=plugin \ --with-ssl=openssl \ --with-sodium \ --with-mysql \ --with-pgsql failed tests: array_free ........................................................... : ok $(SOURCE_DIR)/src/lib/test-backtrace.c:21: Assert failed: strstr(str_c(bt), "main") != NULL backtrace_append ..................................................... : FAILED $(SOURCE_DIR)/src/lib/test-backtrace.c:45: Assert failed: strstr(bt, "main") != NULL backtrace_get ........................................................ : FAILED base32_encode() with padding ......................................... : ok buffer_replace() ..................................................... : ok $(SOURCE_DIR)/src/lib/test-buffer-istream.c:55: Assert failed: buffer_append_full_file(result, TEST_FILENAME, SIZE_MAX, &error) == BUFFER_APPEND_READ_ERROR $(SOURCE_DIR)/src/lib/test-buffer-istream.c:56: Assert failed: error != NULL && *error != '\0' buffer_append_full_file .............................................. : FAILED buffer_append_full_istream ........................................... : ok connection idle kill ................................................. : ok $(SOURCE_DIR)/src/lib/test-connection.c:563: Assert failed: !received_quit $(SOURCE_DIR)/src/lib/test-connection.c:563: Assert failed: !received_quit connection handshake failed (version) ................................ : FAILED connection handshake failed (handshake_args) ......................... : ok file_cache_switch_fd ................................................. : ok $(SOURCE_DIR)/src/lib-test/test-common.c:245: Assert failed: suppress == TRUE Error: fstat(.test_file_cache) failed: Bad file number $(SOURCE_DIR)/src/lib-test/test-common.c:245: Assert failed: suppress == TRUE Error: mmap_anon(.test_file_cache, 4096) failed: Not enough space $(SOURCE_DIR)/src/lib-test/test-common.c:245: Assert failed: suppress == TRUE Error: mremap_anon(.test_file_cache, 8192) failed: Not enough space file_cache_errors .................................................... : FAILED file_create_locked() ................................................. : ok ostream file send istream file ....................................... : ok $(SOURCE_DIR)/src/lib/test-ostream-file.c:172: Assert failed: input2->v_offset == 10 $(SOURCE_DIR)/src/lib/test-ostream-file.c:173: Assert failed: output->offset == 14 ostream file send istream sendfile() ................................. : FAILED ostream multiplex (simple) ........................................... : ok Again, compilation works clean without any warning. If you could provide some hints how to start would be great. I know I'm kind of inch picker but want to provide best experience to possible users and not give any chance to complain back to dovecot community. kind regards, Fritz

2 1

dovecot panic
by tobisworld＠gmail.com 27 Dec '21

27 Dec '21

Hi list since today I receive dovecot panics in my mail logs, whenever I want to access on my inbox in my mailclient (evolution) Details: dovecot --version 2.3.17.1 (476cd46418) Centos 7 (latest updates) x86 architecture mailbox stored in NFS > Panic: file mail-index-transaction-finish.c: line 185 (mail_index_transaction_get_uid): assertion failed: (seq <= t->view- >map->hdr.messages_count) > Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7fb86f592142] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7fb86f59224e] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf72fe) [0x7fb86f5a02fe] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf73a1) [0x7fb86f5a03a1] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fb86f4eee38] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xf438d) [0x7fb86f95b38d] - > /usr/lib64/dovecot/libdovecot-storage.so.0(+0xf43da) [0x7fb86f95b3da] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_index_transaction_finish+0x177) [0x7fb86f95ba87] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xf9ad6) [0x7fb86f960ad6] - > /usr/lib64/dovecot/libdovecot- storage.so.0(mail_index_transaction_commit_full+0x9d) [0x7fb86f960fad] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_index_transaction_commit+0x1c) [0x7fb86f96106c] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_cache_set_seq_corrupted_reason+0x61) [0x7fb86f94a921] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_set_mail_cache_corrupted+0xed) [0x7fb86f8b9bbd] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x7a3e9) [0x7fb86f8e13e9] - > /usr/lib64/dovecot/libdovecot-storage.so.0(+0x7a6b0) [0x7fb86f8e16b0] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_get_physical_size+0x38) [0x7fb86f8a6ba8] -> /usr/libexec/dovecot//lib20_mail_log_plugin.so(+0x2465) [0x7fb86e49b465] -> /usr/libexec/dovecot//lib15_notify_plugin.so(notify_contexts_mail_copy+ 0x5c) [0x7fb86e69f3ec] -> /usr/libexec/dovecot//lib15_notify_plugin.so(+0x25d4) [0x7fb86e6a05d4] -> /usr/libexec/dovecot//lib10_quota_plugin.so(+0x102ae) [0x7fb86eab72ae] -> /usr/libexec/dovecot//lib01_acl_plugin.so(+0xef3e) [0x7fb86eccef3e] -> /usr/lib64/dovecot/libdovecot- storage.so.0(+0x50c4c) [0x7fb86f8b7c4c] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_move+0x58) [0x7fb86f8b7ec8] -> dovecot/imap(+0x1175b) [0x55a2b1a5375b] -> dovecot/imap(command_exec+0x64) [0x55a2b1a61f04] -> dovecot/imap(+0x1dde2) [0x55a2b1a5fde2] -> dovecot/imap(+0x1de71) [0x55a2b1a5fe71] -> dovecot/imap(+0x1e039) [0x55a2b1a60039] -> dovecot/imap(client_handle_input+0x205) [0x55a2b1a602f5] -> dovecot/imap(client_input+0x79) [0x55a2b1a608d9] I attached output from dovecot-sysreport here to this report Best regards tobi

1 1

Re: Dovecot does not start on MacOS 12.01
by Steven Smith 19 Dec '21

19 Dec '21

Re: https://www.mail-archive.com/dovecot@dovecot.org/msg84784.html <https://www.mail-archive.com/dovecot@dovecot.org/msg84784.html> I just upgraded to macOS 12.1, ran into this issue, and discovered this thread from the error message. Is there a viable workaround or patch yet? I tried the workaround in this thread, and still see these issues. Set default_vsz_limit = 0 in ./conf.d/10-master.conf. Observe that: dovecot now launches without the setrlimit(RLIMIT_DATA, 268435456) error at the command line However, the mail-err.log is still filled with these errors (below), perhaps for the child processes. Steve > Dec 19 11:22:06 imap-login: Error: Dec 19 11:22:06 service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid argument > Dec 19 11:22:06 imap-login: Error: Dec 19 11:22:06 service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid argument > Dec 19 11:22:06 imap-login: Error: Dec 19 11:22:06 service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid argument > Dec 19 11:22:06 imap-login: Error: Dec 19 11:22:06 service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid argument > Dec 19 11:22:06 imap-login: Error: Dec 19 11:22:06 service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid argument > Dec 19 11:22:06 imap-login: Fatal: master: service(imap-login): child 4629 returned error 89 (Fatal failure) > Dec 19 11:22:06 master: Error: service(imap-login): command startup failed, throttling for 2.000 secs > Dec 19 11:22:06 imap-login: Fatal: master: service(imap-login): child 4630 returned error 89 (Fatal failure) > Dec 19 11:22:06 imap-login: Fatal: master: service(imap-login): child 4628 returned error 89 (Fatal failure) > Dec 19 11:22:06 imap-login: Fatal: master: service(imap-login): child 4627 returned error 89 (Fatal failure) > Dec 19 11:22:06 imap-login: Fatal: master: service(imap-login): child 4619 returned error 89 (Fatal failure) > Dec 19 11:22:06 imap-login: Error: Dec 19 11:22:06 service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid argument > Dec 19 11:22:06 imap-login: Fatal: master: service(imap-login): child 4631 returned error 89 (Fatal failure) > Dec 19 11:22:09 imap-login: Error: Dec 19 11:22:09 service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid argument > Dec 19 11:22:09 imap-login: Fatal: master: service(imap-login): child 4638 returned error 89 (Fatal failure) > Dec 19 11:22:09 master: Error: service(imap-login): command startup failed, throttling for 4.000 secs > On Mon, 1 Nov 2021 14:55:25 +0200, Aki Tuomi said: > > I think this is happening because MacOS no longer supports RLIMIT_DATA. We'll > try to look into this. default_vsz_limit = 0 seems good enough workaround. > Aki

1 2

Undefined symbol using fts-flatcurve with repo.dovecot.org packages
by Mike Acar 18 Dec '21

18 Dec '21

Hi, I'm trying to use dovecot-fts-flatcurve with dovecot 2:2.3.15-1+debian10 from repo.dovecot.org, but it looks like the package doesn't include ICU, which fts-flatcurve requires. After compilation and installation, I get an error from doveadm: doveadm fts-flatcurve stats -u user INBOX Fatal: Couldn't load required plugin /usr/lib/dovecot/modules/lib21_fts_flatcurve_plugin.so: dlopen() failed: /usr/lib/dovecot/modules/lib21_fts_flatcurve_plugin.so: undefined symbol: _ZTIN6icu_638ByteSinkE Unmangled, I think that's this symbol: U typeinfo for icu_63::ByteSink I checked the rules file from dovecot_2.3.15-1%2Bdebian10.debian.tar.xz and it appears that configure doesn't include --with-icu. Is there a plan to include this in a future release? -- | Mike Acar | | mike at waspfactory dot org |

1 0

Re: Re: invalid vsize-hdr
by Станислав Дырив 17 Dec '21

17 Dec '21

it helps for me (dovecot 2.2.36 @ centos7): #delete index files: find /path/to/user/maildir/ -type f -name dovecot.index* -delete find /path/to/user/maildir/ -type f -name dovecot-uidlist -delete #then re-create index by command: doveadm force-resync -u "user(a)domain.com" '*'

1 0

Can dovecot be leveraged to exploit Solr/Log4shell?
by Joseph Tam 15 Dec '21

15 Dec '21

I'm surprised I haven't seen this mentioned yet. An internet red alert went out Friday on a new zero-day exploit. It is an input validation problem where Java's Log4j module can be instructed via a specially crafted string to fetch and execute code from a remote LDAP server. It has been designated the Log4shell exploit (CVE-2021-44228). Although I don't use it, I immediately thought of Solr, which provides some dovecot installations with search indexing. Can dovecot be made to pass on arbitrary loggable strings to affected versions of Solr (7.4.0-7.7.3, 8.0.0-8.11.0)? Those running Solr to implement Dovecot FTS should look at https://solr.apache.org/security.html#apache-solr-affected-by-apache-log4j-… Joseph Tam <jtam.home(a)gmail.com>

6 8

quota warnings not sent out anymore
by mj 15 Dec '21

15 Dec '21

Hi, We suddenly realised that our maildir quota warnings are no longer sent out. We don't understand why not. This is dovecot 2.3.4.1 on debian 10.11. We use a script to send out the notification, adapted from the dovecot wiki here: (https://doc.dovecot.org/configuration_manual/quota/) Our quota notification script is: > #!/bin/sh > PERCENT=$1 > USER=$2 > cat << EOF | /usr/lib/dovecot/dovecot-lda -d $USER -o "plugin/quota=maildir::noenforcing" > From: noreply(a)domain.com > Subject: quota warning > > Your mailbox is now $PERCENT% full. > > Please delete or archive items to decrease your mailbox size. Our complete doveconf -n output is at the end of this email. When calling the script manually as user root, it works perfectly. But as user vmail or dovecot, no notifications are sent at all. I guess this is relevant: > root@dovecot:/etc/dovecot# ls -l /var/run/dovecot/ > total 8 > srw------- 1 root root 0 Dec 6 00:00 anvil > srw------- 1 root root 0 Dec 6 00:00 anvil-auth-penalty > srw------- 1 dovecot root 0 Dec 6 11:34 auth-client > srw------- 1 dovecot root 0 Dec 6 11:34 auth-login > srw------- 1 root root 0 Dec 6 11:34 auth-master > -rw------- 1 root root 32 Jul 19 17:39 auth-token-secret.dat > srw-rw-rw- 1 vmail vmail 0 Dec 6 11:34 auth-userdb > srw------- 1 dovecot root 0 Dec 6 11:34 auth-worker > srw------- 1 root root 0 Dec 6 11:34 config > srw-rw---- 1 root dovecot 0 Dec 6 11:34 dict > srw-rw---- 1 root dovecot 0 Dec 6 11:34 dict-async > srw------- 1 root root 0 Dec 6 11:34 director-admin > srw-rw-rw- 1 root root 0 Dec 6 11:34 dns-client > srw------- 1 root root 0 Dec 6 11:34 doveadm-server > lrwxrwxrwx 1 root root 25 Dec 6 00:00 dovecot.conf -> /etc/dovecot/dovecot.conf > drwxr-xr-x 2 root root 40 Jul 19 17:39 empty > srw-rw---- 1 root dovecot 0 Dec 6 11:34 imap-hibernate > srw------- 1 root root 0 Dec 6 11:34 imap-master > srw-rw-rw- 1 root root 0 Dec 6 11:34 imap-urlauth > srw------- 1 dovecot root 0 Dec 6 11:34 imap-urlauth-worker > srw-rw-rw- 1 root root 0 Dec 6 11:34 indexer > srw------- 1 dovecot root 0 Dec 6 11:34 indexer-worker > srw------- 1 dovecot root 0 Dec 6 11:34 ipc > srw-rw-rw- 1 root root 0 Dec 6 11:34 lmtp > srw------- 1 root root 0 Dec 6 11:34 log-errors > drwxr-x--- 2 root nogroup 120 Dec 6 11:34 login > srw------- 1 root root 0 Dec 6 11:34 master > -rw------- 1 root root 6 Dec 6 00:00 master.pid > srw------- 1 root root 0 Dec 6 11:34 old-stats > prw------- 1 root root 0 Dec 6 11:34 old-stats-mail > prw------- 1 root root 0 Dec 6 11:34 old-stats-user > srw------- 1 vmail root 0 Dec 6 11:34 quota-warning > srw------- 1 root root 0 Dec 6 11:34 replication-notify > prw------- 1 root root 0 Dec 6 11:34 replication-notify-fifo > srw------- 1 dovecot root 0 Dec 6 11:34 replicator > srw-rw---- 1 vmail vmail 0 Dec 6 11:34 stats-reader > srw-rw---- 1 vmail vmail 0 Dec 6 11:34 stats-writer > drwxr-x--- 2 root nogroup 80 Dec 6 11:34 token-login Can anyone help, and explain what is going on here? Thank you very much in advance for a reply! MJ The doveconf -n output: > root@imap:/etc/dovecot# doveconf -n > # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.5.4 () > # OS: Linux 4.19.0-17-amd64 x86_64 Debian 10.11 xfs > # Hostname: mail.company.com > auth_debug = yes > auth_failure_delay = 10 secs > auth_master_user_separator = * > auth_mechanisms = plain login > auth_username_format = %Ln > auth_verbose = yes > auth_verbose_passwords = sha1 > default_vsz_limit = 512 M > deliver_log_format = %f | %s | msgid=%m: %$ > lda_mailbox_autocreate = yes > lda_mailbox_autosubscribe = yes > login_greeting = Dovecot ready. > login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c lport=%a > mail_gid = vmail > mail_location = maildir:/var/vmail/%Ln/Maildir:LAYOUT=fs:DIRNAME=mAildir > mail_plugins = acl lazy_expunge zlib quota mail_log notify > mail_shared_explicit_inbox = yes > mail_uid = vmail > 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 ihave > namespace { > list = children > location = maildir:/var/vmail/%%u/Maildir:LAYOUT=fs:DIRNAME=mAildir:INDEX=/var/vmail/%u/shared/%%u > prefix = shared/%%n/ > separator = / > subscriptions = no > type = shared > } > namespace inbox { > inbox = yes > location = > mailbox "Deleted items" { > special_use = \Trash > } > mailbox Drafts { > special_use = \Drafts > } > mailbox Junk { > special_use = \Junk > } > mailbox Sent { > special_use = \Sent > } > mailbox "Sent items" { > special_use = \Sent > } > mailbox Trash { > special_use = \Trash > } > mailbox inbox { > auto = subscribe > } > prefix = > separator = / > type = private > } > passdb { > args = /etc/dovecot/deny.imap > deny = yes > driver = passwd-file > } > passdb { > args = /etc/dovecot/master-users > driver = passwd-file > master = yes > } > passdb { > args = /etc/dovecot/dovecot-ldap.conf.ext > driver = ldap > result_failure = return-fail > } > plugin { > acl = vfile > acl_shared_dict = file:/var/lib/dovecot/db/shared-mailboxes.db > mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename append > mail_log_fields = uid box msgid from subject > quota = maildir > quota_rule = ?:storage=5G > quota_rule2 = Trash:storage=+100M > quota_warning = storage=97%% quota-warning 97 %u > quota_warning2 = storage=95%% quota-warning 95 %u > quota_warning3 = storage=90%% quota-warning 90 %u > quota_warning4 = storage=85%% quota-warning 85 %u > quota_warning5 = storage=80%% quota-warning 80 %u > quota_warning6 = -storage=100%% quota-warning below %u > sieve = ~/.dovecot.sieve > sieve_default = /var/lib/dovecot/default.sieve > sieve_dir = ~/sieve > } > protocols = imap lmtp sieve > service auth { > unix_listener /var/spool/postfix/private/auth { > mode = 0666 > } > unix_listener auth-userdb { > group = vmail > mode = 0666 > user = vmail > } > } > service imap-login { > process_limit = 500 > process_min_avail = 2 > } > service quota-warning { > executable = script /usr/local/bin/quota-warning.sh > unix_listener quota-warning { > user = vmail > } > user = dovecot > } > service stats { > unix_listener stats-reader { > group = vmail > mode = 0660 > user = vmail > } > unix_listener stats-writer { > group = vmail > mode = 0660 > user = vmail > } > } > shutdown_clients = no > ssl = required > ssl_cert = </etc/ssl/letsencrypt/fullchain.pem > ssl_cipher_list = ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384 > ssl_dh = # hidden, use -P to show it > ssl_key = # hidden, use -P to show it > ssl_min_protocol = TLSv1.2 > userdb { > args = uid=vmail gid=vmail home=/var/vmail/%n allow_all_users=yes > driver = static > } > userdb { > args = /etc/dovecot/dovecot-ldap.conf.ext > driver = ldap > } > verbose_proctitle = yes > protocol lda { > mail_plugins = acl lazy_expunge zlib quota mail_log notify sieve quota > } > protocol imap { > imap_max_line_length = 2 M > mail_max_userip_connections = 40 > mail_plugins = acl lazy_expunge zlib quota mail_log notify imap_quota imap_acl > }

2 5

dovecot-2.3.17: "Panic: file ioloop.c: line 865"
by Piper Andreas 14 Dec '21

14 Dec '21

Hello, since the upgrade from dovecot-2.3.16 to 2.3.17 I get 'Panic'-errors in the system-log of my replicator hosts. See below for log messages, doveconf-output and gdb-backtrace. Storage filesystem is ZFS. The error seems to be correlated with exactly one user-mailbox, this user is repeatedly noted as 'failed' in replication status, although replication of this mailbox seems to work, as the mailbox status shows always the identical size on both replicators. The error can be produced by forcing replication of this individual mailbox. Is there anything I can do to repair this mailbox? Thanks for any hints, Andreas Example log-messages: Nov 11 07:17:50 vhrz311 dovecot: doveadm(119455): Error: write(<local>) failed: Timed out after 60 seconds Nov 11 07:17:50 vhrz311 dovecot: doveadm(119455): Panic: file ioloop.c: line 865 (io_loop_destroy): assertion failed: (ioloop == cur rent_ioloop) Nov 11 07:17:50 vhrz311 dovecot: doveadm(119455): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7 f4e59419182] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f4e5941929e] -> /usr/lib/dovecot/libdovecot.so.0(+0xf8a5e) [0x7f4e59427a5e] -> /usr/lib/dovecot/libdovecot.so.0(+0xf8b01) [0x7f4e59427b01] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f 4e593744a7] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_destroy+0x2dc) [0x7f4e5944121c] -> dovecot/doveadm-server(+0x46fb6) [0x563d0 150ffb6] -> dovecot/doveadm-server(doveadm_print+0x27) [0x563d01508fb7] -> dovecot/doveadm-server(+0x2b427) [0x563d014f4427] -> dove cot/doveadm-server(+0x2da44) [0x563d014f6a44] -> dovecot/doveadm-server(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x2cf) [0x563d014f7c6f] -> dovecot/doveadm-server(doveadm_cmd_run_ver2+0x43b) [0x563d01508c1b] -> dovecot/doveadm-server(+0x44612) [0x563d0150d612] -> /usr /lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7f4e594406d9] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal +0x134) [0x7f4e59442034] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x50) [0x7f4e594407e0] -> /usr/lib/dovecot/libdovec ot.so.0(io_loop_run+0x38) [0x7f4e59440a18] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f4e593a6a23] -> dovecot/ doveadm-server(main+0x102) [0x563d014e6922] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f4e58bc1bf7] -> dovecot/d oveadm-server(_start+0x2a) [0x563d014e69aa] Nov 11 07:17:50 vhrz311 dovecot: doveadm(119455): Fatal: master: service(doveadm): child 119455 killed with signal 6 (core dumped) 'doveconf -n': # 2.3.17 (e2aa53df5b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.17 (054dddfa) # OS: Linux 4.15.0-162-generic x86_64 Ubuntu 18.04.6 LTS # Hostname: vhrz311.HRZ.Uni-Marburg.DE auth_cache_negative_ttl = 0 auth_cache_size = 10 M auth_master_user_separator = * auth_worker_max_count = 1024 base_dir = /var/run/dovecot/ default_client_limit = 10000 default_vsz_limit = 6 G doveadm_password = # hidden, use -P to show it doveadm_port = 12345 first_valid_gid = 10000 first_valid_uid = 10000 imap_max_line_length = 640 k last_valid_gid = 10000 last_valid_uid = 10000 mail_attribute_dict = file:%h/mdbox/dovecot-attributes mail_gid = 10000 mail_location = mdbox:%h/mdbox mail_plugins = " mail_log notify zlib notify replication" mail_privileged_group = mail mail_uid = 10000 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 { hidden = no inbox = yes list = yes location = prefix = separator = / subscriptions = yes type = private } passdb { args = /etc/dovecot.deny deny = yes driver = passwd-file } passdb { args = /etc/dovecot/private/passwd.masterusers driver = passwd-file master = yes } passdb { args = /etc/dovecot/dovecot-ldap.hrz.conf.ext driver = ldap name = passdb_ldap_hrz } passdb { args = /etc/dovecot/dovecot-ldap.staff.conf.ext driver = ldap name = passdb_ldap_staff } passdb { args = /etc/dovecot/dovecot-ldap.students.conf.ext driver = ldap name = passdb_ldap_students } plugin { mail_replica = tcp:172.25.1.95 sieve = file:~/sieve;active=~/.dovecot.sieve sieve_default = /var/lib/dovecot/default.sieve sieve_max_actions = 55 sieve_max_redirects = 50 } pop3_uidl_format = %08Xv%08Xu postmaster_address = postmaster(a)hrz.uni-marburg.de protocols = imap pop3 lmtp sieve replication_dsync_parameters = -d -n INBOX -l 30 -U replication_max_conns = 20 service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service auth-worker { user = $default_internal_user } service auth { client_limit = 10000 } service config { process_min_avail = 8 } service doveadm { inet_listener { port = 12345 } vsz_limit = 6 G } service imap-login { process_min_avail = 64 service_count = 0 } service imap { process_limit = 8192 } service lmtp { inet_listener lmtp { port = 24 } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 8 service_count = 0 } service pop3-login { process_min_avail = 8 service_count = 0 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } } service submission-login { service_count = 0 } ssl = required ssl_ca = </etc/ssl/certs/umr-chain.pem ssl_cert = </etc/ssl/certs/vhrz311.hrz.uni-marburg.de.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_require_crl = no userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf.ext driver = ldap name = userdb_ldap } protocol imap { imap_metadata = yes mail_max_userip_connections = 25 mail_plugins = " mail_log notify zlib notify replication imap_zlib" } protocol lmtp { mail_plugins = " mail_log notify zlib notify replication sieve" } gdb: gdb /usr/lib/dovecot/doveadm-server /var/vmail/system-cores/core GNU gdb (Ubuntu 8.1.1-0ubuntu1) 8.1.1 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/lib/dovecot/doveadm-server...(no debugging symbols found)...done. [New LWP 119455] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `dovecot/doveadm-server'. Program terminated with signal SIGABRT, Aborted. #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 51 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x00007f4e58be0921 in __GI_abort () at abort.c:79 #2 0x00007f4e59427a11 in ?? () from /usr/lib/dovecot/libdovecot.so.0 #3 0x00007f4e59427b01 in ?? () from /usr/lib/dovecot/libdovecot.so.0 #4 0x00007f4e593744a7 in i_panic () from /usr/lib/dovecot/libdovecot.so.0 #5 0x00007f4e5944121c in io_loop_destroy () from /usr/lib/dovecot/libdovecot.so.0 #6 0x0000563d0150ffb6 in ?? () #7 0x0000563d01508fb7 in doveadm_print () #8 0x0000563d014f4427 in ?? () #9 0x0000563d014f6a44 in ?? () #10 0x0000563d014f7c6f in doveadm_cmd_ver2_to_mail_cmd_wrapper () #11 0x0000563d01508c1b in doveadm_cmd_run_ver2 () #12 0x0000563d0150d612 in ?? () #13 0x00007f4e594406d9 in io_loop_call_io () from /usr/lib/dovecot/libdovecot.so.0 #14 0x00007f4e59442034 in io_loop_handler_run_internal () from /usr/lib/dovecot/libdovecot.so.0 #15 0x00007f4e594407e0 in io_loop_handler_run () from /usr/lib/dovecot/libdovecot.so.0 #16 0x00007f4e59440a18 in io_loop_run () from /usr/lib/dovecot/libdovecot.so.0 #17 0x00007f4e593a6a23 in master_service_run () from /usr/lib/dovecot/libdovecot.so.0 #18 0x0000563d014e6922 in main ()

4 5

Dovecot, Solr (FTS) and iOS body search
by Ben Howard 13 Dec '21

13 Dec '21

I had a question about full text search with Dovecot, Solr with iOS as a client (the built in default mail client). Does anyone happen to know if it's possible to get the iOS mail client to search bodies of email via IMAP with Dovecot and Solr on the server? I've looked at the IMAP queries being sent to Solr and regardless of iOS settings only the subject or to/cc/from seem to get queried. i.e.: test search query: Foobar Request [dovecot] webapp=/solr path=/select params={q={!lucene+q.op%3DAND}subject:Foobar&fl=uid,score&sort=uid+asc (trimmed for space) test search query with 'message' selected as search via the GUI in iOS mail app: Foobar 2021-12-12 22:16:43.840 INFO (qtp1309129055-21) [ x:dovecot] o.a.s.c.S.Request [dovecot] webapp=/solr path=/select params={q={!lucene+q.op%3DAND}to:Foobar+OR+cc:Foobar+OR+from:Foobar+OR+subject:Foobar&fl=uid,score&sort=uid+asc (trimmed for space) I also put Wireshark between an iOS device and the mail server to see the IMAP commands being issued client side and it matches with what Dovecot is seeing - i.e. only to/cc/from/subject no body queries. dovecot version: 2.3.17.1 (476cd46418), solr 8.11.0 and fts_enforced = yes Is it just not possible for the iOS mail client to search for keywords within the body of emails via IMAP/Dovecot/Solr? Any pointers, or just knowing I should give up, would be most gratefully received. Thanks

1 0

Re: 2.3.17: Panic on LMTP deliveries
by Volker ********* 13 Dec '21

13 Dec '21

It WORKS!!! :-) Great, thanks! Best regards Volker Am 12.12.2021 um 13:00 schrieb Volker: > That´s a good message, thank you very much! > > I will try the patch! > > Kind regards > Volker > > Am 12.12.2021 um 12:48 schrieb Aki Tuomi: >>>> Hello! >>>> >>>> While searching for an explanation for the fact that after updating to >>>> Dovecot 2.3.17_1 (FreeBSD 12.2) I suddenly stopped receiving emails and >>>> following error messages appeared in the dovecot.log, >>>> >>>> /Error: lmtp-server: conn unix:uid=125 [1]: rcptuser(a)domain.tld: >>>> duplicate db: Useruser(a)domain.tld doesn't have home dir set, disabling >>>> duplicate database// >>>> // >>>> //Dec 12 08:42:54 lmtp(user(a)domain.tld)<80363><z7AxDf6ntWHrOQEAp6O1gg>: >>>> Panic: file imem.c: line 65 (i_strconcat): assertion failed: (str1 != NULL) >>>> >>>> /I found your answer here >>>> <https://www.mail-archive.com/dovecot@dovecot.org/msg84893.html>: >>>> >>>> /Problem confirmed. This is a 2.3.17 regression. Tracking internally as >>>> DOP-2659./ >>>> / >>>> Regards, >>>> Stephan./ >>>> >>>> >>>> But what exactly does your answer mean for those affected? >>>> >>>> That all users who use Dovecot and use the whole thing without >>>> "mail_home" and only with "mail_location", must wait until a BugFix >>>> appears to be able to receive emails again? >>>> >>>> >>>> Thanks in advance and have a nice advent sunday >>>> Volker >>>> >>>> P. S.: >>>> In my case dovecot -n shows >>>> >>>> /mail_location = maildir:/var/mail/vhosts/%d/%n// >>>> //mail_home = /var/mail/vhosts/%d/%n >>>> >>>> /so mail_home is even set!/ >>>> / >>>> >>> You can roll back to 2.3.16 as well? >>> >>> Aki >> After looking bit more, this issue is fixed and will be in 2.3.18. If you want, you can try applying >> >> https://github.com/dovecot/core/compare/98f709de%5E..d36d2c59.patch >> >> which should fix this issue. >> >> Aki >

1 0

Send to mailbox + alias??
by postfix＠aecperformance.com 12 Dec '21

12 Dec '21

Is there any way to set postfix/dovecot to: 1. Deliver email to the mailbox -> ie. bob(a)test.com <mailto:bob@test.com> AND 2. Set the email as an alias and send it to the forwarded address -> bobs.boss(a)bosses.com <mailto:bobs.boss@bosses.com> This would be given that both email accounts are set up as virtual_users in MySql. Right now if I set up an alias and mailbox for the same email the alias overrides the mailbox and the email is delivered to the forwarded account and not to the email's mailbox. If the mailbox exists I need the email sent to both the mailbox and the forwarded mailbox. Can I do that? If so, how?

2 1

submission Connection failed: Failed to connect to remote server
by fugee ohu 12 Dec '21

12 Dec '21

I'm getting this error when I try to send mail mail dovecot: submission(username-here)<113012><tY+KjubSZJJHvuNn>: Debug: smtp-client: conn 127.0.0.1:25 [1]: Connection failed: Failed to connect to remote server

2 1

Re[7]: Replicator bug report
by Daniel Miller 12 Dec '21

12 Dec '21

On 12/7/2021 12:29:49 PM, "Daniel Miller" <dmiller(a)amfes.com> wrote: >>service replicator { >> vsz_limit = 2G >>} >> >>Aki >> >Tried that - got another one. I just tried setting service replicator { vcsz_limit = 5G } and I still get: Dec 7 15:08:25 bubba dovecot: replicator: Panic: data stack: Out of memory when allocating 4294967336 bytes -- Daniel

3 4

2.3.17: Panic on LMTP deliveries
by Volker 12 Dec '21

12 Dec '21

Hello! While searching for an explanation for the fact that after updating to Dovecot 2.3.17_1 (FreeBSD 12.2) I suddenly stopped receiving emails and following error messages appeared in the dovecot.log, /Error: lmtp-server: conn unix:uid=125 [1]: rcpt user(a)domain.tld: duplicate db: User user(a)domain.tld doesn't have home dir set, disabling duplicate database// // //Dec 12 08:42:54 lmtp(user(a)domain.tld)<80363><z7AxDf6ntWHrOQEAp6O1gg>: Panic: file imem.c: line 65 (i_strconcat): assertion failed: (str1 != NULL) /I found your answer here <https://www.mail-archive.com/dovecot@dovecot.org/msg84893.html>: /Problem confirmed. This is a 2.3.17 regression. Tracking internally as DOP-2659./ / Regards, Stephan./ But what exactly does your answer mean for those affected? That all users who use Dovecot and use the whole thing without "mail_home" and only with "mail_location", must wait until a BugFix appears to be able to receive emails again? Thanks in advance and have a nice advent sunday Volker P. S.: In my case dovecot -n shows /mail_location = maildir:/var/mail/vhosts/%d/%n// //mail_home = /var/mail/vhosts/%d/%n /so mail_home is even set!/ /

2 2

dovecot error
by Rajesh M 11 Dec '21

11 Dec '21

hello all we were seeing an error as such in dovecot.log for the first time we use sogo for active sync dovecot: master: Warning: service(dict): process_limit (100) reached, client connections are being dropped once we restarted sogo service this issue got resolved could someone please guide us on how to resolve the above please find below dovecot config file ####################################### # More details about Dovecot settings: # - http://wiki2.dovecot.org/ # - http://wiki2.dovecot.org/Variables # Listen addresses. # - '*' means all available IPv4 addresses. # - '[::]' means all available IPv6 addresses. # Listen on all available addresses by default listen = * #base_dir = /var/run/dovecot mail_plugins = quota mailbox_alias acl mail_log notify stats # Enabled mail protocols. protocols = pop3 imap sieve lmtp default_client_limit = 2400 # User/group who owns the message files: mail_uid = 2000 mail_gid = 2000 # Assign uid to virtual users. first_valid_uid = 2000 last_valid_uid = 2000 # Logging. Reference: http://wiki2.dovecot.org/Logging # # Use syslog syslog_facility = local5 # Log file path if we use internal log system #log_path = /var/log/dovecot/dovecot.log # Debug #mail_debug = yes #auth_verbose = yes #auth_debug = yes #auth_debug_passwords = yes # Possible values: no, plain, sha1. #auth_verbose_passwords = no # SSL: Global settings. # Refer to wiki site for per protocol, ip, server name SSL settings: # http://wiki2.dovecot.org/SSL/DovecotConfiguration ssl_protocols = !SSLv3 ssl = required verbose_ssl = no #ssl_ca = </path/to/ca ssl_cert = </etc/ssl/certificate_key.crt ssl_key = </etc/ssl/certificate_key.crt # Fix 'The Logjam Attack' ssl_cipher_list = ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5 ssl_prefer_server_ciphers = yes # With disable_plaintext_auth=yes AND ssl=required, STARTTLS is mandatory. # Set disable_plaintext_auth=no AND ssl=yes to allow plain password transmitted # insecurely. disable_plaintext_auth = no ssl=yes # Allow plain text password per IP address/net #remote 192.168.0.0/24 { # disable_plaintext_auth = no #} # Mail location and mailbox format. mail_location = maildir:%Lh/Maildir/:INDEX=%Lh/Maildir/ # Authentication related settings. # Append this domain name if client gives empty realm. #auth_default_realm = aaaonlinux.net # Authentication mechanisms. auth_mechanisms = PLAIN LOGIN # Limits the number of users that can be logging in at the same time. # Default is 100. This can be overridden by `process_limit =` in # `service [protocol]` block. # e.g. # protocol imap-login { # ... # process_limit = 500 # } #default_process_limit = 100 # Mail delivery log format deliver_log_format = from=%{from}, envelope_sender=%{from_envelope}, subject=%{subject}, msgid=%m, size=%{size}, %$ service auth { unix_listener /var/spool/postfix/private/dovecot-auth { user = postfix group = postfix mode = 0666 } unix_listener auth-master { user = vmail group = vmail mode = 0666 } unix_listener auth-userdb { user = vmail group = vmail mode = 0660 } } # LMTP server (Local Mail Transfer Protocol). # Reference: http://wiki2.dovecot.org/LMTP service lmtp { user = vmail # For higher volume sites, it may be desirable to increase the number of # active listener processes. A range of 5 to 20 is probably good for most # sites. process_min_avail = 5 # Logging. # Require 'log_path =' in 'protocol lmtp {}' block. executable = lmtp -L # Listening on socket file and TCP unix_listener /var/spool/postfix/private/dovecot-lmtp { user = postfix group = postfix mode = 0600 } inet_listener lmtp { # Listen on localhost (ipv4) address = 127.0.0.1 port = 24 } } # Virtual mail accounts. userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } # Master user. # Master users are able to log in as other users. It's also possible to # directly log in as any user using a master password, although this isn't # recommended. # Reference: http://wiki2.dovecot.org/Authentication/MasterUsers auth_master_user_separator = * passdb { driver = passwd-file args = /etc/dovecot/dovecot-master-users master = yes } plugin { # Quota configuration. # Reference: http://wiki2.dovecot.org/Quota/Configuration quota = dict:user::proxy::quotadict # Set default quota rule if no quota returned from SQL/LDAP query. #quota_rule = *:storage=1G #quota_rule2 = *:messages=0 #quota_rule3 = Trash:storage=1G #quota_rule4 = Junk:ignore # Quota warning. # # If user suddenly receives a huge mail and the quota jumps from # 85% to 95%, only the 95% script is executed. # # Only the command for the first exceeded limit is executed, so configure # the highest limit first. quota_warning = storage=100%% quota-warning 100 %u quota_warning2 = storage=95%% quota-warning 95 %u quota_warning3 = storage=90%% quota-warning 90 %u quota_warning4 = storage=85%% quota-warning 85 %u # allow user to become max 10% (or 50 MB) over quota quota_grace = 10%% #quota_grace = 50 M # Custom Quota Exceeded Message. # You can specify the message directly or read the message from a file. #quota_exceeded_message = Quota exceeded, please try again later. #quota_exceeded_message = </path/to/quota_exceeded_message.txt # Plugin: expire. #expire = Trash 7 Trash/* 7 Junk 30 #expire_dict = proxy::expire # ACL and share folder acl = vfile acl_shared_dict = proxy::acl # By default Dovecot doesn't allow using the IMAP "anyone" or # "authenticated" identifier, because it would be an easy way to spam # other users in the system. If you wish to allow it, #acl_anyone = allow # Pigeonhole managesieve service. # Reference: http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration # Per-user sieve settings. sieve_dir = ~/sieve sieve = ~/sieve/dovecot.sieve # Global sieve settings. sieve_global_dir = /var/vmail/sieve # Note: if user has personal sieve script, global sieve rules defined in # sieve_default will be ignored. Please use sieve_before or # sieve_after instead. #sieve_default = sieve_before = /var/vmail/sieve/dovecot.sieve #sieve_after = # The maximum number of redirect actions that can be performed during a # single script execution. # The meaning of 0 differs based on your version. For pigeonhole-0.3.0 and # beyond this means that redirect is prohibited. For older versions, # however, this means that the number of redirects is unlimited. sieve_max_redirects = 30 # Use recipient as vacation message sender instead of null sender (<>). sieve_vacation_send_from_recipient = yes # Reference: http://wiki2.dovecot.org/Plugins/MailboxAlias mailbox_alias_old = Sent mailbox_alias_new = Sent Messages mailbox_alias_old2 = Sent mailbox_alias_new2 = Sent Items # Events to log. `autoexpunge` is included in `expunge` # Defined in https://github.com/dovecot/core/blob/master/src/plugins/mail-log/mail-log-p… mail_log_events = delete undelete expunge mailbox_delete mailbox_rename mail_log_fields = uid box msgid size from subject # stats # # how often to session statistics (must be set) stats_refresh = 30 secs # track per-IMAP command statistics (optional) stats_track_cmds = yes } service stats { fifo_listener stats-mail { user = vmail mode = 0644 } inet_listener { address = 127.0.0.1 port = 24242 } } service quota-warning { executable = script /usr/local/bin/dovecot-quota-warning.sh unix_listener quota-warning { user = vmail group = vmail mode = 0660 } } service dict { unix_listener dict { mode = 0660 user = vmail group = vmail } } dict { #expire = db:/var/lib/dovecot/expire/expire.db quotadict = mysql:/etc/dovecot/dovecot-used-quota.conf acl = mysql:/etc/dovecot/dovecot-share-folder.conf } protocol lda { # Reference: http://wiki2.dovecot.org/LDA mail_plugins = $mail_plugins sieve lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes # Log file path if we use internal log system #log_path = /var/log/dovecot/sieve.log } protocol lmtp { # Log file path if we use internal log system #log_path = /var/log/dovecot/lmtp.log # Plugins mail_plugins = quota sieve # Address extension delivery lmtp_save_to_detail_mailbox = yes recipient_delimiter = + } protocol imap { mail_plugins = $mail_plugins imap_quota imap_acl imap_stats imap_client_workarounds = tb-extra-mailbox-sep #process_limit = 1000 # Maximum number of IMAP connections allowed for a user from each IP address. # NOTE: The username is compared case-sensitively. # Default is 10. # Increase it to avoid issue like below: # "Maximum number of concurrent IMAP connections exceeded" mail_max_userip_connections = 100 } protocol pop3 { mail_plugins = $mail_plugins pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv # Maximum number of IMAP connections allowed for a user from each IP address. # NOTE: The username is compared case-sensitively. # Default is 10. mail_max_userip_connections = 100 #process_limit = 1000 # POP3 logout format string: # %i - total number of bytes read from client # %o - total number of bytes sent to client # %t - number of TOP commands # %p - number of bytes sent to client as a result of TOP command # %r - number of RETR commands # %b - number of bytes sent to client as a result of RETR command # %d - number of deleted messages # %m - number of messages (before deletion) # %s - mailbox size in bytes (before deletion) # Default format doesn't have 'in=%i, out=%o'. #pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s, in=%i, out=%o } # Login processes. Refer to Dovecot wiki for more details: # http://wiki2.dovecot.org/LoginProcess ################### LAST LOGIN START protocol imap { # Append plugin name `last_login` here mail_plugins = last_login } protocol pop3 { # Append plugin name `last_login` here mail_plugins = last_login } dict { # Add this line. For FreeBSD, please replace the path by # /usr/local/etc/dovecot/dovecot-last-login.conf lastlogin = mysql:/etc/dovecot/dovecot-last-login.conf } plugin { # Add 2 lines last_login_dict = proxy::lastlogin last_login_key = last-login/%s/%u/%d/%r/%l } ################### LAST LOGIN END # Login processes. Refer to Dovecot wiki for more details: # http://wiki2.dovecot.org/LoginProcess ###################### service imap-login { service_count = 0 process_min_avail = 50 process_limit = 256 } service imap { process_limit = 2048 process_min_avail = 50 service_count = 1 vsz_limit = 512 M } ######################## service pop3-login { service_count = 0 process_min_avail = 25 process_limit = 256 } service pop3 { service_count = 1 process_limit = 256 process_min_avail = 25 } ########################## ############## #service imap-login { #inet_listener imap { # port = 143 #} #inet_listener imaps { # port = 993 # ssl = yes #} # service_count = 1 # To avoid startup latency for new client connections, set process_min_avail # to higher than zero. That many idling processes are always kept around # waiting for new connections. #process_min_avail = 0 # number of simultaneous IMAP connections # process_limit = 500 # vsz_limit should be fine at its default 64MB value #vsz_limit = 64M #} #service pop3-login { #inet_listener pop3 { # port = 110 #} #inet_listener pop3s { # port = 995 # ssl = yes #} # service_count = 1 # number of simultaneous POP3 connections #process_limit = 500 #} ############## Commented by service managesieve-login { inet_listener sieve { # Listen on localhost (ipv4) address = 127.0.0.1 port = 4190 } } namespace { type = private separator = / prefix = inbox = yes # Refer to document for more details about alias mailbox: # http://wiki2.dovecot.org/MailboxSettings # # Sent mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox "Sent Items" { auto = no special_use = \Sent } mailbox Drafts { auto = subscribe special_use = \Drafts } # Trash mailbox Trash { auto = subscribe special_use = \Trash } mailbox "Deleted Messages" { auto = no special_use = \Trash } # Junk mailbox Junk { auto = subscribe special_use = \Junk } mailbox Spam { auto = no special_use = \Junk } mailbox "Junk E-mail" { auto = no special_use = \Junk } # Archive mailbox Archive { auto = no special_use = \Archive } mailbox Archives { auto = no special_use = \Archive } } namespace { type = shared separator = / prefix = Shared/%%u/ location = maildir:%%Lh/Maildir/:INDEX=%%Lh/Maildir/Shared/%%Ld/%%Ln # this namespace should handle its own subscriptions or not. subscriptions = yes list = children } # Public mailboxes. # Refer to Dovecot wiki page for more details: # http://wiki2.dovecot.org/SharedMailboxes/Public #namespace { # type = public # separator = / # prefix = Public/ # location = maildir:/var/vmail/public:CONTROL=%Lh/Maildir/public:INDEXPVT=%Lh/Maildir/public # # # Allow users to subscribe to the public folders. # subscriptions = yes #} !include_try /etc/dovecot/iredmail/*.conf ################################## many thanks rajesh

2 1

dovecot error
by Rajesh M 10 Dec '21

10 Dec '21

1 0

RE: virtual mailbox domains??
by postfix＠aecperformance.com 09 Dec '21

09 Dec '21

Thanks *so much* for all your help. Another complete rebuild and I think I’ve finally got it. I was able to log into mail.sizzelicks.com for smoker1(a)sizzelicks.com <mailto:smoker1@sizzelicks.com> this time with no trouble. I sent an email to smoker1(a)sizzelicks.com <mailto:smoker1@sizzelicks.com> from a gmail account and was able to retrieve it in Thunderbird. I replied to the gmail email and in gmail.com I got the response. Now I can add email accounts to the database for any of our domains and they work! I've added responses below. -----Original Message----- From: owner-postfix-users(a)postfix.org <owner-postfix-users(a)postfix.org> On Behalf Of raf Sent: Thursday, December 9, 2021 1:07 AM To: postfix-users(a)postfix.org Subject: Re: virtual mailbox domains?? On Tue, Dec 07, 2021 at 10:25:44AM -0500, <mailto:postfix@aecperformance.com> postfix(a)aecperformance.com wrote: > Sorry I sent this from the wrong email address. > > VPS Ubuntu 20.04 postfix 3.4.13 and dovecot 2.3.7.2 > > I'm making progress but still not there. > > Any help would be greatly appreciated. > > I'm getting the errors: > > warning: SASL: Connect to private/auth failed: Connection refused > > fatal: no SASL authentication mechanisms > > > > I have a param in main.cf: smtpd_sasl_path = private/auth > > I do not have a folder /etc/postfix/private/auth > > I do have a folder /etc/postfix/auth but nothing is in it. > > How can I fix this error? The reference to private/auth is referring to dovecot's authentication socket under postfix's chroot directory. It's in /var/spool/postfix/private/auth, not /etc/postfix. You have set that up in dovecot's config: service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail } user = dovecot } My version of that looks like: service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } So it looks like that should be OK. Does /var/spool/postfix/private/auth exist? Mine has root as owner/group. Yours should have postfix as owner/group. But that shouldn't matter as long as the mode is 0666. I must of changed the mode to 0660 but per your suggestion I changed it to 0666. Thanks. Yes it does exist. ls -l /var/spool/postfix/private/auth srw-rw---- 1 postfix postfix 0 Dec 8 21:50 /var/spool/postfix/private/auth If not, check dovecot's log messages for problems with it. But I don't know what to look for. The dovecot mailing list folks might be more useful for that. It should exist and be used by dovecot. If you have lsof installed, you can check that: > sudo lsof /var/spool/postfix/private/auth COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME dovecot 17341 root 53u unix 0xffff8e43c69f7400 0t0 16873340 /var/spool/postfix/private/auth type=STREAM auth 1521507 dovecot 13u unix 0xffff8e43c69f7400 0t0 16873340 /var/spool/postfix/private/auth type=STREAM auth 1521507 dovecot 21u unix 0xffff8e43c417c800 0t0 69451443 /var/spool/postfix/private/auth type=STREAM auth 1521507 dovecot 22u unix 0xffff8e43c9fc2400 0t0 69453124 /var/spool/postfix/private/auth type=STREAM sudo lsof /var/spool/postfix/private/auth COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME dovecot 4550 root 58u unix 0x0000000000000000 0t0 1305802532 /var/spool/postfix/private/auth type=STREAM Something else that might or might not be a (different) problem is that the TLS certificate at mail.sizzlelicks.com doesn't certify the domain mail.sizzlelicks.com. Its list of domains contains sizzelicks.com and <http://www.sizzelicks.com> www.sizzelicks.com but not mail.sizzelicks.com. That might cause problems with Thunderbird trying to connect for IMAPS. I think you reported such an error message earlier. So you might want to add the mail.sizzelicks.com domain to that certificate. But that's not related to the failure to connect to the dovecot auth socket. You are correct and I sure wish I saw *this* a week ago😊. I did a rebuild due to lots of trouble trying to add the certs. Now I’ve got it all back up with the certificates for all of the mail.mydomain.com MX records. THANK YOU cheers, raf > -----Original Message----- > From: <mailto:owner-postfix-users@postfix.org> owner-postfix-users(a)postfix.org > < <mailto:owner-postfix-users@postfix.org> mailto:owner-postfix-users@postfix.org> > <owner-postfix-users(a)postfix.org > < <mailto:owner-postfix-users@postfix.org> mailto:owner-postfix-users@postfix.org> > On Behalf Of Wietse Venema > Sent: Monday, December 6, 2021 11:04 AM > To: Postfix users <postfix-users(a)postfix.org > < <mailto:postfix-users@postfix.org> mailto:postfix-users@postfix.org> > > Subject: Re: virtual mailbox domains?? > > > > < <mailto:postfix@aecperformance.com> mailto:postfix@aecperformance.com> <mailto:postfix@aecperformance.com> postfix(a)aecperformance.com: > > > Command: sudo postfix status > > > postfix/postfix-script: the Postfix mail system is running: PID: > > 38284 > > > > Good. > > > > > I attempted to send an email to < <mailto:smoker1@sizzelicks.com> mailto:smoker1@sizzelicks.com> > <mailto:smoker1@sizzelicks.com> smoker1(a)sizzelicks.com > > > < < <mailto:smoker1@sizzelicks.com> mailto:smoker1@sizzelicks.com> <mailto:smoker1@sizzelicks.com> mailto:smoker1@sizzelicks.com> . > > It > bounced. > > > > What is the Postfix logging for this? Be sure to include more than > only the delivery error (i.e. logging from pickup or smtpd; cleanup; qmgr; ...). > > > > This is the first problem that you need to fix. > > > > > In the log I see a few attempts to connect from spammers. I do not > > see > > > my laptop IP or anything at all about what I did. > > > > That is the second problem to fix. I suspect a firewalling or routing > problem. > > > > Wietse >

1 0

Force clients to use pgp encryption when sending email?
by Austin Witmer 09 Dec '21

09 Dec '21

Hello all! I am looking for a way to force imap clients to encrypt their messages with the public keys of the recipients before sending them. Would a post-login script in dovecot work for something like this? I am using postfix and dovecot on my mail server. Basically I want the server to check if the message being sent is encrypted with OpenGPG and either proceed or reject the message based on that criteria. If the message is rejected, the user could then encrypt the outgoing email message with the recipient public key and try again. Does anybody have a suggestion on how to implement something like this? Would there be a way that the the client software (thunderbird) could show an alert asking the user to encrypt the message and then attempt to resend the message? I realize that you can tell a client (like thunderbird) to automatically encrypt outgoing messages with pgp but I would like to have some way to enforce that policy at the server level before the email is sent. I want to have all messages end-to-end encrypted, hence my desire for functionality like this. Any suggestions are welcome. Thanks in advance for your help!

3 4

Mailbox connection fails: Connection closed (No commands sent) Help please
by postfix＠aecperformance.com 09 Dec '21

09 Dec '21

I would greatly appreciate help with this. VPS ubuntu 20.04 postfix 3.4.13 dovecot 2.3.7.2 I'm trying to set up postfix with dovecot for virtual mailboxes using mysql I have a database mailserver with tables virtual_domains, virtual_users & virtual_aliases Using postmap I've tested all connections and gotten correct responses (1, 1, smoker1(a)sizzelicks.com <mailto:smoker1@sizzelicks.com> ) I have a domain: sizzelicks.com and an email address smoker1(a)sizzelicks.com <mailto:smoker1@sizzelicks.com> The password for the user is encrypted with sha512-CRYPT My VPS IP is: 194.163.45.150 MX test from: https://mxtoolbox.com/SuperTool.aspx?action=mx%3asizzelicks.com&run=toolpage I set up a mailbox for smoker1(a)sizzelicks.com <mailto:smoker1@sizzelicks.com> in Thunderbird: IMAP and SMTP server: mail.sizzelicks.com IMAP port: 993 SMTP port: 587 IMAP connection security: SSL/TLS SMTP connection security: STARTTLS When I try to connect to the mailbox Thunderbird returns this: server mail.sizzelicks.com has disconnected. The server may have gone down or there may be a network problem. mail.log Dec 7 21:16:02 softlinksys dovecot: imap-login: Login: user=, method=PLAIN, rip=67.8.3.170, lip=194.163.45.150, mpid=63115, TLS, session= Dec 7 21:16:02 softlinksys dovecot: imap(smoker1(a)sizzelicks.com)<63115>: Connection closed (No commands sent) in=0 out=388 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Dec 7 21:16:04 softlinksys dovecot: imap-login: Login: user=, method=PLAIN, rip=67.8.3.170, lip=194.163.45.150, mpid=63117, TLS, session= Dec 7 21:16:04 softlinksys dovecot: imap(smoker1(a)sizzelicks.com)<63117>: Connection closed (No commands sent) in=0 out=388 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Dovecot -n # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.0 x86_64 Ubuntu 20.04.3 LTS ext4 # Hostname: softlinksys.com auth_mechanisms = plain login mail_location = maildir:/var/mail/vhosts/%d/%n mail_privileged_group = mail namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } postmaster_address = postmaster at aecperformance.com protocols = imap pop3 lmtp service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail } user = dovecot } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } 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 { port = 995 ssl = yes } } ssl = required ssl_cert = </etc/letsencrypt/live/aecperformance.com/fullchain.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 { driver = passwd } userdb { args = uid=vmail gid=vmail home=/var/mail/vhosts/%d/%n driver = static } Kristy Atkins ViviData SaaS

5 8

Unexpected variable expand behavior
by Евгений Бахтин 09 Dec '21

09 Dec '21

2 1

No source packages in APT repo?
by Shawn Heisey 08 Dec '21

08 Dec '21

I added a deb-src entry to my APT config matching the deb entry: deb https://repo.dovecot.org/ce-2.3-latest/ubuntu/focal focal main deb-src https://repo.dovecot.org/ce-2.3-latest/ubuntu/focal focal main When this is there, I see a warning when running "apt update". W: Skipping acquire of configured file 'main/source/Sources' as repository 'https://repo.dovecot.org/ce-2.3-latest/ubuntu/focal focal InRelease' does not seem to provide it (sources.list entry misspelt?) Were source packages excluded deliberately? The github repo for dovecot does not have a "debian" directory, which is the other route that would allow me to build packages. Thanks, Shawn

3 6

#define DUPLICATE_LOCK_MAX_LOCKS 100
by Vladimir Gulas 08 Dec '21

08 Dec '21

Hello, dovecot --version 2.3.17 (e2aa53df5b) debug log: Debug: duplicate db: transaction: Too many duplicate IDs locked Debug: duplicate db: transaction: Check ID: too many IDs locked - .sieve with 100+ redirects ( 201 actually ) #define DUPLICATE_LOCK_MAX_LOCKS 100 It's not corresponding with sieve_max_redirects = 310 or sieve_max_actions = 320 On dovecot 2.3.16 version DUPLICATE_LOCK_MAX_LOCKS is not implemented and redirects work correctly. Thank you. Vladimir Gulas.

1 0

app-specific passwords for dovecot
by mj 08 Dec '21

08 Dec '21

Hi all, I have read these documents on the subject of app-specific passwords: > https://www.dgsiegel.net/news/2013_05_21-application_specific_passwords_for… > https://www.happyassassin.net/posts/2014/08/26/adding-application-specific-… But since both articles are rather old, I'd like to ask if there are other/new ways of implementing app-specific passwords for dovecot/imap and postfix/smtp. Also perhaps (web?) GUI's exist, to make it possible for the users themselves to generate/edit those passwords..? Thanks for your suggestions! MJ

1 0

vsz_limit
by Daniel Miller 07 Dec '21

07 Dec '21

I just noticed, that when checking "doveconf -a" - all vsz_limit settings that are not explicitly given have a value of: 18446744073709551615 B I have this on two servers, one with an implicit default_vsz_limit=256M, the other with an explicit default_vsz_limit=2G. Is this correct? -- Daniel

1 0

Replicator bug report
by Daniel Miller 07 Dec '21

07 Dec '21

I've run dovecot-sysreport -o <core> and generated a file - but it's a few gigs in size. Am I generating the core dump incorrectly? Should I do something different? -- Daniel

3 6

Pigeonhole v0.5.17.1 Released
by Aki Tuomi 07 Dec '21

07 Dec '21

We are happy to announce 0.5.17.1 patch release of Pigeonhole. This contains some fixes for issues found after 0.5.17 release. https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.17.1… https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.17.1… Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Aki Tuomi Open-Xchange oy --- - managesieve: Dovecot failed to start if ssl_ca was too large. - lib-sieve-tool: Binaries failed to run if ssl_ca was too large.

1 0

LDAP and user duplicated with replication
by Claudio Corvino 07 Dec '21

07 Dec '21

Hi, I have two IMAP/LMTP Dovecot server in replica (version 2.3.4.1), I use LDAP/AD for /userdb, /replica is working. When I do a search like: /doveadm replicator status '*'/ I receive user duplicated, with and without the domain part, for example: /test/ /test(a)domain.com/ but they are the same user; this lead the replicator doing twice the work of replication. I think this is related to //etc/dovecot/dovecot-ldap.conf/ that is configured in this way: /hosts = xxx/ /base = dc=xxx,dc=xxx ldap_version=3 auth_bind = yes dn = cn=xxx,cn=Users,dc=xxx,dc=xxx dnpass = xxx scope = subtree user_attrs = sAMAccountName=home=/mnt/mail-storage-lv0007/%$,=uid=501,=gid=501 pass_attrs = sAMAccountName=user user_filter = (&(objectclass=person)(samaccountname=%n)) pass_filter= (&(objectclass=person)(samaccountname=%n)) iterate_attrs = sAMAccountName=user # With following filter we exclude all objects without an email address, all computers and all inactive accounts / /iterate_filter = (&(objectCategory=person)(mail=*)(objectClass=user)(!(userAccountControl:1.2.840.113556.1.4.803:=2))) / I think that *iterate_attrs* and *iterate_filter* should be fixed, but I don't know how/./ Please could someone give me any hints? Thanks/ / Regards/ /

2 3

public folders, ACLs
by Stefan G. Weichinger 06 Dec '21

06 Dec '21

greetings ... I got the following request from a customer where we run dovecot-2.3.15 on a debian server: They have a public folder with all their project-related subfolders inside: namespace { location = maildir:/home/vmail/oeffentlich prefix = Oeffentlich/ separator = / subscriptions = yes type = public } So far we don't have the mail_plugin ACL enabled. They want to be able to create projectfolders that aren't move/delete/rename-able by the users, only by some admins. But the users should be allowed to move mails between different projectfolders etc As far as I understand we can do that with Dovecot ACLs (although I am still figuring out how to properly design them ...). My questions: * if I enable the mail_plugin for ACLs, does that in any way change the behavior of existing mailboxes? afai understand: no. Only if ACL-lists exist in the various mailboxes, these get applied, right? I don't want to break things, and I want to avoid additional complexity for the non-public user mailboxes etc Maybe I can enable the plugin only for that public namespace? * maybe someone has a link to a similar setup? thanks in advance, Stefan

2 8

Errors after upgrade to v2.3.17
by Aurel Mihai 06 Dec '21

06 Dec '21

Hello, after upgrade to version 2.3.17, we enconter a lot of errors, such as: Dec 2 13:41:22 mail5 dovecot: lmtp(user@domain)<41944><EFw6IuKwqGHYowAAF7/xgA>: Error: lmtp-server: conn unix:pid=40487,uid=107 [22]: rcpt user@domain: stat(/home/virtual0/domain/user/.dovecot.lda-dupes/tmp) failed: Not a directory Here is my config: #dovecot -n # 2.3.17 (e2aa53df5b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.17 (054dddfa) # OS: Linux 4.19.0-18-amd64 x86_64 Debian 10.11 nfs # Hostname: auth_cache_verify_password_with_worker = yes auth_failure_delay = 5 secs auth_mechanisms = plain login auth_verbose = yes auth_worker_max_count = 256 default_client_limit = 10000 default_process_limit = 10000 default_vsz_limit = 1 G dict { lastlogin = mysql:/etc/dovecot/mysql/dovecot-dict-lastlogin.conf quotadict = mysql:/etc/dovecot/mysql/dovecot-dict-quota.conf } disable_plaintext_auth = no first_valid_uid = 100 imap_hibernate_timeout = 5 secs imap_idle_notify_interval = 3 mins log_timestamp = "%Y-%m-%d %H:%M:%S " login_log_format_elements = user=<%u> method=%m rip=%r lip=%l pid=%p %c login_trusted_networks = xxxx mail_fsync = always mail_location = maildir:/home/virtual0/%d/%u mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = zlib quota mail_log notify mail_privileged_group = mail maildir_stat_dirs = yes 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 ihave metric imap_command { filter = event=imap_command_finished AND tagged_reply_state=OK group_by = cmd_name } metric imap_select_no { filter = event=imap_command_finished AND cmd_name=SELECT AND tagged_reply_state=NO } metric imap_select_no_notfound { filter = event=imap_command_finished AND cmd_name=SELECT AND tagged_reply="NO*Mailbox doesn't exist:*" } metric storage_http_gets { filter = event=http_request_finished AND category=storage AND method=get } mmap_disable = yes namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Trash { auto = subscribe autoexpunge = 60 days special_use = \Trash } mailbox virtual/All { special_use = \All } prefix = } passdb { args = /etc/dovecot/mysql/dovecot-sql.conf driver = sql } plugin { last_login_dict = proxy::lastlogin last_login_key = # hidden, use -P to show it mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size quota = dict:user::proxy::quotadict quota_rule2 = Trash:ignore quota_rule3 = Spam:ignore quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 The email account that you tried to reach is over quota quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = ~/.dovecot.sieve sieve_before = /etc/dovecot/sieve/default.sieve sieve_dir = ~/sieve trash = /etc/dovecot/dovecot-trash.conf zlib_save = gz zlib_save_level = 6 } protocols = imap sieve pop3 lmtp service anvil { client_limit = 50000 unix_listener anvil-auth-penalty { mode = 00 } } service auth { client_limit = 50000 unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { group = mail mode = 0660 user = vmail } user = root vsz_limit = 1 G } service dict { unix_listener dict { mode = 0660 user = vmail } } service imap-hibernate { unix_listener imap-hibernate { group = $default_internal_group mode = 0660 } } service imap-login { inet_listener imap { address = * port = 143 } inet_listener imaps { address = * port = 993 } process_min_avail = 16 service_count = 1 } service imap { extra_groups = $default_internal_group process_min_avail = 16 unix_listener imap-master { user = $default_internal_user } vsz_limit = 2 G } service lmtp { process_min_avail = 16 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } vsz_limit = 1 G } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 16 service_count = 1 } service managesieve { vsz_limit = 1 G } service pop3-login { inet_listener pop3 { address = * port = 110 } inet_listener pop3s { address = * port = 995 } process_min_avail = 16 service_count = 1 } service pop3 { process_min_avail = 16 vsz_limit = 1 G } service quota-status { executable = /usr/lib/dovecot/quota-status -p postfix process_min_avail = 16 unix_listener /var/spool/postfix/private/quota-status { group = postfix mode = 0666 user = postfix } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { mode = 0660 user = vmail } user = vmail } service stats { unix_listener stats-reader { mode = 0660 user = vmail } unix_listener stats-writer { mode = 0666 user = vmail } } ssl_cert = </etc/dovecot/ssl/domain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1 userdb { args = /etc/dovecot/mysql/dovecot-sql.conf driver = sql } protocol imap { imap_max_line_length = 64 k mail_max_userip_connections = 16 mail_plugins = zlib quota mail_log notify trash imap_quota last_login } protocol pop3 { mail_max_userip_connections = 10 mail_plugins = zlib quota mail_log notify last_login pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_fast_size_lookups = yes pop3_no_flag_updates = yes pop3_uidl_format = %08Xu%08Xv } protocol sieve { mail_max_userip_connections = 10 managesieve_max_compile_errors = 5 } protocol lda { auth_socket_path = /var/run/dovecot/auth-master mail_plugins = zlib quota mail_log notify sieve sendmail_path = /usr/lib/sendmail syslog_facility = mail } protocol lmtp { mail_plugins = zlib quota mail_log notify sieve syslog_facility = mail } Any help please? Aurel

3 4

Re[5]: Replication weirdness
by Daniel Miller - CLOUD 05 Dec '21

05 Dec '21

Another update. I dug deeper into the mailboxes - and found the "subscriptions" and actual mailboxes weren't correct in all cases. I guess when I shifted to the explicit INBOX/ namespace not all the existing boxes migrated correctly. So...after manually correcting all the "subscription" files, and manually moving the duplicated "Archives" folders to the correct locations nearly all the errors have gone. I wish I'd gotten more inforrmative error messages, and processes certainly shouldn't have crashed, but since I obviously created the problem due to manually poking things and improper configuration I guess I can't complain too much. I still have problems using the "-N" flag for syncing - but things seem to be working with the multiple explicit "-n" namespaces. I do still have the locking error appearing during long-running syncs - I don't see why Dovecot doesn't know that it's already syncing a given user before trying to start a second process. Probably something else I setup wrong but I don't know what. -- Daniel

1 0

Re[4]: Replication weirdness
by Daniel Miller 04 Dec '21

04 Dec '21

And some more messages... Dec 3 15:10:58 bubba dovecot: doveadm(obfuscated)<1901><UGoeMgGkqmFtBwAAnbWsyw>: Error: Mailbox Sent sync: mailbox_rename failed: Can't rename mailbox while it has aliases Dec 3 15:10:58 bubba dovecot: doveadm(obfuscated)<1900><YVHxLACkqmFsBwAAnbWsyw>: Error: Duplicate mailbox GUID f4338038839caa613a1a0500b88bfabe for mailboxes INBOX/Sent Messages and INBOX/Sent - giving a new GUID bcf4f82702a4aa616c0700009db5accb to INBOX/Sent -- Daniel ------ Original Message ------ From: "Daniel Miller" <dmiller(a)amfes.com> To: "Daniel Miller" <dmiller(a)amfes.com>; dovecot(a)dovecot.org Sent: 12/3/2021 3:13:55 PM Subject: Re[3]: Replication weirdness >And... > >The user who has both a "Sent" and a "Sent Messages" now has: > >drwx------ 3 vmail mail 24 Dec 3 09:56 Sent >lrwxrwxrwx 1 vmail mail 4 Nov 30 17:51 'Sent Messages' -> Sent >drwx------ 3 vmail mail 24 Dec 3 15:10 'Sent Messages-temp-1' >drwx------ 3 vmail mail 24 Dec 3 15:10 'Sent >Messages-temp-fc30bd0a3a9aaa61c1180500b88bfabe' > >and I got the following errors: > >Dec 3 15:10:46 cloud1 dovecot: >doveadm(obfuscated)<336247><EMEQBvWjqmF3IQUAuIv6vg>: Error: Duplicate >mailbox GUID 6aae8c39f3a3aa615a0700009db5accb for mailboxes Sent and >Sent Messages-temp-1 - giving a new GUID >63481f29f6a3aa6177210500b88bfabe to Sent >Dec 3 15:10:50 cloud1 dovecot: >doveadm(obfuscated)<336245><HrHeOPOjqmF1IQUAuIv6vg>: Panic: file >dsync-brain-mailbox.c: line 851 (dsync_brain_slave_recv_mailbox): >assertion failed: (memcmp(dsync_box->mailbox_guid, >local_dsync_box.mailbox_guid, sizeof(dsync_box->mailbox_guid)) == 0) >Dec 3 15:10:50 cloud1 dovecot: >doveadm(obfuscated)<336245><HrHeOPOjqmF1IQUAuIv6vg>: Error: Raw >backtrace: #0 fatal_handler_real[0x7fde7fd20060] -> #1 >i_internal_fatal_handler[0x7fde7fd20190] -> #2 i_panic[0x7fde7fc731ff] >-> #3 dsync_brain_slave_recv_mailbox[0x55dde7b22900] -> #4 >dsync_brain_run[0x55dde7b20380] -> #5 >dsync_brain_run_io[0x55dde7b20b50] -> #6 >dsync_ibc_stream_input[0x55dde7b329c0] -> #7 >io_loop_call_io[0x7fde7fd36500] -> #8 >io_loop_handler_run_internal[0x7fde7fd37ac0] -> #9 >io_loop_handler_run[0x7fde7fd365c0] -> #10 io_loop_run[0x7fde7fd36740] >-> #11 cmd_dsync_server_run[0x55dde7b04f60] -> #12 >doveadm_mail_next_user[0x55dde7b06850] -> #13 >doveadm_cmd_ver2_to_mail_cmd_wrapper[0x55dde7b077e0] -> #14 >doveadm_cmd_run_ver2[0x55dde7b17f00] -> #15 >client_connection_tcp_input[0x55dde7b1c6b0] -> #16 >io_loop_call_io[0x7fde7fd36500] -> #17 >io_loop_handler_run_internal[0x7fde7fd37ac0] -> #18 >io_loop_handler_run[0x7fde7fd365c0] -> #19 io_loop_run[0x7fde7fd36740] >-> #20 master_service_run[0x7fde7fca87d0] -> #21 main[0x55dde7af7770] >-> #22 __libc_start_main[0x7fde7f8f9fc0] -> #23 _start[0x55dde7af78d0] >Dec 3 15:10:50 cloud1 dovecot: >doveadm(obfuscated)<336245><HrHeOPOjqmF1IQUAuIv6vg>: Fatal: master: >service(doveadm): child 336245 killed with signal 6 (core dumped) >Dec 3 15:10:52 cloud1 dovecot: >doveadm(obfuscated)<336253><2VTpM/ujqmF9IQUAuIv6vg>: Error: Duplicate >mailbox GUID 63481f29f6a3aa6177210500b88bfabe for mailboxes INBOX/Sent >and INBOX/Sent Messages-temp-1 - giving a new GUID >cba35507fca3aa617d210500b88bfabe to INBOX/Sent >Dec 3 15:10:58 cloud1 dovecot: >doveadm(obfuscated)<336258><ykbQAAGkqmGCIQUAuIv6vg>: Error: Duplicate >mailbox GUID dc3b4434fba3aa61660700009db5accb for mailboxes Sent and >Sent Messages-temp-1 - giving a new GUID >60ad190102a4aa6182210500b88bfabe to Sent > >-- >Daniel > >------ Original Message ------ >From: "Daniel Miller" <dmiller(a)amfes.com> >To: "Daniel Miller" <dmiller(a)amfes.com>; dovecot(a)dovecot.org >Sent: 12/3/2021 2:42:12 PM >Subject: Re[2]: Replication weirdness > >>And...one more. >> >>I'm now seeing (again) messages like: >> >>Dec 3 14:29:14 cloud1 dovecot: >>doveadm(obfuscated)<334017><e3FHNjmaqmHBGAUAuIv6vg>: Error: Duplicate >>mailbox GUID bcb9ca36ae36aa617f0a00009db5accb for mailboxes INBOX/Sent >>Messages and INBOX/Sent - giving a new GUID >>fc30bd0a3a9aaa61c1180500b88bfabe to INBOX/Sent >>Dec 3 14:38:59 cloud1 dovecot: >>doveadm(obfuscated)<334394><an5KIoOcqmE6GgUAuIv6vg>: Error: Duplicate >>mailbox GUID fc30bd0a3a9aaa61c1180500b88bfabe for mailboxes INBOX/Sent >>Messages and INBOX/Sent - giving a new GUID >>f4338038839caa613a1a0500b88bfabe to INBOX/Sent >> >>Having one message for the initial sync I suppose is reasonable. A >>second...maybe? But I'm getting nervous I'm about to start seeing the >>endless temp folders again. >>-- >>Daniel >> >>------ Original Message ------ >>From: "Daniel Miller" <dmiller(a)amfes.com> >>To: "Daniel Miller" <dmiller(a)amfes.com>; dovecot(a)dovecot.org >>Sent: 12/3/2021 2:39:25 PM >>Subject: Re: Replication weirdness >> >>>Another item. >>> >>>Again, it may be a 2.3.13 issue and I'm now on 2.3.17. But...I had >>>problem when using the "-N" parameter for dsync. So - I just have >>>(had): >>> >>>replication_dsync_parameters = -d -l 30 -U -x INBOX/virtual -x >>>INBOX/shared >>> >>>Now that things are working - I wanted to have my other namespaces >>>sync as well. So I went to: >>> >>>replication_dsync_parameters = -d -l 30 -U -n INBOX -n INBOX/Archives >>>-n INBOX/Lists -x INBOX/virtual -x INBOX/shared >>> >>>This appears to be working (the sync is just starting)...but I'm >>>seeing lock errors in the logs such as: >>>Dec 3 14:34:24 bubba dovecot: >>>doveadm(dmiller(a)amfes.com)<31785><TV+0LlGbqmEpfAAAnbWsyw>: Error: >>>Couldn't lock /var/mail/amfes.com/dmiller/.dovecot-sync.lock: >>>fcntl(/var/mail/amfes.com/dmiller/.dovecot-sync.lock, write-lock, >>>F_SETLKW) locking failed: Timed out after 30 seconds (WRITE lock held >>>by pid 31373) >>> >>>Checking the pid in question I see it's actively syncing a folder in >>>my mailbox. So I'm guessing, purely guessing, that by having multiple >>>namespaces explicitly directed to sync Dovecot is trying to start a >>>sync process for each of those namespaces - but all of them share a >>>common lock and therefore only one operation is allowed at a time. >>> >>>Am I correct, and whether or not I am - how can I correct these >>>errors? Do I dare try going back to just "-N"? >>> >>>-- >>>Daniel >>> >>>------ Original Message ------ >>>From: "Daniel Miller" <dmiller(a)amfes.com> >>>To: dovecot(a)dovecot.org >>>Sent: 12/3/2021 2:16:28 PM >>>Subject: Replication weirdness >>> >>>>First, I have to say this. After configuring everything correctly - >>>>and that means *everything* correctly - Dovecot replication Just >>>>Works. I'm not sure how (yes I do - Timo & Co. Magic) - but it does. >>>>Real-time new sync is near instantaneous. >>>> >>>>Now the problem. Or the background for the problem. My primary >>>>server uses sdbox for primary storage, mdbox for archival storage, >>>>and fts-solr. I spun up a second server, using sdbox, mdbox, and >>>>fts-flatcurve. My namespaces are as defined below. As best I can >>>>tell (based on diff comparing two 'doveconf -n' outputs) my >>>>namespaces are the same on both servers. >>>> >>>>namespace archives { >>>> list = children >>>> location = mdbox:/var/mail/%d/%n/Archives/mdbox >>>> mailbox Unsorted { >>>> auto = no >>>> special_use = \Archive >>>> } >>>> prefix = INBOX/Archives/ >>>> separator = / >>>> subscriptions = no >>>> type = private >>>>} >>>>namespace inbox { >>>> alias_for = >>>> hidden = no >>>> inbox = yes >>>> list = yes >>>> location = >>>> mailbox "Deleted Messages" { >>>> auto = no >>>> autoexpunge = 30 days >>>> special_use = \Trash >>>> } >>>> mailbox Drafts { >>>> auto = subscribe >>>> special_use = \Drafts >>>> } >>>> mailbox Sent { >>>> auto = subscribe >>>> special_use = \Sent >>>> } >>>> mailbox Trash { >>>> auto = subscribe >>>> autoexpunge = 30 days >>>> special_use = \Trash >>>> } >>>> prefix = INBOX/ >>>> separator = / >>>> subscriptions = no >>>> type = private >>>>} >>>>namespace lists { >>>> list = children >>>> location = mdbox:/var/mail/%d/%n/Lists/mdbox >>>> prefix = INBOX/Lists/ >>>> separator = / >>>> subscriptions = no >>>> type = private >>>>} >>>>namespace subscriptions { >>>> hidden = yes >>>> list = no >>>> location = >>>> prefix = >>>> separator = / >>>> subscriptions = yes >>>> type = private >>>>} >>>>namespace usershares { >>>> list = yes >>>> location = sdbox:/var/mail/%%d/%%n/sdbox:NO-NOSELECT >>>> prefix = INBOX/shared/%%d/%%n/ >>>> separator = / >>>> subscriptions = no >>>> type = shared >>>>} >>>>namespace virtual { >>>> list = children >>>> location = virtual:/var/mail/%d/%n/virtual >>>> mailbox Flagged { >>>> comment = All my flagged messages >>>> special_use = \Flagged >>>> } >>>> prefix = INBOX/virtual/ >>>> separator = / >>>> subscriptions = no >>>>} >>>> >>>>I also have: >>>>plugin { >>>> mailbox_alias_new = Sent Messages >>>> mailbox_alias_new2 = Sent Items >>>> mailbox_alias_new3 = Deleted Messages >>>> mailbox_alias_old = Sent >>>> mailbox_alias_old2 = Sent >>>> mailbox_alias_old3 = Trash >>>>} >>>> >>>>This setup worked fine with my single server. Then I enabled >>>>replication - just on the primary. Dsync went to work (it seemed to >>>>take forever for the initial sync but that's what happens with large >>>>mailboxes and slow internet connections). >>>> >>>>The problem came up with certain subfolders. And I believe it only >>>>happens with subfolders that have spaces in their names. I had two >>>>user's mailboxes (under Sent), one of which had a "Sent Messages" >>>>symlink alias for "Sent", that started generating tens or hundreds >>>>of duplicates during sync. Fortunately those subfolders only had a >>>>few mails in them. But I had trees looking like: >>>> >>>>[...] (below is under /var/mail/domain/user/sdbox/mailboxes/Sent/) >>>>Proposal >>>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-1-temp-f80b1a00ce9aa961a86-temp-2 >>>>Proposal >>>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-1-temp-f80b1a00ce9aa961a86-temp-3 >>>>Proposal >>>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-023fa4271c9ca9611ade0400b88bfabe >>>>Proposal >>>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-023fa4271c9ca9611ad-temp-1 >>>>Proposal >>>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-1 >>>>Proposal >>>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-2 >>>>Proposal >>>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-2-temp-1-temp-1 >>>>Proposal >>>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-3 >>>>Proposal >>>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-4 >>>>Proposal >>>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-5 >>>>Proposal >>>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-e2aa0f35c99ba961356500009db5accb >>>>[...] >>>> >>>>I kept stopping, cleaning up the folders, and re-starting - and they >>>>kept regenerating. I tried renaming the folders to eliminate the >>>>spaces and I think that helped in one case - for the others I just >>>>moved the folders outside of the mail area completely to let the >>>>sync finish. >>>> >>>>Now that it's been stable for a day or two - I enabled sync in the >>>>other direction. And after setting *all* the required parameters >>>>instead of just most of them...it's working. But...I'm nervous about >>>>moving the problem folders back over. I will say, if it makes any >>>>difference, my primary server *was* running version 2.3.13 and I >>>>just updated it to 2.3.17. The remote is also 2.3.17. >>>> >>>>-- >>>>Daniel

1 0

Re[3]: Replication weirdness
by Daniel Miller 04 Dec '21

04 Dec '21

And... The user who has both a "Sent" and a "Sent Messages" now has: drwx------ 3 vmail mail 24 Dec 3 09:56 Sent lrwxrwxrwx 1 vmail mail 4 Nov 30 17:51 'Sent Messages' -> Sent drwx------ 3 vmail mail 24 Dec 3 15:10 'Sent Messages-temp-1' drwx------ 3 vmail mail 24 Dec 3 15:10 'Sent Messages-temp-fc30bd0a3a9aaa61c1180500b88bfabe' and I got the following errors: Dec 3 15:10:46 cloud1 dovecot: doveadm(obfuscated)<336247><EMEQBvWjqmF3IQUAuIv6vg>: Error: Duplicate mailbox GUID 6aae8c39f3a3aa615a0700009db5accb for mailboxes Sent and Sent Messages-temp-1 - giving a new GUID 63481f29f6a3aa6177210500b88bfabe to Sent Dec 3 15:10:50 cloud1 dovecot: doveadm(obfuscated)<336245><HrHeOPOjqmF1IQUAuIv6vg>: Panic: file dsync-brain-mailbox.c: line 851 (dsync_brain_slave_recv_mailbox): assertion failed: (memcmp(dsync_box->mailbox_guid, local_dsync_box.mailbox_guid, sizeof(dsync_box->mailbox_guid)) == 0) Dec 3 15:10:50 cloud1 dovecot: doveadm(obfuscated)<336245><HrHeOPOjqmF1IQUAuIv6vg>: Error: Raw backtrace: #0 fatal_handler_real[0x7fde7fd20060] -> #1 i_internal_fatal_handler[0x7fde7fd20190] -> #2 i_panic[0x7fde7fc731ff] -> #3 dsync_brain_slave_recv_mailbox[0x55dde7b22900] -> #4 dsync_brain_run[0x55dde7b20380] -> #5 dsync_brain_run_io[0x55dde7b20b50] -> #6 dsync_ibc_stream_input[0x55dde7b329c0] -> #7 io_loop_call_io[0x7fde7fd36500] -> #8 io_loop_handler_run_internal[0x7fde7fd37ac0] -> #9 io_loop_handler_run[0x7fde7fd365c0] -> #10 io_loop_run[0x7fde7fd36740] -> #11 cmd_dsync_server_run[0x55dde7b04f60] -> #12 doveadm_mail_next_user[0x55dde7b06850] -> #13 doveadm_cmd_ver2_to_mail_cmd_wrapper[0x55dde7b077e0] -> #14 doveadm_cmd_run_ver2[0x55dde7b17f00] -> #15 client_connection_tcp_input[0x55dde7b1c6b0] -> #16 io_loop_call_io[0x7fde7fd36500] -> #17 io_loop_handler_run_internal[0x7fde7fd37ac0] -> #18 io_loop_handler_run[0x7fde7fd365c0] -> #19 io_loop_run[0x7fde7fd36740] -> #20 master_service_run[0x7fde7fca87d0] -> #21 main[0x55dde7af7770] -> #22 __libc_start_main[0x7fde7f8f9fc0] -> #23 _start[0x55dde7af78d0] Dec 3 15:10:50 cloud1 dovecot: doveadm(obfuscated)<336245><HrHeOPOjqmF1IQUAuIv6vg>: Fatal: master: service(doveadm): child 336245 killed with signal 6 (core dumped) Dec 3 15:10:52 cloud1 dovecot: doveadm(obfuscated)<336253><2VTpM/ujqmF9IQUAuIv6vg>: Error: Duplicate mailbox GUID 63481f29f6a3aa6177210500b88bfabe for mailboxes INBOX/Sent and INBOX/Sent Messages-temp-1 - giving a new GUID cba35507fca3aa617d210500b88bfabe to INBOX/Sent Dec 3 15:10:58 cloud1 dovecot: doveadm(obfuscated)<336258><ykbQAAGkqmGCIQUAuIv6vg>: Error: Duplicate mailbox GUID dc3b4434fba3aa61660700009db5accb for mailboxes Sent and Sent Messages-temp-1 - giving a new GUID 60ad190102a4aa6182210500b88bfabe to Sent -- Daniel ------ Original Message ------ From: "Daniel Miller" <dmiller(a)amfes.com> To: "Daniel Miller" <dmiller(a)amfes.com>; dovecot(a)dovecot.org Sent: 12/3/2021 2:42:12 PM Subject: Re[2]: Replication weirdness >And...one more. > >I'm now seeing (again) messages like: > >Dec 3 14:29:14 cloud1 dovecot: >doveadm(obfuscated)<334017><e3FHNjmaqmHBGAUAuIv6vg>: Error: Duplicate >mailbox GUID bcb9ca36ae36aa617f0a00009db5accb for mailboxes INBOX/Sent >Messages and INBOX/Sent - giving a new GUID >fc30bd0a3a9aaa61c1180500b88bfabe to INBOX/Sent >Dec 3 14:38:59 cloud1 dovecot: >doveadm(obfuscated)<334394><an5KIoOcqmE6GgUAuIv6vg>: Error: Duplicate >mailbox GUID fc30bd0a3a9aaa61c1180500b88bfabe for mailboxes INBOX/Sent >Messages and INBOX/Sent - giving a new GUID >f4338038839caa613a1a0500b88bfabe to INBOX/Sent > >Having one message for the initial sync I suppose is reasonable. A >second...maybe? But I'm getting nervous I'm about to start seeing the >endless temp folders again. >-- >Daniel > >------ Original Message ------ >From: "Daniel Miller" <dmiller(a)amfes.com> >To: "Daniel Miller" <dmiller(a)amfes.com>; dovecot(a)dovecot.org >Sent: 12/3/2021 2:39:25 PM >Subject: Re: Replication weirdness > >>Another item. >> >>Again, it may be a 2.3.13 issue and I'm now on 2.3.17. But...I had >>problem when using the "-N" parameter for dsync. So - I just have >>(had): >> >>replication_dsync_parameters = -d -l 30 -U -x INBOX/virtual -x >>INBOX/shared >> >>Now that things are working - I wanted to have my other namespaces >>sync as well. So I went to: >> >>replication_dsync_parameters = -d -l 30 -U -n INBOX -n INBOX/Archives >>-n INBOX/Lists -x INBOX/virtual -x INBOX/shared >> >>This appears to be working (the sync is just starting)...but I'm >>seeing lock errors in the logs such as: >>Dec 3 14:34:24 bubba dovecot: >>doveadm(dmiller(a)amfes.com)<31785><TV+0LlGbqmEpfAAAnbWsyw>: Error: >>Couldn't lock /var/mail/amfes.com/dmiller/.dovecot-sync.lock: >>fcntl(/var/mail/amfes.com/dmiller/.dovecot-sync.lock, write-lock, >>F_SETLKW) locking failed: Timed out after 30 seconds (WRITE lock held >>by pid 31373) >> >>Checking the pid in question I see it's actively syncing a folder in >>my mailbox. So I'm guessing, purely guessing, that by having multiple >>namespaces explicitly directed to sync Dovecot is trying to start a >>sync process for each of those namespaces - but all of them share a >>common lock and therefore only one operation is allowed at a time. >> >>Am I correct, and whether or not I am - how can I correct these >>errors? Do I dare try going back to just "-N"? >> >>-- >>Daniel >> >>------ Original Message ------ >>From: "Daniel Miller" <dmiller(a)amfes.com> >>To: dovecot(a)dovecot.org >>Sent: 12/3/2021 2:16:28 PM >>Subject: Replication weirdness >> >>>First, I have to say this. After configuring everything correctly - >>>and that means *everything* correctly - Dovecot replication Just >>>Works. I'm not sure how (yes I do - Timo & Co. Magic) - but it does. >>>Real-time new sync is near instantaneous. >>> >>>Now the problem. Or the background for the problem. My primary server >>>uses sdbox for primary storage, mdbox for archival storage, and >>>fts-solr. I spun up a second server, using sdbox, mdbox, and >>>fts-flatcurve. My namespaces are as defined below. As best I can tell >>>(based on diff comparing two 'doveconf -n' outputs) my namespaces are >>>the same on both servers. >>> >>>namespace archives { >>> list = children >>> location = mdbox:/var/mail/%d/%n/Archives/mdbox >>> mailbox Unsorted { >>> auto = no >>> special_use = \Archive >>> } >>> prefix = INBOX/Archives/ >>> separator = / >>> subscriptions = no >>> type = private >>>} >>>namespace inbox { >>> alias_for = >>> hidden = no >>> inbox = yes >>> list = yes >>> location = >>> mailbox "Deleted Messages" { >>> auto = no >>> autoexpunge = 30 days >>> special_use = \Trash >>> } >>> mailbox Drafts { >>> auto = subscribe >>> special_use = \Drafts >>> } >>> mailbox Sent { >>> auto = subscribe >>> special_use = \Sent >>> } >>> mailbox Trash { >>> auto = subscribe >>> autoexpunge = 30 days >>> special_use = \Trash >>> } >>> prefix = INBOX/ >>> separator = / >>> subscriptions = no >>> type = private >>>} >>>namespace lists { >>> list = children >>> location = mdbox:/var/mail/%d/%n/Lists/mdbox >>> prefix = INBOX/Lists/ >>> separator = / >>> subscriptions = no >>> type = private >>>} >>>namespace subscriptions { >>> hidden = yes >>> list = no >>> location = >>> prefix = >>> separator = / >>> subscriptions = yes >>> type = private >>>} >>>namespace usershares { >>> list = yes >>> location = sdbox:/var/mail/%%d/%%n/sdbox:NO-NOSELECT >>> prefix = INBOX/shared/%%d/%%n/ >>> separator = / >>> subscriptions = no >>> type = shared >>>} >>>namespace virtual { >>> list = children >>> location = virtual:/var/mail/%d/%n/virtual >>> mailbox Flagged { >>> comment = All my flagged messages >>> special_use = \Flagged >>> } >>> prefix = INBOX/virtual/ >>> separator = / >>> subscriptions = no >>>} >>> >>>I also have: >>>plugin { >>> mailbox_alias_new = Sent Messages >>> mailbox_alias_new2 = Sent Items >>> mailbox_alias_new3 = Deleted Messages >>> mailbox_alias_old = Sent >>> mailbox_alias_old2 = Sent >>> mailbox_alias_old3 = Trash >>>} >>> >>>This setup worked fine with my single server. Then I enabled >>>replication - just on the primary. Dsync went to work (it seemed to >>>take forever for the initial sync but that's what happens with large >>>mailboxes and slow internet connections). >>> >>>The problem came up with certain subfolders. And I believe it only >>>happens with subfolders that have spaces in their names. I had two >>>user's mailboxes (under Sent), one of which had a "Sent Messages" >>>symlink alias for "Sent", that started generating tens or hundreds of >>>duplicates during sync. Fortunately those subfolders only had a few >>>mails in them. But I had trees looking like: >>> >>>[...] (below is under /var/mail/domain/user/sdbox/mailboxes/Sent/) >>>Proposal >>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-1-temp-f80b1a00ce9aa961a86-temp-2 >>>Proposal >>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-1-temp-f80b1a00ce9aa961a86-temp-3 >>>Proposal >>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-023fa4271c9ca9611ade0400b88bfabe >>>Proposal >>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-023fa4271c9ca9611ad-temp-1 >>>Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-1 >>>Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-2 >>>Proposal >>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-2-temp-1-temp-1 >>>Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-3 >>>Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-4 >>>Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-5 >>>Proposal >>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-e2aa0f35c99ba961356500009db5accb >>>[...] >>> >>>I kept stopping, cleaning up the folders, and re-starting - and they >>>kept regenerating. I tried renaming the folders to eliminate the >>>spaces and I think that helped in one case - for the others I just >>>moved the folders outside of the mail area completely to let the sync >>>finish. >>> >>>Now that it's been stable for a day or two - I enabled sync in the >>>other direction. And after setting *all* the required parameters >>>instead of just most of them...it's working. But...I'm nervous about >>>moving the problem folders back over. I will say, if it makes any >>>difference, my primary server *was* running version 2.3.13 and I just >>>updated it to 2.3.17. The remote is also 2.3.17. >>> >>>-- >>>Daniel

1 0

Re[2]: Replication weirdness
by Daniel Miller 04 Dec '21

04 Dec '21

And...one more. I'm now seeing (again) messages like: Dec 3 14:29:14 cloud1 dovecot: doveadm(obfuscated)<334017><e3FHNjmaqmHBGAUAuIv6vg>: Error: Duplicate mailbox GUID bcb9ca36ae36aa617f0a00009db5accb for mailboxes INBOX/Sent Messages and INBOX/Sent - giving a new GUID fc30bd0a3a9aaa61c1180500b88bfabe to INBOX/Sent Dec 3 14:38:59 cloud1 dovecot: doveadm(obfuscated)<334394><an5KIoOcqmE6GgUAuIv6vg>: Error: Duplicate mailbox GUID fc30bd0a3a9aaa61c1180500b88bfabe for mailboxes INBOX/Sent Messages and INBOX/Sent - giving a new GUID f4338038839caa613a1a0500b88bfabe to INBOX/Sent Having one message for the initial sync I suppose is reasonable. A second...maybe? But I'm getting nervous I'm about to start seeing the endless temp folders again. -- Daniel ------ Original Message ------ From: "Daniel Miller" <dmiller(a)amfes.com> To: "Daniel Miller" <dmiller(a)amfes.com>; dovecot(a)dovecot.org Sent: 12/3/2021 2:39:25 PM Subject: Re: Replication weirdness >Another item. > >Again, it may be a 2.3.13 issue and I'm now on 2.3.17. But...I had >problem when using the "-N" parameter for dsync. So - I just have >(had): > >replication_dsync_parameters = -d -l 30 -U -x INBOX/virtual -x >INBOX/shared > >Now that things are working - I wanted to have my other namespaces sync >as well. So I went to: > >replication_dsync_parameters = -d -l 30 -U -n INBOX -n INBOX/Archives >-n INBOX/Lists -x INBOX/virtual -x INBOX/shared > >This appears to be working (the sync is just starting)...but I'm seeing >lock errors in the logs such as: >Dec 3 14:34:24 bubba dovecot: >doveadm(dmiller(a)amfes.com)<31785><TV+0LlGbqmEpfAAAnbWsyw>: Error: >Couldn't lock /var/mail/amfes.com/dmiller/.dovecot-sync.lock: >fcntl(/var/mail/amfes.com/dmiller/.dovecot-sync.lock, write-lock, >F_SETLKW) locking failed: Timed out after 30 seconds (WRITE lock held >by pid 31373) > >Checking the pid in question I see it's actively syncing a folder in my >mailbox. So I'm guessing, purely guessing, that by having multiple >namespaces explicitly directed to sync Dovecot is trying to start a >sync process for each of those namespaces - but all of them share a >common lock and therefore only one operation is allowed at a time. > >Am I correct, and whether or not I am - how can I correct these errors? >Do I dare try going back to just "-N"? > >-- >Daniel > >------ Original Message ------ >From: "Daniel Miller" <dmiller(a)amfes.com> >To: dovecot(a)dovecot.org >Sent: 12/3/2021 2:16:28 PM >Subject: Replication weirdness > >>First, I have to say this. After configuring everything correctly - >>and that means *everything* correctly - Dovecot replication Just >>Works. I'm not sure how (yes I do - Timo & Co. Magic) - but it does. >>Real-time new sync is near instantaneous. >> >>Now the problem. Or the background for the problem. My primary server >>uses sdbox for primary storage, mdbox for archival storage, and >>fts-solr. I spun up a second server, using sdbox, mdbox, and >>fts-flatcurve. My namespaces are as defined below. As best I can tell >>(based on diff comparing two 'doveconf -n' outputs) my namespaces are >>the same on both servers. >> >>namespace archives { >> list = children >> location = mdbox:/var/mail/%d/%n/Archives/mdbox >> mailbox Unsorted { >> auto = no >> special_use = \Archive >> } >> prefix = INBOX/Archives/ >> separator = / >> subscriptions = no >> type = private >>} >>namespace inbox { >> alias_for = >> hidden = no >> inbox = yes >> list = yes >> location = >> mailbox "Deleted Messages" { >> auto = no >> autoexpunge = 30 days >> special_use = \Trash >> } >> mailbox Drafts { >> auto = subscribe >> special_use = \Drafts >> } >> mailbox Sent { >> auto = subscribe >> special_use = \Sent >> } >> mailbox Trash { >> auto = subscribe >> autoexpunge = 30 days >> special_use = \Trash >> } >> prefix = INBOX/ >> separator = / >> subscriptions = no >> type = private >>} >>namespace lists { >> list = children >> location = mdbox:/var/mail/%d/%n/Lists/mdbox >> prefix = INBOX/Lists/ >> separator = / >> subscriptions = no >> type = private >>} >>namespace subscriptions { >> hidden = yes >> list = no >> location = >> prefix = >> separator = / >> subscriptions = yes >> type = private >>} >>namespace usershares { >> list = yes >> location = sdbox:/var/mail/%%d/%%n/sdbox:NO-NOSELECT >> prefix = INBOX/shared/%%d/%%n/ >> separator = / >> subscriptions = no >> type = shared >>} >>namespace virtual { >> list = children >> location = virtual:/var/mail/%d/%n/virtual >> mailbox Flagged { >> comment = All my flagged messages >> special_use = \Flagged >> } >> prefix = INBOX/virtual/ >> separator = / >> subscriptions = no >>} >> >>I also have: >>plugin { >> mailbox_alias_new = Sent Messages >> mailbox_alias_new2 = Sent Items >> mailbox_alias_new3 = Deleted Messages >> mailbox_alias_old = Sent >> mailbox_alias_old2 = Sent >> mailbox_alias_old3 = Trash >>} >> >>This setup worked fine with my single server. Then I enabled >>replication - just on the primary. Dsync went to work (it seemed to >>take forever for the initial sync but that's what happens with large >>mailboxes and slow internet connections). >> >>The problem came up with certain subfolders. And I believe it only >>happens with subfolders that have spaces in their names. I had two >>user's mailboxes (under Sent), one of which had a "Sent Messages" >>symlink alias for "Sent", that started generating tens or hundreds of >>duplicates during sync. Fortunately those subfolders only had a few >>mails in them. But I had trees looking like: >> >>[...] (below is under /var/mail/domain/user/sdbox/mailboxes/Sent/) >>Proposal >>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-1-temp-f80b1a00ce9aa961a86-temp-2 >>Proposal >>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-1-temp-f80b1a00ce9aa961a86-temp-3 >>Proposal >>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-023fa4271c9ca9611ade0400b88bfabe >>Proposal >>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-023fa4271c9ca9611ad-temp-1 >>Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-1 >>Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-2 >>Proposal >>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-2-temp-1-temp-1 >>Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-3 >>Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-4 >>Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-5 >>Proposal >>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-e2aa0f35c99ba961356500009db5accb >>[...] >> >>I kept stopping, cleaning up the folders, and re-starting - and they >>kept regenerating. I tried renaming the folders to eliminate the >>spaces and I think that helped in one case - for the others I just >>moved the folders outside of the mail area completely to let the sync >>finish. >> >>Now that it's been stable for a day or two - I enabled sync in the >>other direction. And after setting *all* the required parameters >>instead of just most of them...it's working. But...I'm nervous about >>moving the problem folders back over. I will say, if it makes any >>difference, my primary server *was* running version 2.3.13 and I just >>updated it to 2.3.17. The remote is also 2.3.17. >> >>-- >>Daniel

1 0

Re: Replication weirdness
by Daniel Miller 04 Dec '21

04 Dec '21

Another item. Again, it may be a 2.3.13 issue and I'm now on 2.3.17. But...I had problem when using the "-N" parameter for dsync. So - I just have (had): replication_dsync_parameters = -d -l 30 -U -x INBOX/virtual -x INBOX/shared Now that things are working - I wanted to have my other namespaces sync as well. So I went to: replication_dsync_parameters = -d -l 30 -U -n INBOX -n INBOX/Archives -n INBOX/Lists -x INBOX/virtual -x INBOX/shared This appears to be working (the sync is just starting)...but I'm seeing lock errors in the logs such as: Dec 3 14:34:24 bubba dovecot: doveadm(dmiller(a)amfes.com)<31785><TV+0LlGbqmEpfAAAnbWsyw>: Error: Couldn't lock /var/mail/amfes.com/dmiller/.dovecot-sync.lock: fcntl(/var/mail/amfes.com/dmiller/.dovecot-sync.lock, write-lock, F_SETLKW) locking failed: Timed out after 30 seconds (WRITE lock held by pid 31373) Checking the pid in question I see it's actively syncing a folder in my mailbox. So I'm guessing, purely guessing, that by having multiple namespaces explicitly directed to sync Dovecot is trying to start a sync process for each of those namespaces - but all of them share a common lock and therefore only one operation is allowed at a time. Am I correct, and whether or not I am - how can I correct these errors? Do I dare try going back to just "-N"? -- Daniel ------ Original Message ------ From: "Daniel Miller" <dmiller(a)amfes.com> To: dovecot(a)dovecot.org Sent: 12/3/2021 2:16:28 PM Subject: Replication weirdness >First, I have to say this. After configuring everything correctly - and >that means *everything* correctly - Dovecot replication Just Works. I'm >not sure how (yes I do - Timo & Co. Magic) - but it does. Real-time new >sync is near instantaneous. > >Now the problem. Or the background for the problem. My primary server >uses sdbox for primary storage, mdbox for archival storage, and >fts-solr. I spun up a second server, using sdbox, mdbox, and >fts-flatcurve. My namespaces are as defined below. As best I can tell >(based on diff comparing two 'doveconf -n' outputs) my namespaces are >the same on both servers. > >namespace archives { > list = children > location = mdbox:/var/mail/%d/%n/Archives/mdbox > mailbox Unsorted { > auto = no > special_use = \Archive > } > prefix = INBOX/Archives/ > separator = / > subscriptions = no > type = private >} >namespace inbox { > alias_for = > hidden = no > inbox = yes > list = yes > location = > mailbox "Deleted Messages" { > auto = no > autoexpunge = 30 days > special_use = \Trash > } > mailbox Drafts { > auto = subscribe > special_use = \Drafts > } > mailbox Sent { > auto = subscribe > special_use = \Sent > } > mailbox Trash { > auto = subscribe > autoexpunge = 30 days > special_use = \Trash > } > prefix = INBOX/ > separator = / > subscriptions = no > type = private >} >namespace lists { > list = children > location = mdbox:/var/mail/%d/%n/Lists/mdbox > prefix = INBOX/Lists/ > separator = / > subscriptions = no > type = private >} >namespace subscriptions { > hidden = yes > list = no > location = > prefix = > separator = / > subscriptions = yes > type = private >} >namespace usershares { > list = yes > location = sdbox:/var/mail/%%d/%%n/sdbox:NO-NOSELECT > prefix = INBOX/shared/%%d/%%n/ > separator = / > subscriptions = no > type = shared >} >namespace virtual { > list = children > location = virtual:/var/mail/%d/%n/virtual > mailbox Flagged { > comment = All my flagged messages > special_use = \Flagged > } > prefix = INBOX/virtual/ > separator = / > subscriptions = no >} > >I also have: >plugin { > mailbox_alias_new = Sent Messages > mailbox_alias_new2 = Sent Items > mailbox_alias_new3 = Deleted Messages > mailbox_alias_old = Sent > mailbox_alias_old2 = Sent > mailbox_alias_old3 = Trash >} > >This setup worked fine with my single server. Then I enabled >replication - just on the primary. Dsync went to work (it seemed to >take forever for the initial sync but that's what happens with large >mailboxes and slow internet connections). > >The problem came up with certain subfolders. And I believe it only >happens with subfolders that have spaces in their names. I had two >user's mailboxes (under Sent), one of which had a "Sent Messages" >symlink alias for "Sent", that started generating tens or hundreds of >duplicates during sync. Fortunately those subfolders only had a few >mails in them. But I had trees looking like: > >[...] (below is under /var/mail/domain/user/sdbox/mailboxes/Sent/) >Proposal >Requests-temp-c6e003375e64a961c93d00009db5accb-temp-1-temp-f80b1a00ce9aa961a86-temp-2 >Proposal >Requests-temp-c6e003375e64a961c93d00009db5accb-temp-1-temp-f80b1a00ce9aa961a86-temp-3 >Proposal >Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-023fa4271c9ca9611ade0400b88bfabe >Proposal >Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-023fa4271c9ca9611ad-temp-1 >Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-1 >Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-2 >Proposal >Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-2-temp-1-temp-1 >Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-3 >Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-4 >Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-5 >Proposal >Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-e2aa0f35c99ba961356500009db5accb >[...] > >I kept stopping, cleaning up the folders, and re-starting - and they >kept regenerating. I tried renaming the folders to eliminate the spaces >and I think that helped in one case - for the others I just moved the >folders outside of the mail area completely to let the sync finish. > >Now that it's been stable for a day or two - I enabled sync in the >other direction. And after setting *all* the required parameters >instead of just most of them...it's working. But...I'm nervous about >moving the problem folders back over. I will say, if it makes any >difference, my primary server *was* running version 2.3.13 and I just >updated it to 2.3.17. The remote is also 2.3.17. > >-- >Daniel

1 0

Replication weirdness
by Daniel Miller 04 Dec '21

04 Dec '21

First, I have to say this. After configuring everything correctly - and that means *everything* correctly - Dovecot replication Just Works. I'm not sure how (yes I do - Timo & Co. Magic) - but it does. Real-time new sync is near instantaneous. Now the problem. Or the background for the problem. My primary server uses sdbox for primary storage, mdbox for archival storage, and fts-solr. I spun up a second server, using sdbox, mdbox, and fts-flatcurve. My namespaces are as defined below. As best I can tell (based on diff comparing two 'doveconf -n' outputs) my namespaces are the same on both servers. namespace archives { list = children location = mdbox:/var/mail/%d/%n/Archives/mdbox mailbox Unsorted { auto = no special_use = \Archive } prefix = INBOX/Archives/ separator = / subscriptions = no type = private } namespace inbox { alias_for = hidden = no inbox = yes list = yes location = mailbox "Deleted Messages" { auto = no autoexpunge = 30 days special_use = \Trash } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe autoexpunge = 30 days special_use = \Trash } prefix = INBOX/ separator = / subscriptions = no type = private } namespace lists { list = children location = mdbox:/var/mail/%d/%n/Lists/mdbox prefix = INBOX/Lists/ separator = / subscriptions = no type = private } namespace subscriptions { hidden = yes list = no location = prefix = separator = / subscriptions = yes type = private } namespace usershares { list = yes location = sdbox:/var/mail/%%d/%%n/sdbox:NO-NOSELECT prefix = INBOX/shared/%%d/%%n/ separator = / subscriptions = no type = shared } namespace virtual { list = children location = virtual:/var/mail/%d/%n/virtual mailbox Flagged { comment = All my flagged messages special_use = \Flagged } prefix = INBOX/virtual/ separator = / subscriptions = no } I also have: plugin { mailbox_alias_new = Sent Messages mailbox_alias_new2 = Sent Items mailbox_alias_new3 = Deleted Messages mailbox_alias_old = Sent mailbox_alias_old2 = Sent mailbox_alias_old3 = Trash } This setup worked fine with my single server. Then I enabled replication - just on the primary. Dsync went to work (it seemed to take forever for the initial sync but that's what happens with large mailboxes and slow internet connections). The problem came up with certain subfolders. And I believe it only happens with subfolders that have spaces in their names. I had two user's mailboxes (under Sent), one of which had a "Sent Messages" symlink alias for "Sent", that started generating tens or hundreds of duplicates during sync. Fortunately those subfolders only had a few mails in them. But I had trees looking like: [...] (below is under /var/mail/domain/user/sdbox/mailboxes/Sent/) Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-1-temp-f80b1a00ce9aa961a86-temp-2 Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-1-temp-f80b1a00ce9aa961a86-temp-3 Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-023fa4271c9ca9611ade0400b88bfabe Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-023fa4271c9ca9611ad-temp-1 Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-1 Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-2 Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-2-temp-1-temp-1 Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-3 Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-4 Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-5 Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-e2aa0f35c99ba961356500009db5accb [...] I kept stopping, cleaning up the folders, and re-starting - and they kept regenerating. I tried renaming the folders to eliminate the spaces and I think that helped in one case - for the others I just moved the folders outside of the mail area completely to let the sync finish. Now that it's been stable for a day or two - I enabled sync in the other direction. And after setting *all* the required parameters instead of just most of them...it's working. But...I'm nervous about moving the problem folders back over. I will say, if it makes any difference, my primary server *was* running version 2.3.13 and I just updated it to 2.3.17. The remote is also 2.3.17. -- Daniel

1 0

Searching 30 GB mailbox
by Einar Bjarni Halldórsson 03 Dec '21

03 Dec '21

Hi, We're migrating our mailboxes from Zimbra to dovecot, running on FreeBSD 12.2. We're using mdbox and solr for fts. dovecot version 2.3.17. One of our mailboxes gets a bcc of every outgoing mail from our system and it currently holds ~4.5 million messages taking 30 GB. One of the ways we use the mailbox is that when outgoing mail is sent, we store the Message-ID in our database, and in our admin interface we can open the mail and it's fetched from IMAP by doing a 'SEARCH HEADER Message-ID <MSG_ID>'. In Zimbra this was reasonably fast, but after migrating the mailbox to dovecot it's 30 seconds which I think we can reduce. After turning on mail_debug I see this in our log https://pastebin.com/kP9H7gSB Looks like solr finishes searching instantly, then there's ~30 seconds of silence in the logs, and then more log lines about fetching data from mail cache. The same thing happens if I use telnet and just issue a 'SEARCH HEADER...' command. How can I find out what dovecot is doing in those 30 seconds? .einar

5 14

Expunged message reappeared
by Claudio Corvino 03 Dec '21

03 Dec '21

Hi, I have two IMAP/LMTP Dovecot server in replica (version 2.3.4.1), I use LDAP/AD for /userdb, /replica is working, but sometimes I get these errors into log: Dec 3 15:47:15 xxx dovecot: imap(xxx)<28251><TOSxmj7SPRYloY5/>: Warning: Maildir /mnt/mail-storage-lv0007/xxx/Maildir: Expunged message reappeared, giving a new UID (old uid=233140, file=1638540323.M588041P27708.xxx,S=84376,W=85507:2,) The user delete the message and then the message reappears into mail client after one second. Does anybody knows how can I fix it? Thanks in advance Regards

1 1

Re: new bee needs starter docs
by Gene Heskett 03 Dec '21

03 Dec '21

On Fri, 3 Dec, 2021 at 3:50 AM, Christian Mack <christian.mack(a)uni-konstanz.de> wrote: To: dovecot(a)dovecot.org Hello What you need is probably 'doveadm sync'. Check its manual with man doveadm-sync I did, that's equ to my climbing El Capitan at 87 yo. 'taint gonna happen. So I think I'll try to make my old method work, so back to the kde-pim list. Kind regards, Christian Mack Thank you Christian

1 0

Issue with SCRAM-SHA Authorization
by Thomas Schmid 03 Dec '21

03 Dec '21

Hi, I was debugging a bug report for my sieve editor implementation concerning an issue with SCRAM-SHA Authorization. But I am a bit unsure about my findings. It seems to be a server side bug. But I am wondering if I missed something. What puzzles me a bit is that SCRAM-SHA is out since ages and obviously no one ran into this issue. Which feels odd. When I try to connect to a dovecot server with enabled Authorization, then SCRAM SHA1 or SHA256 fail with a channel binding error. Authorization via SASL PLAIN works perfectly fine. So I digged into the logs. The trace is below also my findings/conclusion. The username and authorization in the trace are set to "user" the password is "pencil". Nov 24 14:00:06 auth: Debug: client in: AUTH 1 SCRAM-SHA-256 service=sieve secured=tlssession=sI9yRonRZISsEQAB lip=172.17.0.2 rip=172.17.0.1 lport=4190 rport=33892 resp=bixhPXVzZXIsbj11c2VyLHI9ZmEzZGY1NjNlZjczZTY3YjQzZThhZWRiZjUzNGI1NWIxNzIwNzU3OThjZmJiMjExNmMyMTNkMWM4NDE4MmZkOQ== (previous base64 data may contain sensitive data) Nov 24 14:00:06 auth: Debug: passwd-file(user,172.17.0.1,<sI9yRonRZISsEQAB>): Performing passdb lookup Nov 24 14:00:06 auth: Debug: passwd-file(user,172.17.0.1,<sI9yRonRZISsEQAB>): lookup: user=user file=/etc/dovecot/users Nov 24 14:00:06 auth: Debug: passwd-file(user,172.17.0.1,<sI9yRonRZISsEQAB>): Generating SCRAM-SHA-256 from user 'user', password 'pencil' Nov 24 14:00:06 auth: Debug: passwd-file(user,172.17.0.1,<sI9yRonRZISsEQAB>): Finished passdb lookup Nov 24 14:00:06 auth: Debug: Credentials: 343039362c326b3934364452546c326431765a37434b6d556c32513d3d2c46444d364f7173577035464c446e394151666554316547585045427a47566d6965673842427331456d37633d2c79766e5a4169376250392f59706c4a71597872356a79794f7a6e4c664730667636485155325a7a6975376b3d Nov 24 14:00:06 auth: Debug: client passdb out: CONT 1 cj1mYTNkZjU2M2VmNzNlNjdiNDNlOGFlZGJmNTM0YjU1YjE3MjA3NTc5OGNmYmIyMTE2YzIxM2QxYzg0MTgyZmQ5J2Q9NCskV2NuWEFVTnZxOU1EZENgM2UheVguXFw3O2JgKlg0X29gKDtBXnJrTi1xUmQ2IXgiQX5+eGU8ZlJHWSxzPTJrOTQ2RFJUbDJkMXZaN0NLbVVsMlE9PSxpPTQwOTY= Nov 24 14:00:06 auth: Debug: client in: CONT 1 Yz1iaXhoUFhWelpYSXMscj1mYTNkZjU2M2VmNzNlNjdiNDNlOGFlZGJmNTM0YjU1YjE3MjA3NTc5OGNmYmIyMTE2YzIxM2QxYzg0MTgyZmQ5J2Q9NCskV2NuWEFVTnZxOU1EZENgM2UheVguXFw3O2JgKlg0X29gKDtBXnJrTi1xUmQ2IXgiQX5+eGU8ZlJHWSxwPUcvZGZWUUlGZy9NMkpSMlpEMXM0cms4MS9jTmFMa0tuMzZFYzFlTTN1enc9 (previous base64 data may contain sensitive data) Nov 24 14:00:06 auth: Info: scram-sha-256(user,172.17.0.1,<sI9yRonRZISsEQAB>): Invalid channel binding data Nov 24 14:00:06 auth: Debug: auth(user,172.17.0.1,<sI9yRonRZISsEQAB>): Auth request finished Nov 24 14:00:08 auth: Debug: client passdb out: FAIL 1 user=user Nov 24 14:00:08 managesieve-login: Info: Disconnected: Aborted login by logging out (auth failed, 1 attempts in 2 secs): user=<user>, method=SCRAM-SHA-256, rip=172.17.0.1, lip=172.17.0.2, TLS, session=<sI9yRonRZISsEQAB> Nov 24 14:00:08 managesieve-login: Debug: SSL alert: close notify The matching trace from the client, a sieve editor (https://github.com/thsmi/sieve) is as follows: [15:000:06.192 kw53213a-qc7kf99m1lp] Client -> Server: AUTHENTICATE "SCRAM-SHA-256" "bixhPXVzZXIsbj11c2VyLHI9ZmEzZGY1NjNlZjczZTY3YjQzZThhZWRiZjUzNGI1NWIxNzIwNzU3OThjZmJiMjExNmMyMTNkMWM4NDE4MmZkOQ==" [15:000:06.202 kw53213a-qc7kf99m1lp] Server -> Client "cj1mYTNkZjU2M2VmNzNlNjdiNDNlOGFlZGJmNTM0YjU1YjE3MjA3NTc5OGNmYmIyMTE2YzIxM2QxYzg0MTgyZmQ5J2Q9NCskV2NuWEFVTnZxOU1EZENgM2UheVguXFw3O2JgKlg0X29gKDtBXnJrTi1xUmQ2IXgiQX5+eGU8ZlJHWSxzPTJrOTQ2RFJUbDJkMXZaN0NLbVVsMlE9PSxpPTQwOTY=" [15:000:06.209 kw53213a-qc7kf99m1lp] Client -> Server: "Yz1iaXhoUFhWelpYSXMscj1mYTNkZjU2M2VmNzNlNjdiNDNlOGFlZGJmNTM0YjU1YjE3MjA3NTc5OGNmYmIyMTE2YzIxM2QxYzg0MTgyZmQ5J2Q9NCskV2NuWEFVTnZxOU1EZENgM2UheVguXFw3O2JgKlg0X29gKDtBXnJrTi1xUmQ2IXgiQX5+eGU8ZlJHWSxwPUcvZGZWUUlGZy9NMkpSMlpEMXM0cms4MS9jTmFMa0tuMzZFYzFlTTN1enc9" [15:000:08.215 kw53213a-qc7kf99m1lp] Server -> Client NO "Authentication failed." According to the RFC (https://datatracker.ietf.org/doc/html/rfc5802) the initial request is defined as: (("p=" cb-name) / "n" / "y") "," [ authzid ] "," client-first-message-bare This means the decoded message from the trace is: n,a=user,n=user,r=fa3df563ef73e67b43e8aedbf534b55b172075798cfbb2116c213d1c84182fd9 The final request (which is rejected by the server with the binding error) is defined as : client-final-message-without-proof = channel-binding "," nonce [","extensions] or client-final-message = client-final-message-without-proof "," proof So the request from the trace decodes into: c=bixhPXVzZXIs,r=fa3df563ef73e67b43e8aedbf534b55b172075798cfbb2116c213d1c84182fd9'd=4+$WcnXAUNvq9MDdC`3e!yX.\\7;b`*X4_o`(;A^rkN-qRd6!x"A~~xe<fRGY,p=G/dfVQIFg/M2JR2ZD1s4rk81/cNaLkKn36Ec1eM3uzw= The channel-binding and cbind-input part are defined as: channel-binding = "c=" base64(cbind-input) cbind-input = (("p=" cb-name) / "n" / "y") "," [ authzid ] "," [ cbind-data ] where cbind-data has to be absent by definition as dovecot does not support channel binding so no "p=" is possible and thus no cbind-data. This means c=bixhPXVzZXI decodes into. n,a=user, And this is where it gets strange. The dovecot code section which throws the error, implements the following: https://github.com/dovecot/core/blob/a5209c83c3a82386c94d466eec5fea394973e8… cbind_input = t_strconcat(request->gs2_cbind_flag, ",,", NULL); str = t_str_new(MAX_BASE64_ENCODED_SIZE(strlen(cbind_input))); str_append(str, "c="); base64_encode(cbind_input, strlen(cbind_input), str); if (strcmp(fields[0], str_c(str)) != 0) { *error_r = "Invalid channel binding data"; return FALSE; } As you can see it uses the bind flag which was saved to the request. But instead of the authzid, it uses always an hardcoded empty string. Thus cbind-input is "n,," instead of "n,a=user," and results in the request being rejected with an "Invalid channel binding data". Which is on the one hand a funny message because dovecot does not support channel binding at all, as describe in https://github.com/dovecot/core/blob/a5209c83c3a82386c94d466eec5fea394973e8… but it also on the other hand somehow correct because cbind-input string does not match. Which is an illegal state during channel binding negotiation which should not happen. As said previously, it looks to me like a server side bug. Or did I miss something special case in the RFC? Kind Regards Thomas Schmid

2 1

LDAP Help
by Günther J. Niederwimmer 03 Dec '21

03 Dec '21

Hello Dovecot professionals, I have a working user authentication with LDAP, now I want to allow the users to use mailAterneteAddress for their account, unfortunately I can't find any filter settings for dovecot that this works? I just can't find the right settings for LDAP (FreeIPA). Does anyone of you have any hints or links so that I can get on with it. Somehow I don't understand how I can umconvigure the dovecot-ldap.conf.ext Thank you for your help. -- mit freundlichen Grüßen / best regards Günther J. Niederwimmer

4 3

new bee needs starter docs
by Gene Heskett 03 Dec '21

03 Dec '21

Greetings all' Brand New today install of debian bullseye. I have looked at you doc pages, but don't see a good tut for a newbie to use for setting it up the first time ever. I have version 2.3.13 (89f716dc2) from the debian bullseye distro. What I want is to pull from my ISP account, which is also running dovecot, to a local mailfile. Or I can do that with fetchmail, its been doing that for a decade already. Its currently using procmail to run stuff thru spamassassin and clamd depositing the survivors into a /var/mail/mailfile, which the older tde kmail then pulled and sorted into folders holding maildirs. But I can't get tde to install on bullseye. Kudo's for any help you can supply. Cheers, Gene

2 1

execve(/usr/bin/sieve-test) failed: Argument list too long
by Patrick Cernko 03 Dec '21

03 Dec '21

Hi Dovecot developers, while debugging the above error message from sieve-test, I found out, that the content of directive ssl_ca is added as env var SSL_CA by doveconf on execve and sieve-test now uses doveconf. In our setup, ssl_ca is set to ssl_ca = </etc/ssl/certs/ca-certificates.crt on our director servers. We have backend servers with certificates signed by two different CAs and to avoid problems if a backend switches to a different CA, I decided to allow all "known" CAs. The corresponding env var SSL_CA has more than 230500 bytes, which causes execve to fail with error E2BIG. I found a workaround for the problem by setting ssl_ca = </etc/dovecot/backendCAs.pem Where this file contains only the two CAs used atm. However I would like to request a fix for this issue as others might also want to have all "known" CAs set for dovecot director backend connections. Best, -- Patrick Cernko <pcernko(a)mpi-klsb.mpg.de> +49 681 9325 5815 Joint Administration: Information Services and Technology Max-Planck-Institute fuer Informatik & Softwaresysteme

2 1