- dovecot - dovecot.org

We couldn't drop root group privileges
by forumforeign 01 Feb '24

01 Feb '24

Hello. I have - dovecot 2.3.21 (also tried 2.3.5) - postfix 3.8.5 (also tried 3.8.4) It's a new setup where I use postfix + dovecot-delivery for delivery to local mailbox. At logs I have an error and mail deffers in queue: dovecot: [ID 702911 mail.crit] lda(poli(a)domain.com)<7808>: Fatal: We couldn't drop root group privileges (wanted=6(mail), gid=0(root), egid=0(root)) Postfix and dovecot start from root UID, but user dovecot/postfix has corresponding groups to run as specific group: root@solaris:# id -a dovecot uid=110(dovecot) gid=110(dovecot) groups=110(dovecot),6(mail) root@solaris:# id -a postfix uid=26(postfix) gid=26(postfix) groups=26(postfix),6(mail) root@solaris:# id -a root uid=0(root) gid=0(root) groups=0(root),1(other),2(bin),3(sys),4(adm),6(mail),7(tty),8(lp),12(daemon) Also, when I run a dtrace (a system call trace mechanism) I see, that dovecot-lda runs as group "mail" (gid=6), so, there isn't any problem, but dovecot thinks another: UID GID PID PPID ARGS 0 26 7719 7638 pipe -n dovecot -t unix flags=DRhu user=nobody:mail argv=/usr/libexec/dovecot/d 60001 6 7720 7718 /usr/libexec/dovecot/dovecot-lda -f mega(a)domain.com -d poli(a)domain.com 60001 6 7720 7718 /usr/bin/amd64/doveconf -f service=lda -c /etc/dovecot/dovecot.conf -m lda -e / 60001 6 7720 7718 /usr/libexec/dovecot/dovecot-lda -f mega(a)domain.com -d poli(a)domain.com What exactly dovecot wants and how to solve this error? Here is part of "dovecot -n" output which is corresponding to user/group/lda: # 2.3.5.1 (7ec6d0ade): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.6 (92dc263a) # OS: SunOS 5.11 i86pc # Hostname: solaris auth_debug = yes auth_mechanisms = plain login auth_verbose = yes default_process_limit = 99 disable_plaintext_auth = no first_valid_gid = 6 first_valid_uid = 60001 last_valid_gid = 6 last_valid_uid = 60001 mail_access_groups = mail mail_debug = yes mail_gid = 6 mail_location = /var/mail/vmail/%u@%d mail_max_userip_connections = 99 mail_privileged_group = mail mail_uid = 60001 maildir_very_dirty_syncs = yes ... service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } ... protocol lda { mail_plugins = " sieve" postmaster_address = postmaster } PS. Also, I have aother box with very old setup (dovecot 2.2.27) and it works with the same configuration without any errors. I thought that this is OS specific problem and tried on the same version OS run a dovecot 2.3.21, but still had an errors.

1 1

Emails automatically thread by subject, no matter how old or unrelated
by wakod67943＠flexvio.com 01 Feb '24

01 Feb '24

To preface, I’m using the Crossbox mail client hosted by MXroute. I was directed to Dovecot support when I made my inquiry to the former’s developers. Apparently, when you write an email subject that is verbatim to another, previously sent email, the two become linked in a conversation thread. I could have an email from 1996 titled “Groceries” and if I make one today titled “Groceries” my inbox would have them connected as one long thread. I’m getting email threads in the 100s because of this. Crossbox people have told me it’s not something they have control over. They mentioned it being a Dovecot problem. Has anyone encountered this? It would be tremendously inconvenient to ensure that every email I ever send from now on has a unique subject so to as not have them threaded together. Let me be clear, email threading and conversation views are extremely useful. I just want them to be…relevant to the chain of emails that are being looked at. Is there a way to group threads by unique header information? It is becoming borderline unusable to sift through invoices.

3 2

JMAP support?
by Mark Constable 31 Jan '24

31 Jan '24

