December 2019 - dovecot

Dovecot 2.3 repo for CentOS 8.
by Reio Remma 15 Feb '20

15 Feb '20

Hello! Are there any plans for an official Dovecot repo for CentOS 8? Thanks, Reio

7 10

mail_filter and mail_filter_out broken somewhere between 2.2.27 and 2.3.4, problem still exists in git
by Michael Fincham 03 Feb '20

03 Feb '20

Hi Dovecot folks, I recently reported this bug in Debian (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939442) after a stretch -> buster upgrade, however since I can reproduce it using the latest 2.4 from git I thought perhaps I ought to take it straight upstream. Here's the text I provided Debian about the issue, and below that I've included a syslog snip showing the same issue in a fresh build of git master as well. mail_filter_out seems to fully panic (backtrace below), whereas mail_filter is just behaving oddly. Thanks :) ***************************** Package: dovecot-core Version: 2.3.4.1-5+deb10u1 Severity: important Hi Dovecot maintainers, After upgrading from the latest stretch version of dovecot-core (2.2.27-3+deb9u5) to buster (2.3.4.1-5+deb10u1) the "mail filter" interface seems to have broken. This problem is also present in the sid version (2.3.7.2-1). Mail filter is used to run the content of messages being stored or retrieved through an arbitrary process. The interface used for the external process is described here: https://wiki.dovecot.org/Plugins/MailFilter It is expected that the process will be called with the arguments specified in the configuration then supplied a message body on stdin, however since upgrading it seems that the arguments are not being correctly passed, instead being all jammed in to $1 and separated by tabs, rather than expanded in to argv. Even stranger the first few lines of the body of the message appear in argv rather than in stdin... These reproduction steps were carried out on a fresh install of Debian Buster with the "dovecot-core" package installed initially from stretch then upgraded to the buster version, however this behaviour has also been observed on stretch systems after upgrading to buster. To reproduce, drop this minimalised config in to /etc/dovecot/conf.d/repro.conf: # Minimal maildir setup for LDA first_valid_uid = 0 mail_location = maildir:~/Maildir userdb { driver = static args = allow_all_users=yes uid=mail gid=mail home=/tmp/%u } # Mail filter configuration mail_plugins = $mail_plugins mail_filter plugin { mail_filter = mail-filter read %u mail_filter_out = mail-filter write %u } service mail-filter { executable = script /usr/local/bin/mail-filter.sh user = dovecot unix_listener mail-filter { mode = 0666 } } And create the example script in /usr/local/bin/mail-filter.sh with executable permissions: #!/bin/bash echo "arguments were: $@" 1>&2 tempfile=$(mktemp) cat > "${tempfile}" cat "${tempfile}" rm "${tempfile}" This script simply logs the arguments it recieves, writes stdin to a file then retrieves it again from the file. Here's a sample session of me using dovecot-lda to pass a message through this script, then retrieve it again with doveadm: root@scratch-b6fd8bdd:~# /usr/lib/dovecot/dovecot-lda -d fincham@scratch-b6fd8bdd -f 'Test <scratch-b6fd8bdd>' < /root/test.eml root@scratch-b6fd8bdd:~# doveadm fetch -u 'fincham@scratch-b6fd8bdd' hdr subject Test hdr: To: Test <fincham@scratch-b6fd8bdd> From: Test <fincham@scratch-b6fd8bdd> Subject: This is the test e-mail root@scratch-b6fd8bdd:~# tail /var/log/syslog | grep mail-filter Sep 5 00:07:48 scratch-b6fd8bdd dovecot: mail-filter: Error: arguments were: write fincham@scratch-b6fd8bdd Sep 5 00:07:50 scratch-b6fd8bdd dovecot: mail-filter: Error: arguments were: read fincham@scratch-b6fd8bdd However after upgrading dovecot to the buster version this process no longer works, and the logged argv of the example script is very strange: root@scratch-b6fd8bdd:~# apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: liblua5.3-0 libsodium23 ssl-cert The following packages will be upgraded: dovecot-core [...] root@scratch-b6fd8bdd:~# /usr/lib/dovecot/dovecot-lda -d fincham@scratch-b6fd8bdd -f scratch-b6fd8bdd < /root/test.eml Aborted root@scratch-b6fd8bdd:~# doveadm fetch -u 'fincham@scratch-b6fd8bdd' hdr subject Test hdr: Hello! doveadm(fincham@scratch-b6fd8bdd): Error: Mailbox INBOX: UID=1: read() failed: Cached message size larger than expected (115 > 7, box=INBOX, UID=1) (read reason=mail stream) doveadm(fincham@scratch-b6fd8bdd): Error: Corrupted record in index cache file /tmp/fincham(a)scratch-b6fd8bdd/Maildir/dovecot.index.cache: UID 1: Broken physical size in mailbox INBOX: read() failed: Cached message size larger than expected (115 > 7, box=INBOX, UID=1) doveadm(fincham@scratch-b6fd8bdd): Error: read() failed: Cached message size larger than expected (115 > 7, box=INBOX, UID=1) doveadm(fincham@scratch-b6fd8bdd): Error: fetch(hdr) failed for box=INBOX uid=1: read() failed: Cached message size larger than expected (115 > 7, box=INBOX, UID=1) root@scratch-b6fd8bdd:~# tail /var/log/syslog | grep mail-filter Sep 5 00:07:48 scratch-b6fd8bdd dovecot: mail-filter: Error: arguments were: write fincham@scratch-b6fd8bdd Sep 5 00:07:50 scratch-b6fd8bdd dovecot: mail-filter: Error: arguments were: read fincham@scratch-b6fd8bdd Sep 5 00:12:11 scratch-b6fd8bdd dovecot: mail-filter: Error: arguments were: write#011fincham@scratch-b6fd8bdd#011 To: Test <fincham@scratch-b6fd8bdd> From: Test <fincham@scratch-b6fd8bdd> Subject: This is the test e-mail Sep 5 00:12:14 scratch-b6fd8bdd dovecot: mail-filter: Error: arguments were: read#011fincham@scratch-b6fd8bdd#011 To: Test <fincham@scratch-b6fd8bdd> From: Test <fincham@scratch-b6fd8bdd> Subject: This is the test e-mail -- Package-specific info: dovecot configuration --------------------- # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-5-cloud-amd64 x86_64 Debian 10.0 # Hostname: scratch-b6fd8bdd first_valid_uid = 0 mail_location = maildir:~/Maildir mail_plugins = " mail_filter" 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 } plugin { mail_filter = mail-filter read %u mail_filter_out = mail-filter write %u } service mail-filter { executable = script /usr/local/bin/mail-filter.sh unix_listener mail-filter { mode = 0666 } user = dovecot } ssl = no userdb { driver = passwd } userdb { args = allow_all_users=yes uid=mail gid=mail home=/tmp/%u driver = static } -- System Information: Debian Release: 10.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-cloud-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dovecot-core depends on: ii adduser 3.118 ii libapparmor1 2.13.2-10 ii libbz2-1.0 1.0.6-9.1 ii libc6 2.28-10 ii libexttextcat-2.0-0 3.4.5-1 ii libicu63 63.1-6 ii liblua5.3-0 5.3.3-1.1 ii liblz4-1 1.8.3-1 ii liblzma5 5.2.4-1 ii libpam-runtime 1.3.1-5 ii libpam0g 1.3.1-5 ii libsodium23 1.0.17-1 ii libssl1.1 1.1.1c-1 ii libstemmer0d 0+svn585-1+b2 ii libwrap0 7.6.q-28 ii lsb-base 10.2019051400 ii openssl 1.1.1c-1 ii ssl-cert 1.0.39 ii ucf 3.0038+nmu1 ii zlib1g 1:1.2.11.dfsg-1 dovecot-core recommends no packages. Versions of packages dovecot-core suggests: pn dovecot-gssapi <none> pn dovecot-imapd <none> pn dovecot-ldap <none> pn dovecot-lmtpd <none> pn dovecot-lucene <none> pn dovecot-managesieved <none> pn dovecot-mysql <none> pn dovecot-pgsql <none> pn dovecot-pop3d <none> pn dovecot-sieve <none> pn dovecot-solr <none> pn dovecot-sqlite <none> pn dovecot-submissiond <none> ii ntp 1:4.2.8p12+dfsg-4 Versions of packages dovecot-core is related to: ii dovecot-core [dovecot-common] 1:2.3.4.1-5+deb10u1 pn dovecot-dev <none> pn dovecot-gssapi <none> pn dovecot-imapd <none> pn dovecot-ldap <none> pn dovecot-lmtpd <none> pn dovecot-managesieved <none> pn dovecot-mysql <none> pn dovecot-pgsql <none> pn dovecot-pop3d <none> pn dovecot-sieve <none> pn dovecot-sqlite <none> -- no debconf information ***************************** And here it is on 2.4 from git: Sep 5 02:18:10 scratch-b6fd8bdd dovecot: master: Dovecot v2.4.devel () starting up for imap, pop3, lmtp Sep 5 02:18:10 scratch-b6fd8bdd systemd[1]: Started LSB: Dovecot init script. Sep 5 02:18:12 scratch-b6fd8bdd dovecot: mail-filter: Error: arguments were: write#011fincham@scratch-b6fd8bdd#011 To: Test <fincham@scratch-b6fd8bdd> From: Test <fincham@scratch-b6fd8bdd> Subject: This is the test e-mail Sep 5 02:18:12 scratch-b6fd8bdd dovecot: lda(fincham@scratch-b6fd8bdd)<4213><94f8BWRwcF11EAAA/w3Ckw>: Panic: file ostream.c: line 201 (o_stream_flush): assertion failed: (stream->stream_errno != 0) Sep 5 02:18:12 scratch-b6fd8bdd dovecot: lda(fincham@scratch-b6fd8bdd)<4213><94f8BWRwcF11EAAA/w3Ckw>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xef5fb) [0x7f85ed0715fb] -> /usr/lib/dovecot/libdovecot.so.0(+0xef661) [0x7f85ed071661] -> /usr/lib/dovecot/libdovecot.so.0(+0x4e808) [0x7f85ecfd0808] -> /usr/lib/dovecot/libdovecot.so.0(+0x52ec1) [0x7f85ecfd4ec1] -> /usr/lib/dovecot/libdovecot-storage.so.0(maildir_save_finish+0x96) [0x7f85ed1b24d6] -> /usr/lib/dovecot/libdovecot-lda.so.0(+0x4395) [0x7f85ed294395] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_save_finish+0x82) [0x7f85ed189e52] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_copy+0xd9) [0x7f85ed17c409] -> /usr/lib/dovecot/libdovecot-storage.so.0(maildir_copy+0x52) [0x7f85ed1aea02] -> /usr/lib/dovecot/libdovecot-lda.so.0(+0x4221) [0x7f85ed294221] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x5c1bc) [0x7f85ed18a1bc] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver_save+0x1b0) [0x7f85ed295390] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x2f6) [0x7f85ed295ad6] -> /usr/libexec/dovecot/dovecot-lda(main+0x81b) [0x560cba869f4b] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7f85ecdde09b] -> /usr/libexec/dovecot/dovecot-lda(_start+0x2a) [0x560cba86a65a]