On Fri Jan 25 2019 Aki wrote: > There is no JMAP support in any dovecot version yet. Two years on so what is the status of JMAP support in Dovecot now?

7 10

doveadm sync failed after adding "mechanisms = plain login" to passdb
by James 31 Jan '24

31 Jan '24

Hello, After adding `mechanisms = plain login` to passdb (passwd-file), `doveadm -D sync -u e(a)example.com -d -N -l 30 -U` failed with ``` Jan 26 06:49:22 doveadm(e(a)example.com): Error: remote(server2.example.com:61526): doveadm(1.1.1.1,e(a)example.com): auth-master: passdb lookup(e(a)example.com): Auth PASS lookup failed Jan 26 06:49:22 doveadm(e(a)example.com): Error: remote(server2.example.com:61526): doveadm(1.1.1.1,e(a)example.com): /run/dovecot/auth-userdb: passdb lookup failed (to see if user is proxied, because doveadm_port is set) ``` With `auth_debug=yes`, I found these lines. ``` Jan 26 04:55:37 server2 dovecot: auth: Debug: skipping passdb: mechanism filtered Jan 26 04:55:37 server2 dovecot: auth: Error: All password databases were skipped ``` What should I do to fix it without deleting `mechanisms = plain login`? More information could be found on [this link](https://github.com/orgs/docker-mailserver/discussions/3836#discussion…. Thanks

1 0

Re: JMAP support?
by Marcel Schmidt 30 Jan '24

30 Jan '24

Hi, is there any progress on this? Since the IETF draft is long completed, will you integrate JMAP in a coming dovecot version or is this topic completely abandoned? Marcel Hi, is there any progress on this? Since the IETF draft is long completed, will you integrate JMAP in a coming dovecot version or is this topic completely abandoned? Marcel

1 0

One Way sync is deleting emails
by Steve Moser 30 Jan '24

30 Jan '24

Hello, I am hoping that you can help me. I am running this command on my main email server, one way backup/sync to the backup server. sudo doveadm sync -1 -A remote:root@x.x.x.x x.x.x.x is my remote server. I will add a new email on the main, run the command and it shows up on the backup. - Great! Now I delete that email from the main, run the command and the email is removed from the backup. That should not delete anything from the backup, correct? I prefer Not to delete anything, only update/add. Do you see what I am doing wrong? Thank You!!!! Here my installed versions dovecot-core 1:2.3.16+dfsg1-3ubuntu2.2 dovecot-imapd 1:2.3.16+dfsg1-3ubuntu2.2 dovecot-lmtpd 1:2.3.16+dfsg1-3ubuntu2.2 dovecot-mysql 1:2.3.16+dfsg1-3ubuntu2.2 dovecot-pop3d 1:2.3.16+dfsg1-3ubuntu2.2 postfix 3.6.4-1ubuntu1.2 amd64 High-performance mail transport agentpostfix-mysql 3.6.4-1ubuntu1.2 amd64 MySQL map support for Postfixpostfix-policyd-spf-python 2.9.3-1 all Postfix policy server for SPF checking Hello, I am hoping that you can help me. I am running this command on my main email server, one way backup/sync to the backup server. sudo doveadm sync -1 -A remote:root@x.x.x.x x.x.x.x is my remote server. I will add a new email on the main, run the command and it shows up on the backup. - Great! Now I delete that email from the main, run the command and the email is removed from the backup. That should not delete anything from the backup, correct? I prefer Not to delete anything, only update/add. Do you see what I am doing wrong? Thank You!!!! Here my installed versions dovecot-core 1:2.3.16+dfsg1-3ubuntu2.2 dovecot-imapd 1:2.3.16+dfsg1-3ubuntu2.2 dovecot-lmtpd 1:2.3.16+dfsg1-3ubuntu2.2 dovecot-mysql 1:2.3.16+dfsg1-3ubuntu2.2 dovecot-pop3d 1:2.3.16+dfsg1-3ubuntu2.2 postfix 3.6.4-1ubuntu1.2 amd64 High-performance mail transport agent postfix-mysql 3.6.4-1ubuntu1.2 amd64 MySQL map support for Postfix postfix-policyd-spf-python 2.9.3-1 all Postfix policy server for SPF checking

2 1

sieve filter generated email- sent folder
by joe a 29 Jan '24

29 Jan '24

dovecot 2.3.21 pigeonhole 0.5.21. Filters created via roundcube. Attempting to have filters detect certain email, send a notification text message to mobile via email, and copy that notification email to "Sent" folder. Filter(s) detect condition, move the email to desired folder and appear, as note in logs outside of dovecot, to sent the notification email. The notification email is not recorded in "Sent" folder and is not received by mobile device. Is this a "do-able" thing in dovecot/pigeonhole? If so, how? Docs available?

3 4

fts indexer stuck on very large plaintext messages
by p h 29 Jan '24

29 Jan '24

Hi, I recently fts indexed a users mailbox with xapian which had 10-15 very large plaintext messages (>20Mb). The content of these messages was mostly a list of all files on a linux server (tripwire and backup reports). The indexer-worker process was completely stuck processing these messages, cpu pegged at 100% running continuously for multiple days. I was wondering if there is way to avoid this issue. It would be great if I could configure limits for the fts indexing process.

2 1

shared mailbox replication
by micha＠micha.waw.pl 28 Jan '24

28 Jan '24

We use a shared mailbox, where incoming mails from customers are stored. Every user can see it as "shared/contact(a)domain.name". When a new message comes, any user who is currently available just takes the message and does something with it. It's configured this way: namespace shared { type = shared separator = / prefix = shared/%%u/ location = maildir:%%h/.maildir:LAYOUT=fs:INDEX=~/.shared/%%u subscriptions = no list = children } It worked perfectly until I set up replication. Now we have a mess, because a message moved/deleted on one server are replicated beck form another. This is known issue. The documentation says it clear: "Warning Shared folder replication doesn’t work correctly. Mainly it can generate a lot of duplicate emails. This is because there’s currently a per-user lock that prevents multiple dsyncs from working simultaneously on the same user. But with shared folders multiple users can be syncing the same folder. So this would need additional locks (e.g. shared folders would likely need to lock the owner user, and public folders would likely need a per-folder lock or maybe a global public folder lock). There are no plans to fix this." I understand "There are no plans to fix this." But... maybe there is a workaround? I am sure someone before me had already this problem... :-)

1 0

Tests fail 2.3.21 in aarch64 build
by Peter 28 Jan '24

28 Jan '24

Building Dovecot 2.3.21 for aarch64 (building with qemu emulation) I get the following in the test stage: test-file-cache.c:266: Assert failed: file_cache_set_size(cache, 1024) == -1 Panic: file test-common.c: line 211 (test_expect_error_string_n_times): assertion failed: (expected_errors == 0) test-common.c:245: Assert failed: suppress == TRUE Error: Raw backtrace: ./test-lib(+0x693f0) [0x7f10b36943f0] -> ./test-lib(+0x6d8e4) [0x7f10b36988e4] -> ./test-lib(+0x75110) [0x7f10b36a0110] -> ./test-lib(+0x75168) [0x7f10b36a0168] -> ./test-lib(+0x15534) [0x7f10b3640534] -> ./test-lib(+0x152ec) [0x7f10b36402ec] -> ./test-lib(+0x3411c) [0x7f10b365f11c] -> ./test-lib(+0x15e64) [0x7f10b3640e64] -> /lib64/libc.so.6(+0x2c79c) [0x40000087579c] -> /lib64/libc.so.6(__libc_start_main+0x98) [0x40000087586c] -> ./test-lib(+0x163f0) [0x7f10b36413f0] qemu: uncaught target signal 6 (Aborted) - core dumped I'll provide more info on request. Is this just an issue with the tests or is it an issue with Dovecot itself? Peter

1 0