2 3

intermittant passdb error
by NeuralNET 23 Jan '20

23 Jan '20

I'm having great difficulty debugging this problem.. I'm having intermittant problems connecting to dovecot. This started a couple of days ago following an apt-get update on the server. I'm running Ubuntu 14.04, dovecot 2.2.9. Here's my dovecot -n --- # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.19.0-59-generic x86_64 Ubuntu 14.04.4 LTS auth_mechanisms = plain login mail_location = maildir:~/Maildir 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 } plugin { sieve_dir = ~/sieve } protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } user = $default_internal_user } ssl = required ssl_cert = </etc/dovecot/box.neuralnet.org.uk_crt.pem ssl_key = </etc/dovecot/box.neuralnet.org.uk_key.pem ssl_protocols = !SSLv2 !SSLv3 userdb { driver = passwd } --- Pretty standard stuff. In addition disable_plaintext_auth = yes is set in 10-auth.conf This showed up in the mail.err after the reboot; --- May 17 09:04:51 server dovecot: imap-login: Error: read(anvil) failed: EOF May 17 09:04:51 server dovecot: auth: Error: read(anvil-auth-penalty) failed: EOF May 17 09:04:51 server dovecot: auth: Error: net_connect_unix(anvil-auth-penalty) failed: Permission denied --- At that point The following commands were run on the server a few minutes apart with no changes made in the interim; --- username@box /etc/dovecot $ doveadm user username field valueuserdb lookup: user username doesn't exist username@box /etc/dovecot $ doveadm user username field value uid 1000 gid 1000 home /home/username mail maildir:~/Maildir system_groups_user username --- so, passdb wasn't accessible, but now it is ? Imap logins are showing in mail.log as failing, but thunderbird is currently connected; --- May 18 12:00:58 box dovecot: imap-login: Disconnected (auth failed, 3 attempts in 19 secs): user=<username>, method=PLAIN, rip=10.0.0.3, lip=10.0.0.99, TLS, session=<********> May 18 12:08:27 box dovecot: imap-login: Disconnected (auth failed, 3 attempts in 20 secs): user=<username>, method=PLAIN, rip=10.0.0.3, lip=10.0.0.99, TLS, session=<********> May 18 12:08:50 box dovecot: imap-login: Disconnected (auth failed, 3 attempts in 12 secs): user=<username>, method=PLAIN, rip=10.0.0.3, lip=10.0.0.99, TLS, session=<********> --- do I conclude that method=plain is failing, whereas method=login succeeds ? I tried setting auth_debug_password=yes and get the following; --- May 18 12:26:42 box dovecot: auth: Debug: client in: CONT#0111#011A********== (previous base64 data may contain sensitive data) May 18 12:26:42 box dovecot: auth-worker(12214): Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth May 18 12:26:42 box dovecot: auth-worker(12214): Debug: pam(expert,10.0.0.3): lookup service=dovecot May 18 12:26:42 box dovecot: auth-worker(12214): Debug: pam(expert,10.0.0.3): #1/1 style=1 msg=Password: May 18 12:26:42 box dovecot: auth-worker(12211): pam(username,10.0.0.3): pam_authenticate() failed: Authentication failure (password mismatch?) (given password: ******) May 18 12:26:44 box dovecot: auth: Debug: client passdb out: FAIL#0112#011user=username --- Any assistance debugging this further is greatly recieved! Thanks.

2 2

dovecot cannot drop privileges inside singularity container
by cesco 15 Jan '20

15 Jan '20

Hi all I'm facing an issue while running dovecot inside a singularity (https://sylabs.io/singularity/) container dovecot version is 2.3.4.1 (configuration below) running on debian buster, inside a container made with singularity version 3.4.2 unfortunately, when I try to start dovecot, it gives: Singularity test.sif:~> cat /var/log/mail.log Dec 30 17:23:38 testnode dovecot: master: Dovecot v2.3.4.1 (f79e8e7e4) starting up for imap, lmtp, sieve, pop3, submission (core dumps disabled) Dec 30 17:23:38 testnode dovecot: anvil: Fatal: We couldn't drop root privileges Dec 30 17:23:38 testnode dovecot: master: Error: service(anvil): command startup failed, throttling for 2 secs the same happens on singularity containers based on debian bullseye or alpine linux 3.9.2 many thanks! nzasch Singularity test.sif:~> doveconf -n # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-6-amd64 x86_64 Debian 10.2 # Hostname: testnode.example.net mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext 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 } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap lmtp sieve pop3 submission" 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 }

2 2

Dovecot, pigeonhole and hardlinks
by Gionatan Danti 03 Jan '20

03 Jan '20

Hi list, many moons ago I asked about preserving hardlink between identical messages when pigeonhole (for sieve filtering) was used. The reply was that, while hardlink worked well for non-filtered messages, using pigeonhole broke the hardlink (ie: some message-specific data was appended to the actual mail file). Here you can find the original thread: https://dovecot.org/pipermail/dovecot/2015-November/102579.html I would ask the same things today: is dovecot+pigeonhole capable of storing the same incoming message, sent to multiple rcpt or to a group/alias expanding in multiple recipients, as a single hardlink? Note: I know about SIS, but it has some important drawback and I would avoid using it. Thanks. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it email: g.danti(a)assyoma.it - info(a)assyoma.it GPG public key ID: FF5F32A8

2 4

spamsieve question
by Gerben Wierda 31 Dec '19

31 Dec '19

My new dovecot covers spam/ham training through the standard Spam_train and Notspam_train mailboxes. When a message is copied (I’m using macOS/iOS standard Apple clients) it triggers the spam/ham learning by rspamd. So far so good. When I move a message to Spam_train I’d like it to be removed immediately after learning. When I move a message to Notspam_train, I’d like it to move back where it came from after having been piped The first is I think doable, but how? Is the second doable? Gerben Wierda Chess and the Art of Enterprise Architecture <https://ea.rna.nl/the-book/> Mastering ArchiMate <https://ea.rna.nl/the-book-edition-iii/> Architecture for Real Enterprises <https://www.infoworld.com/blog/architecture-for-real-enterprises/> at InfoWorld On Slippery Ice <https://eapj.org/on-slippery-ice/> at EAPJ

1 0

Problem with big number of pop3-login [1 pre-login]
by Григорий Семенов 30 Dec '19

30 Dec '19

Dear all, I have recently migrated from my old Debian 8 (jessie) system to a new VM with fresh Debian 10 (buster) installation. Previous dovecot version was 2.2.13 and now I have 2.3.4.1. Dovecot was setup from Debian packages. Mostly, it is working, but one problem is just frustrating me. The number of some pop3-login processes are getting higher and higher until they reach my login_max_processes_count option which is equal 1000. From ps aux it looks like this: dovecot 55067 0.0 0.0 8192 6340 ? S 00:09 0:00 dovecot/pop3-login [1 pre-login] dovecot 55344 0.0 0.0 8192 6388 ? S 00:35 0:00 dovecot/pop3-login [1 pre-login] dovecot 55351 0.0 0.0 8192 6268 ? S 00:35 0:00 dovecot/pop3-login [1 pre-login] dovecot 55354 0.0 0.0 8192 6388 ? S 00:35 0:00 dovecot/pop3-login [1 pre-login] dovecot 55594 0.0 0.0 8192 6280 ? S 00:36 0:00 dovecot/pop3-login [1 pre-login] dovecot 56822 0.0 0.0 8192 6300 ? S 00:36 0:00 dovecot/pop3-login [1 pre-login] dovecot 56996 0.0 0.0 8192 6268 ? S 00:36 0:00 dovecot/pop3-login [1 pre-login] … Once it reaches the login_max_processes_count value my users start to complain to no new mail is arriving. Restart resolves the problem just for some time, until it will come to a limit next time (sometimes it take 1 day, sometimes 1 hour). In my old system I had nothing like that, but I guess it could be done something wrong during migration. I don’t know if it is significant but instead of real users I deal with only one third-party application which utilizeses 5 simultaneous tcp connections to check mailboxes via SSL\TLS. My dovecot is not public, and there is nothing else besides these 5 connections. Currently, in a config I have this: service pop3-login { process_min_avail = 4 process_limit = 4 client_limit = 100 service_count = 100 Please friends give me a way how to handle the situation. Might it be a bug? ========= Regards, Greg Semenov

1 0

Re: Issue running Dovecot in Docker Container
by Naveen Reddy 30 Dec '19

30 Dec '19

I'm not using internal logging. I'm running the docker with the logging to the host. I have used the same options you have specified. The problem is that the below processes are not running inside docker container whereas the standalone dovecot is running these processes(meaning without container) dovecot-Dovecot/auth dovecot-Dovecot/ssl-params dovecot-Director/lmtp dovecot-Director/ssl-params dovecot-Director/imap-login director Thanks & Regards, Naveen On Mon, Dec 30, 2019 at 3:16 PM Marc Roos <M.Roos(a)f1-outsourcing.eu> wrote: > > If you are running your container as root. You will not have the issues > I encountered. Dovecot is dropping to the 'dovecot' and 'dovenull'(?) > when needed, this is fine. > > PS. I would not recommend using internal logging, use something like > this to log to the host or remote syslog. > docker run -v /dev/log:/dev/log -it dovecot-proxy > > > -----Original Message----- > Subject: Re: Issue running Dovecot in Docker Container > > Hi Marc, > > I can see the processes are running as a root in container environment. > Do you think that still have issues ? > Here is the processes running inside container: > > bash-4.2# ps -ef > UID PID PPID C STIME TTY TIME CMD > root 1 0 0 Dec27 ? 00:00:00 /bin/bash /bootstrap.sh > root 7 1 0 Dec27 ? 00:00:00 /usr/sbin/dovecot -F -c > /etc/dovecot/director.conf > root 8 1 0 Dec27 ? 00:00:00 /usr/sbin/dovecot -F > root 9 1 0 Dec27 ? 00:00:00 sleep 36000d > dovecot 10 8 0 Dec27 ? 00:00:00 dovecot-Dovecot/anvil > dovecot 14 7 0 Dec27 ? 00:00:00 dovecot-Director/anvil > root 267 8 0 Dec27 ? 00:00:00 dovecot-Dovecot/log > root 269 8 0 Dec27 ? 00:00:08 dovecot-Dovecot/config > root 281 7 0 Dec27 ? 00:00:00 dovecot-Director/log > root 283 7 0 Dec27 ? 00:00:00 dovecot-Director/config > > > > > Thanks & Regards, > Naveen > > > > On Mon, Dec 30, 2019 at 2:56 PM Marc Roos <M.Roos(a)f1-outsourcing.eu> > wrote: > > > > I have noticed several issues with dovecot, trying to run it > without > root. Which is preferable in any container environment. Maybe you > would > like me to document these somewhere? So at some point they can be > applied. > > > -----Original Message----- > From: Naveen Reddy [mailto:naveenreddy99@gmail.com] > Sent: 30 December 2019 09:02 > To: Aki Tuomi > Cc: dovecot(a)dovecot.org > Subject: Re: Issue running Dovecot in Docker Container > > Hi, I can see those values correctly with the doveconf -nc > command. > Here > is the part of output: > > bash-4.2# doveconf -nc /etc/dovecot/director.conf # 2.2.36 > (1f10bfa63): > /etc/dovecot/director.conf # OS: Linux > 4.1.12-112.14.11.el7uek.x86_64 > x86_64 Red Hat Enterprise Linux Server release 7.7 (Maipo) # > Hostname: > 69b492645b56 auth_debug = yes auth_default_realm = > xxxxxxxxxxxxxxxx > > auth_verbose = yes base_dir = /var/run/dovecot_director > debug_log_path = > $log_path director_mail_servers = xxxxxxxxxxxxxxxxxx > director_servers = > xxxxxxxxxxxxxxxxxxxx disable_plaintext_auth = no first_valid_uid = > 1000 > hostname = xxxxxxxxxxxxxxxxxxxx info_log_path = $log_path > instance_name > = Director lmtp_proxy = yes log_path = /dovecot.log > login_log_format_elements = user=<%u> method=%m rip=%r lip=%l > mpid=%e %c > home=%h > > Thanks & Regards, > Naveen > > > > On Fri, Dec 27, 2019 at 10:08 PM Aki Tuomi > <aki.tuomi(a)open-xchange.com> > wrote: > > > > Can you check with `doveconf -nc /path/to/director.conf` > that the > values are actually set correctly? > > Aki > > On 27/12/2019 15:34 Naveen Reddy > <naveenreddy99(a)gmail.com> > wrote: > > > > The conf.d files are not included. I have added > !include > conf.d/*.conf to director.conf and reloaded the dovecot and > director > services. > > conf.d/10-logging also has the following lines: > > log_path = /dovecot.log > info_log_path = $log_path > debug_log_path = $log_path > > > The /dovecot.log file still shows empty. Nothing > is being > logged to that file. > > > Thanks & Regards, > Naveen > > > > On Thu, Dec 26, 2019 at 10:52 PM Aki Tuomi < > aki.tuomi(a)open-xchange.com> wrote: > > > > Do you have !include or !try_include in > director.conf? > The conf.d files are not included otherwise. > > Aki > > On 26/12/2019 11:27 Naveen Reddy < > naveenreddy99(a)gmail.com> wrote: > > > I have tried these in the > 10-logging.conf but no > luck. There is nothing logged to the file. > > bash-4.2# ps -ef > UID PID PPID C STIME TTY > > TIME CMD > root 1 0 0 Dec23 ? > > 00:00:00 > /bin/bash /bootstrap.sh > root 8 1 0 Dec23 ? > > 00:00:00 > sleep 36000d > root 15681 0 0 08:51 > pts/1 > 00:00:00 bash > root 16340 0 0 09:19 ? > > 00:00:00 > /usr/sbin/dovecot -c /etc/dovecot/director.conf > dovecot 16341 16340 0 09:19 ? > > 00:00:00 > dovecot-Director/anvil > root 16342 16340 0 09:19 ? > > 00:00:00 > dovecot-Director/log > root 16344 16340 0 09:19 ? > > 00:00:00 > dovecot-Director/config > root 16390 0 0 09:22 ? > > 00:00:00 > /usr/sbin/dovecot -c /etc/dovecot/dovecot.conf > dovecot 16391 16390 0 09:22 ? > > 00:00:00 > dovecot-Dovecot/anvil > root 16392 16390 0 09:22 ? > > 00:00:00 > dovecot-Dovecot/log > root 16394 16390 0 09:22 ? > > 00:00:00 > dovecot-Dovecot/config > root 16406 15681 0 09:22 > pts/1 > 00:00:00 ps > -ef > > > The below processes are not > starting as well. > > dovecot-Dovecot/auth > dovecot-Dovecot/ssl-params > dovecot-Director/lmtp > dovecot-Director/ssl-params > dovecot-Director/imap-login > director > > Thanks & Regards, > Naveen > > > > On Tue, Dec 24, 2019 at 10:54 PM > Aki Tuomi < > aki.tuomi(a)open-xchange.com> wrote: > > > > > > On 24/12/2019 > 12:33 > Naveen Reddy < > naveenreddy99(a)gmail.com> wrote: > > > Hello, > > We need help with > an issue that we are > running into when we are trying to run Dovecot in Docker > container. > > Also how do we > enable debugging for > dovecot. Logs doesn't show any info about the issue. > > Below processes > are > not running when a > Director service is started: > > > dovecot-Dovecot/auth > > dovecot-Dovecot/ssl-params > > dovecot-Director/lmtp > > dovecot-Director/ssl-params > > dovecot-Director/imap-login director > > Here is the > version > that I'm running and > including the dovecot -n output below: > > bash-4.2# dovecot > --version > 2.2.36 > > > bash-4.2# dovecot > -n > # 2.2.36 (xxxxx): > /etc/dovecot/dovecot.conf > # OS: Linux > 4.1.12-112.14.11.el7uek.x86_64 > x86_64 Red Hat Enterprise Linux Server release 7.7 (Maipo) > # Hostname: XXXXXXX > auth_debug = yes > auth_default_realm > = xxxxxxxxxxxx > auth_verbose = yes > > disable_plaintext_auth = no > dotlock_use_excl = > no > hostname = > xxxxxxxxxxxxxxxx > instance_name = > Dovecot > > login_log_format_elements = user=<%u> > method=%m rip=%r lip=%l mpid=%e %c home=% domain=%d > mail_debug = yes > mail_fsync = always > mail_gid = imapd > mail_home = > /xxxxxxxxxxx/%d/%n > mail_location = > dbox:~/ > mail_uid = imapd > mmap_disable = yes > passdb { > args = > /etc/dovecot/lookups/ldap-pass.conf > driver = ldap > } > passdb { > args = > /etc/dovecot/lookups/xxxx.conf > driver = ldap > } > plugin { > stats_refresh = > 30 secs > stats_track_cmds > = yes > } > protocols = imap > lmtp > service auth { > client_limit = > 4096 > unix_listener > auth-userdb { > mode = 0777 > } > } > service imap-login > { > chroot = login > client_limit = 0 > > drop_priv_before_exec = no > executable = > imap-login > extra_groups = > group = > idle_kill = 0 > inet_listener > imap { > address = > port = 1144 > ssl = no > } > inet_listener > imaps { > address = > port = 994 > ssl = yes > } > privileged_group > = > process_limit = 0 > > process_min_avail > = 0 > protocol = imap > service_count = > 50 > type = login > user = > $default_login_user > vsz_limit = > 18446744073709551615 B > } > service imap { > service_count = > 50 > } > service lmtp { > executable = > lmtp > -L > inet_listener > lmtp { > address = > port = 10025 > } > } > service stats { > fifo_listener > stats-mail { > mode = 0600 > user = imapd > } > } > ssl_cert = > </xxxxxxx/cert/dovecot.pem > ssl_cipher_list = > XXXXXX > ssl_key = # > hidden, use -P to show it > ssl_protocols = > XXXXX > userdb { > args = > /etc/dovecot/lookups/ldap-user.conf > driver = ldap > } > userdb { > args = > /etc/dovecot/lookups/xxxxxxx.conf > driver = ldap > } > > > Thanks & Regards, > Naveen > > > > Try setting > > log_path=/dovecot.log > info_log_path=$log_path > debug_log_path=$log_path > --- > Aki Tuomi > > > --- > Aki Tuomi > > > --- > Aki Tuomi > > > > > >

3 4

Re: Issue running Dovecot in Docker Container
by Naveen Reddy 30 Dec '19

30 Dec '19

Hi Marc, I can see the processes are running as a root in container environment. Do you think that still have issues ? Here is the processes running inside container: bash-4.2# ps -ef UID PID PPID C STIME TTY TIME CMD root 1 0 0 Dec27 ? 00:00:00 /bin/bash /bootstrap.sh root 7 1 0 Dec27 ? 00:00:00 /usr/sbin/dovecot -F -c /etc/dovecot/director.conf root 8 1 0 Dec27 ? 00:00:00 /usr/sbin/dovecot -F root 9 1 0 Dec27 ? 00:00:00 sleep 36000d dovecot 10 8 0 Dec27 ? 00:00:00 dovecot-Dovecot/anvil dovecot 14 7 0 Dec27 ? 00:00:00 dovecot-Director/anvil root 267 8 0 Dec27 ? 00:00:00 dovecot-Dovecot/log root 269 8 0 Dec27 ? 00:00:08 dovecot-Dovecot/config root 281 7 0 Dec27 ? 00:00:00 dovecot-Director/log root 283 7 0 Dec27 ? 00:00:00 dovecot-Director/config Thanks & Regards, Naveen On Mon, Dec 30, 2019 at 2:56 PM Marc Roos <M.Roos(a)f1-outsourcing.eu> wrote: > > I have noticed several issues with dovecot, trying to run it without > root. Which is preferable in any container environment. Maybe you would > like me to document these somewhere? So at some point they can be > applied. > > > -----Original Message----- > From: Naveen Reddy [mailto:naveenreddy99@gmail.com] > Sent: 30 December 2019 09:02 > To: Aki Tuomi > Cc: dovecot(a)dovecot.org > Subject: Re: Issue running Dovecot in Docker Container > > Hi, I can see those values correctly with the doveconf -nc command. Here > is the part of output: > > bash-4.2# doveconf -nc /etc/dovecot/director.conf # 2.2.36 (1f10bfa63): > /etc/dovecot/director.conf # OS: Linux 4.1.12-112.14.11.el7uek.x86_64 > x86_64 Red Hat Enterprise Linux Server release 7.7 (Maipo) # Hostname: > 69b492645b56 auth_debug = yes auth_default_realm = xxxxxxxxxxxxxxxx > auth_verbose = yes base_dir = /var/run/dovecot_director debug_log_path = > $log_path director_mail_servers = xxxxxxxxxxxxxxxxxx director_servers = > xxxxxxxxxxxxxxxxxxxx disable_plaintext_auth = no first_valid_uid = 1000 > hostname = xxxxxxxxxxxxxxxxxxxx info_log_path = $log_path instance_name > = Director lmtp_proxy = yes log_path = /dovecot.log > login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c > home=%h > > Thanks & Regards, > Naveen > > > > On Fri, Dec 27, 2019 at 10:08 PM Aki Tuomi <aki.tuomi(a)open-xchange.com> > wrote: > > > > Can you check with `doveconf -nc /path/to/director.conf` that the > values are actually set correctly? > > Aki > > On 27/12/2019 15:34 Naveen Reddy <naveenreddy99(a)gmail.com> > > wrote: > > > > The conf.d files are not included. I have added !include > conf.d/*.conf to director.conf and reloaded the dovecot and director > services. > > conf.d/10-logging also has the following lines: > > log_path = /dovecot.log > info_log_path = $log_path > debug_log_path = $log_path > > > The /dovecot.log file still shows empty. Nothing is being > logged to that file. > > > Thanks & Regards, > Naveen > > > > On Thu, Dec 26, 2019 at 10:52 PM Aki Tuomi < > aki.tuomi(a)open-xchange.com> wrote: > > > > Do you have !include or !try_include in > director.conf? > The conf.d files are not included otherwise. > > Aki > > On 26/12/2019 11:27 Naveen Reddy < > naveenreddy99(a)gmail.com> wrote: > > > I have tried these in the 10-logging.conf > but no > luck. There is nothing logged to the file. > > bash-4.2# ps -ef > UID PID PPID C STIME TTY > TIME CMD > root 1 0 0 Dec23 ? > 00:00:00 > /bin/bash /bootstrap.sh > root 8 1 0 Dec23 ? > 00:00:00 > sleep 36000d > root 15681 0 0 08:51 pts/1 > 00:00:00 bash > root 16340 0 0 09:19 ? > 00:00:00 > /usr/sbin/dovecot -c /etc/dovecot/director.conf > dovecot 16341 16340 0 09:19 ? > 00:00:00 > dovecot-Director/anvil > root 16342 16340 0 09:19 ? > 00:00:00 > dovecot-Director/log > root 16344 16340 0 09:19 ? > 00:00:00 > dovecot-Director/config > root 16390 0 0 09:22 ? > 00:00:00 > /usr/sbin/dovecot -c /etc/dovecot/dovecot.conf > dovecot 16391 16390 0 09:22 ? > 00:00:00 > dovecot-Dovecot/anvil > root 16392 16390 0 09:22 ? > 00:00:00 > dovecot-Dovecot/log > root 16394 16390 0 09:22 ? > 00:00:00 > dovecot-Dovecot/config > root 16406 15681 0 09:22 pts/1 > 00:00:00 ps > -ef > > > The below processes are not starting as > well. > > dovecot-Dovecot/auth > dovecot-Dovecot/ssl-params > dovecot-Director/lmtp > dovecot-Director/ssl-params > dovecot-Director/imap-login director > > Thanks & Regards, > Naveen > > > > On Tue, Dec 24, 2019 at 10:54 PM Aki Tuomi > < > aki.tuomi(a)open-xchange.com> wrote: > > > > > > On 24/12/2019 12:33 Naveen > Reddy < > naveenreddy99(a)gmail.com> wrote: > > > Hello, > > We need help with an issue > that we are > running into when we are trying to run Dovecot in Docker container. > Also how do we enable > debugging for > dovecot. Logs doesn't show any info about the issue. > > Below processes are not > running when a > Director service is started: > > dovecot-Dovecot/auth > dovecot-Dovecot/ssl-params > dovecot-Director/lmtp > dovecot-Director/ssl-params > > dovecot-Director/imap-login director > > Here is the version that > I'm running and > including the dovecot -n output below: > > bash-4.2# dovecot --version > 2.2.36 > > > bash-4.2# dovecot -n > # 2.2.36 (xxxxx): > /etc/dovecot/dovecot.conf > # OS: Linux > 4.1.12-112.14.11.el7uek.x86_64 > x86_64 Red Hat Enterprise Linux Server release 7.7 (Maipo) > # Hostname: XXXXXXX > auth_debug = yes > auth_default_realm = > xxxxxxxxxxxx > auth_verbose = yes > disable_plaintext_auth = no > dotlock_use_excl = no > hostname = xxxxxxxxxxxxxxxx > instance_name = Dovecot > login_log_format_elements > = user=<%u> > method=%m rip=%r lip=%l mpid=%e %c home=% domain=%d > mail_debug = yes > mail_fsync = always > mail_gid = imapd > mail_home = > /xxxxxxxxxxx/%d/%n > mail_location = dbox:~/ > mail_uid = imapd > mmap_disable = yes > passdb { > args = > /etc/dovecot/lookups/ldap-pass.conf > driver = ldap > } > passdb { > args = > /etc/dovecot/lookups/xxxx.conf > driver = ldap > } > plugin { > stats_refresh = 30 secs > stats_track_cmds = yes > } > protocols = imap lmtp > service auth { > client_limit = 4096 > unix_listener > auth-userdb { > mode = 0777 > } > } > service imap-login { > chroot = login > client_limit = 0 > drop_priv_before_exec = > no > executable = imap-login > extra_groups = > group = > idle_kill = 0 > inet_listener imap { > address = > port = 1144 > ssl = no > } > inet_listener imaps { > address = > port = 994 > ssl = yes > } > privileged_group = > process_limit = 0 > process_min_avail = 0 > protocol = imap > service_count = 50 > type = login > user = > $default_login_user > vsz_limit = > 18446744073709551615 B > } > service imap { > service_count = 50 > } > service lmtp { > executable = lmtp -L > inet_listener lmtp { > address = > port = 10025 > } > } > service stats { > fifo_listener stats-mail > { > mode = 0600 > user = imapd > } > } > ssl_cert = > </xxxxxxx/cert/dovecot.pem > ssl_cipher_list = XXXXXX > ssl_key = # hidden, use > -P to show it > ssl_protocols = XXXXX > userdb { > args = > /etc/dovecot/lookups/ldap-user.conf > driver = ldap > } > userdb { > args = > /etc/dovecot/lookups/xxxxxxx.conf > driver = ldap > } > > > Thanks & Regards, > Naveen > > > > Try setting > > log_path=/dovecot.log > info_log_path=$log_path > debug_log_path=$log_path > --- > Aki Tuomi > > > --- > Aki Tuomi > > > --- > Aki Tuomi > > >

2 1

Issue running Dovecot in Docker Container
by Naveen Reddy 30 Dec '19

30 Dec '19

Hello, We need help with an issue that we are running into when we are trying to run Dovecot in Docker container. Also how do we enable debugging for dovecot. Logs doesn't show any info about the issue. Below processes are not running when a Director service is started: dovecot-Dovecot/auth dovecot-Dovecot/ssl-params dovecot-Director/lmtp dovecot-Director/ssl-params dovecot-Director/imap-login director Here is the version that I'm running and including the dovecot -n output below: bash-4.2# dovecot --version 2.2.36 bash-4.2# dovecot -n # 2.2.36 (xxxxx): /etc/dovecot/dovecot.conf # OS: Linux 4.1.12-112.14.11.el7uek.x86_64 x86_64 Red Hat Enterprise Linux Server release 7.7 (Maipo) # Hostname: XXXXXXX auth_debug = yes auth_default_realm = xxxxxxxxxxxx auth_verbose = yes disable_plaintext_auth = no dotlock_use_excl = no hostname = xxxxxxxxxxxxxxxx instance_name = Dovecot login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c home=% domain=%d mail_debug = yes mail_fsync = always mail_gid = imapd mail_home = /xxxxxxxxxxx/%d/%n mail_location = dbox:~/ mail_uid = imapd mmap_disable = yes passdb { args = /etc/dovecot/lookups/ldap-pass.conf driver = ldap } passdb { args = /etc/dovecot/lookups/xxxx.conf driver = ldap } plugin { stats_refresh = 30 secs stats_track_cmds = yes } protocols = imap lmtp service auth { client_limit = 4096 unix_listener auth-userdb { mode = 0777 } } service imap-login { chroot = login client_limit = 0 drop_priv_before_exec = no executable = imap-login extra_groups = group = idle_kill = 0 inet_listener imap { address = port = 1144 ssl = no } inet_listener imaps { address = port = 994 ssl = yes } privileged_group = process_limit = 0 process_min_avail = 0 protocol = imap service_count = 50 type = login user = $default_login_user vsz_limit = 18446744073709551615 B } service imap { service_count = 50 } service lmtp { executable = lmtp -L inet_listener lmtp { address = port = 10025 } } service stats { fifo_listener stats-mail { mode = 0600 user = imapd } } ssl_cert = </xxxxxxx/cert/dovecot.pem ssl_cipher_list = XXXXXX ssl_key = # hidden, use -P to show it ssl_protocols = XXXXX userdb { args = /etc/dovecot/lookups/ldap-user.conf driver = ldap } userdb { args = /etc/dovecot/lookups/xxxxxxx.conf driver = ldap } Thanks & Regards, Naveen

3 7