- dovecot - dovecot.org

execute sieve command - fails to notice script has exited
by Lionel Elie Mamane 13 Nov '18

13 Nov '18

Hi, Running dovecot 2.2.27 (c0f36b0) on Debian GNU/Linux stable (version 9.6), I'm trying to use the execute command in a sieve script, with direct execution (not service socket). The script is executed, and returns (the process exits), but the dovecot-lda process seems to not notice, and thinks the script did not terminate. After sieve_execute_exec_timeout has passed, it sends a TERM, a bit later a KILL and then logs a failure. The "ps -Af f" looks like: S 0:00 \_ /usr/sbin/exim4 -Mc 1gMazS-0007IV-RB S 0:00 \_ /usr/lib/dovecot/dovecot-lda -f master(a)blitz.conuropsis.org Z 0:00 | \_ [foofilter] <defunct> S 0:00 \_ /usr/sbin/exim4 -Mc 1gMazS-0007IV-RB The dovecot debug log looks like: lda(user): Debug: Loading modules from directory: /usr/lib/dovecot/modules lda(user): Debug: Module loaded: /usr/lib/dovecot/modules/lib90_sieve_plugin.so lda(user): Debug: Effective uid=1000, gid=1000, home=/home/user lda(user): Debug: maildir++: root=/home/user/Maildir, index=, indexpvt=, control=, inbox=/home/user/Maildir, alt= lda(user): Debug: userdb lookup skipped, username taken from USER environment lda(user): Debug: none: root=, index=, indexpvt=, control=, inbox=, alt= lda(user): Debug: Destination address: user(a)blitz.conuropsis.org (source: user@hostname) lda(user): Debug: sieve: Pigeonhole version 0.4.16 (fed8554) initializing lda(user): Debug: sieve: include: sieve_global is not set; it is currently not possible to include `:global' scripts. lda(user): Debug: sieve: Sieve imapsieve plugin for Pigeonhole version 0.4.16 (fed8554) loaded lda(user): Debug: sieve: Sieve Extprograms plugin for Pigeonhole version 0.4.16 (fed8554) loaded lda(user): Debug: sieve: file storage: Using active Sieve script path: /data/home/user/.dovecot.sieve lda(user): Debug: sieve: file storage: Using script storage path: /home/user/sieve lda(user): Debug: sieve: file storage: Relative path to sieve storage in active link: sieve/ lda(user): Debug: sieve: file storage: Using Sieve script path: /data/home/user/.dovecot.sieve lda(user): Debug: sieve: file script: Opened script `test-foofilter' from `/data/home/user/.dovecot.sieve' lda(user): Debug: sieve: Using the following location for user's Sieve script: /data/home/user/.dovecot.sieve lda(user): Debug: Mailbox stdin: Opened mail UID=1 because: header Message-ID (Cache file is unusable) lda(user): Debug: sieve: Opening script 1 of 1 from `/data/home/user/.dovecot.sieve' lda(user): Debug: sieve: Loading script /data/home/user/.dovecot.sieve lda(user): Debug: sieve: Script binary /data/home/user/.dovecot.svbin successfully loaded lda(user): Debug: sieve: binary save: not saving binary /data/home/user/.dovecot.svbin, because it is already stored lda(user): Debug: sieve: Executing script from `/data/home/user/.dovecot.svbin' lda(user): Debug: sieve: action execute: running program: foofilter lda(user): Debug: Mailbox stdin: Opened mail UID=1 because: mail stream lda(user): Debug: waiting for program `/usr/local/lib/dovecot/sieve-execute/foofilter' to finish after 0 msecs lda(user): Debug: program `/usr/local/lib/dovecot/sieve-execute/foofilter'(24669) execution timed out after 2000 milliseconds: sending TERM signal lda(user): Debug: program `/usr/local/lib/dovecot/sieve-execute/foofilter' (24669) did not die after 5000 milliseconds: sending KILL signal and an strace on the dovecot-lda process shows it is in an "epoll_wait(9 ....". The script is very simple: #! /bin/sh cat > /dev/null exit 1 Anyone has a clue? Thanks in advance. Best Regards, Lionel

2 5

Proxy + 2x static passdb not working as expected
by Michael Goth 13 Nov '18

13 Nov '18

Hi all, I'm trying to setup a Dovecot proxy that authenticates the user against two backend servers. If login server1 fails, server2 should be tried. The problem: Only the first server seems to be tried, even if the login fails. Config snippet: protocol imap { passdb { driver = static args = proxy=y nopassword=y host=oldserver1.example.com port=993 ssl=y } passdb { driver = static args = proxy=y nopassword=y host=oldserver2.example.com port=993 ssl=y } } With this config, only accounts on oldserver1.example.com can login. If I reverse the two passdb entries, only accounts on oldserver2.example.com can login. I've done the same with SQL passdb first + static passdb second. That worked as expected. Not sure what I'm doing wrong here. Attached is the output of doveconf -n Thanks Michael Mit freundlichen Grüßen -- Michael Goth .webflow GmbH Geschäftsführer: Andreas Schrei Wasserburger Straße 4 D - 83352 Altenmarkt a. d. Alz Amtsgericht Traunstein HRB 18537 E-Mail: mg(a)webflow.de Tel: +49 (0) 8621 - 99989 - 26 Fax: +49 (0) 8621 - 99989 - 28 Web: www.webflow.de

2 1

dsync / doveadm sync problem
by admin＠awib.it 13 Nov '18

13 Nov '18

Hi, I had an old dovecot server with a working backup script. Basic concept was: - to dsync to a temp folder - using tar to preserve datetime - piping this 7z to benefit from my 16 core cpu - piping this through openssl to encrypt Over time the size of all my mail grew from 3GB to about 70GB. I used to keep the last 14 backups, but this uses a lot of space. I now want to dsync my Maildir onto my NAS via NFS and use the backup tool provided by Synology to have incremental compressed backup. However I cannot get dsync to run. root@mail:/mnt/backup_mail# dsync -f -u USER@DOMAIN backup maildir:/mnt/backup_mail/MAILSERVER_FQDN/DOMAIN/USER/mail dsync(USER@DOMAIN): Error: User initialization failed: Namespace '': stat(/mnt/backup_mail/MAILSERVER_FQDN/DOMAIN/USER/mail) failed: Permission denied (euid=1001(vmail) egid=1001(vmail) missing +x perm: /mnt/backup_mail, UNIX perms appear ok (ACL/MAC wrong?)) root@mail:/mnt/backup_mail# dsync -u USER@DOMAIN backup maildir:/mnt/backup_mail/MAILSERVER_FQDN/DOMAIN/USER/mail dsync(USER@DOMAIN): Error: User initialization failed: Namespace '': stat(/mnt/backup_mail/MAILSERVER_FQDN/DOMAIN/USER/mail) failed: Permission denied (euid=1001(vmail) egid=1001(vmail) missing +x perm: /mnt/backup_mail, dir owner missing perms) ——— Error message changed after removing „-f“. I then applied the folder permissions (chmod +x backup_mail/) and I get a different error: root@mail:/mnt/backup_mail# dsync -f -u USER@DOMAIN backup maildir:/mnt/backup_mail/MAILSERVER_FQDN/DOMAIN/USER/mail dsync(USER@DOMAIN): Error: User initialization failed: namespace configuration error: All list=yes namespaces must use the same separator I found something about the namespace issue, but did not quite understand I guess. (separators seem to differ) From doveconf -n: [...] namespace { list = children location = maildir:/var/vmail/mailboxes/%%d/%%n/Maildir:INDEXPVT=~/Maildir/shared/%%u prefix = shared/%%u/ separator = / subscriptions = yes type = shared } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Trash { auto = subscribe autoexpunge = 183 days special_use = \Trash } prefix = } […] ——— However I only set up the namespace for inbox. root@mail:/mnt/backup_mail# doveconf namespace gives namespace { disabled = no hidden = no ignore_on_failure = no inbox = no list = children location = maildir:/var/vmail/mailboxes/%%d/%%n/Maildir:INDEXPVT=~/Maildir/shared/%%u order = 0 prefix = shared/%%u/ separator = / subscriptions = yes type = shared } namespace inbox { disabled = no hidden = no ignore_on_failure = no inbox = yes list = yes location = mailbox Drafts { auto = subscribe autoexpunge = 0 autoexpunge_max_mails = 0 comment = driver = special_use = \Drafts } mailbox Sent { auto = subscribe autoexpunge = 0 autoexpunge_max_mails = 0 comment = driver = special_use = \Sent } mailbox Spam { auto = subscribe autoexpunge = 60 days autoexpunge_max_mails = 0 comment = driver = special_use = \Junk } mailbox Trash { auto = subscribe autoexpunge = 60 days autoexpunge_max_mails = 0 comment = driver = special_use = \Trash } order = 0 prefix = separator = subscriptions = yes type = private } I guess here we see the config including defaults. Well… I think I only need the inbox namespace either way, so I tried: root@mail:/mnt/backup_mail# dsync -f -u USER@DOMAIN backup maildir:/mnt/backup_mail/MAILSERVER_FQDN/DOMAIN/USER/mail/ -n inbox dsync-local(USER@DOMAIN): Error: read(remote) failed: EOF (version not received) doveadm(USER@DOMAIN): Fatal: execvp(maildir:/mnt/backup_mail/MAILSERVER_FQDN/DOMAIN/USER/mail/) failed: No such file or directory dsync-local(USER@DOMAIN): Error: Remote command process isn't dying, killing it dsync-local(USER@DOMAIN): Error: kill(15306, SIGKILL) failed: Operation not permitted The folder (mnt/backup_mail/MAILSERVER_FQDN/DOMAIN/USER/mail) however does exist. Can anybody tell me if there is something I miss? Thanks in advance! -M

1 0

compressed folders
by Arkadiusz Miśkiewicz 13 Nov '18

13 Nov '18

Hello. Is this still true? https://www.dovecot.org/list/dovecot/2013-March/089084.html Ability to have specific folders compressed only. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

1 0

New install - getting error: "Failed to initialize SSL server context: Couldn't parse DH parameters"
by James Brown 13 Nov '18

13 Nov '18

I’m setting up Dovecot using Homebrew on a new server and am getting this when I try to login via IMAP: Nov 13 14:13:35 auth: Debug: auth client connected (pid=30719) Nov 13 14:13:35 imap-login: Info: Aborted login (no auth attempts in 0 secs): user=<>, rip=::1, lip=::1, secured, session=<gM0HNIN6HtoAAAAAAAAAAAAAAAAAAAAB> Nov 13 14:18:33 auth: Debug: Loading modules from directory: /usr/local/Cellar/dovecot/2.3.2.1/lib/dovecot/auth Nov 13 14:18:33 auth: Debug: Module loaded: /usr/local/Cellar/dovecot/2.3.2.1/lib/dovecot/auth/lib20_auth_var_expand_crypt.so Nov 13 14:18:33 auth: Debug: Read auth token secret from /usr/local/var/run/dovecot/auth-token-secret.dat Nov 13 14:18:33 auth: Debug: auth client connected (pid=30848) Nov 13 14:18:33 imap-login: Error: Failed to initialize SSL server context: Couldn't parse DH parameters: error:0906D06C:PEM routines:PEM_read_bio:no start line: Expecting: DH PARAMETERS: user=<>, rip=::1, lip=::1, secured, session=<q7TJRYN6RdoAAAAAAAAAAAAAAAAAAAAB> Nov 13 14:18:33 imap-login: Info: Disconnected: TLS initialization failed. (no auth attempts in 0 secs): user=<>, rip=::1, lip=::1, secured, session=<q7TJRYN6RdoAAAAAAAAAAAAAAAAAAAAB> I’ve used: Openssl gendh 2048 And put the output: -----BEGIN DH PARAMETERS----- MIIBCAKCAQEA0IF7kQX32IJFm/5HEVwYf7Be4G9iY86MvLiFLL3wHGqcPT3EMsIv YSe5XOT0Q7DGXPOZ+DLlJq8KDHxWKNI6j/0ZaRBrF38CWj8Jqxa8pqo9FVSWj45b JwSLqBSoBIEFWibqSE6L8wlV8xjMsB34xLHduJDNbaBzsooN749CopTkmkuGeXKH waOEbDzlOq+qHEa4bjx2/e/TnPj0kCrMnfeU4QILo1rJwuN4nY6k7fGwgEDVa2hE oOrVfJxxxxxxxxxyyyyyuuuixxxxblahblahblahhhkkkkkkkkkkkkXCGsxhlDQO QmzOhHqPovzbBByO9iR5fu3xbNm9YRxPowIBAg== -----END DH PARAMETERS—— Into a file dh.pem and then added ssl_dh=/usr/local/etc/dovecot/dh.pem To my dovecot.conf file. Reloaded Dovecot but still get the same error. Any suggestions? macOS 10.13.6, Dovecot 2.3.2.1 Any suggestions? Thanks, James.

3 3

Re: New install - getting error: "Failed to initialize SSL server context: Couldn't parse DH parameters"
by Tuomi, Aki 13 Nov '18

13 Nov '18

Actually you need to use ssl_dh=</usr/local/etc/dovecot/dh.pemNote the <Aki -------- Original message --------From: "Michael A. Peters" <mpeters(a)domblogger.net> Date: 13/11/2018 05:44 (GMT+02:00) To: dovecot(a)dovecot.org Subject: Re: New install - getting error: "Failed to initialize SSL server context: Couldn't parse DH parameters" tryopenssl dhparam -out /usr/local/etc/dovecot/dh.pem 2048On 11/12/2018 07:28 PM, James Brown wrote:> I’m setting up Dovecot using Homebrew on a new server and am getting > this when I try to login via IMAP:> > Nov 13 14:13:35 auth: Debug: auth client connected (pid=30719)> Nov 13 14:13:35 imap-login: Info: Aborted login (no auth attempts in 0 > secs): user=<>, rip=::1, lip=::1, secured, > session=<gM0HNIN6HtoAAAAAAAAAAAAAAAAAAAAB>> Nov 13 14:18:33 auth: Debug: Loading modules from directory: > /usr/local/Cellar/dovecot/2.3.2.1/lib/dovecot/auth> Nov 13 14:18:33 auth: Debug: Module loaded: > /usr/local/Cellar/dovecot/2.3.2.1/lib/dovecot/auth/lib20_auth_var_expand_crypt.so> Nov 13 14:18:33 auth: Debug: Read auth token secret from > /usr/local/var/run/dovecot/auth-token-secret.dat> Nov 13 14:18:33 auth: Debug: auth client connected (pid=30848)> Nov 13 14:18:33 imap-login: Error: Failed to initialize SSL server > context: Couldn't parse DH parameters: error:0906D06C:PEM > routines:PEM_read_bio:no start line: Expecting: DH PARAMETERS: user=<>, > rip=::1, lip=::1, secured, session=<q7TJRYN6RdoAAAAAAAAAAAAAAAAAAAAB>> Nov 13 14:18:33 imap-login: Info: Disconnected: TLS initialization > failed. (no auth attempts in 0 secs): user=<>, rip=::1, lip=::1, > secured, session=<q7TJRYN6RdoAAAAAAAAAAAAAAAAAAAAB>> > I’ve used:> > Openssl gendh 2048> > And put the output:> > -----BEGIN DH PARAMETERS-----> MIIBCAKCAQEA0IF7kQX32IJFm/5HEVwYf7Be4G9iY86MvLiFLL3wHGqcPT3EMsIv> YSe5XOT0Q7DGXPOZ+DLlJq8KDHxWKNI6j/0ZaRBrF38CWj8Jqxa8pqo9FVSWj45b> JwSLqBSoBIEFWibqSE6L8wlV8xjMsB34xLHduJDNbaBzsooN749CopTkmkuGeXKH> waOEbDzlOq+qHEa4bjx2/e/TnPj0kCrMnfeU4QILo1rJwuN4nY6k7fGwgEDVa2hE> oOrVfJxxxxxxxxxyyyyyuuuixxxxblahblahblahhhkkkkkkkkkkkkXCGsxhlDQO> QmzOhHqPovzbBByO9iR5fu3xbNm9YRxPowIBAg==> -----END DH PARAMETERS——> > Into a file dh.pem and then added> > ssl_dh=/usr/local/etc/dovecot/dh.pem> > To my dovecot.conf file.> > Reloaded Dovecot but still get the same error.> > Any suggestions?> > macOS 10.13.6, Dovecot 2.3.2.1> > Any suggestions?> > Thanks,> > James.

2 1

replication guide
by lty＠cndns.com 13 Nov '18

13 Nov '18

DOVECOT -N # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24 (124e06aa) # OS: Linux 2.6.32-431.23.3.el6.x86_64 x86_64 CentOS release 6.9 (Final) '''' plugin { ''' mail_replica = tcp:10.1.1.20:1111 # replication_sync_timeout = 2s replication_sync_timeout = 2 '''' } '''' /VAR/LOG/DOVECOT/DOVECOT.LOG doveadm(lty(a)cndns.com): Error: replication(lty(a)cndns.com): Invalid replication_sync_timeout value: 2s I am talking about the replication_sync_timeout = 2s in the configuration file changed to replication_sync_timeout = 2, no prompt error, but I get the following prompt /VAR/LOG/DOVECOT/DOVECOT.LOG Nov 12 14:01:10 replicator: Panic: data stack: Out of memory when allocating 268435496 bytes Nov 12 14:01:10 replicator: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0() [0x3bdd69f74a] -> /usr/lib64/dovecot/libdovecot.so.0() [0x3bdd69f7b6] -> /usr/lib64/dovecot/libdovecot.so.0() [0x3bdd630b8a] -> /usr/lib64/dovecot/libdovecot.so.0() [0x3bdd69d34a] -> /usr/lib64/dovecot/libdovecot.so .0() [0x3bdd69d558] -> /usr/lib64/dovecot/libdovecot.so.0() [0x3bdd6bb818] -> /usr/lib64/dovecot/libdovecot.so.0() [0x3bdd69b0a2] -> /usr/ Lib64/dovecot/libdovecot.so.0(buffer_write+0x89) [>xvebd/b. -> dovecot/replicator() [0x4040d0] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x61) [0x3bdd6b4921] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xbf ) [0x3bdd6b65cf] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x3bdd6b49dc] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x3bdd6b4b98] -> /usr/lib64/do Vecot/libdovecot.so.0(master_service_run+0x13) [0x3bdd63ad43] -> dovecot/replicator(main+0x17e) [0x40461e] -> /lib64/libc.so.6(__libc_start_main+0xfd) [0x3bb6a1ed1d] -> dovecot/ Replicator() [0x4031f9] Nov 12 14:01:10 replicator: Fatal: master: service(replicator): child 19591 killed with signal 6 (core dumps disabled) /VAR/LOG/DOVECOT/SIEVE.LOG Nov 12 13:54:36 lda(lty(a)cndns.com): Warning: replication(lty(a)cndns.com): Remote sent invalid input: - Nov 12 13:54:36 lda(lty(a)cndns.com): Info: sieve: msgid=unspecified: stored mail into mailbox 'Junk' Nov 12 14:01:10 lda(lty(a)cndns.com): Warning: replication(lty@cndnscom): Sync failure: Nov 12 14:01:10 lda(lty(a)cndns.com): Warning: replication(lty(a)cndns.com): Remote sent invalid input: - Please help me, thank you

1 0

Disaster Recovery Help
by Giovanni Bisanti TEST 2 13 Nov '18

13 Nov '18

I lost the whole maildir from my server fro 3 users. They all have iPhones with all the messages safely stored on the Apple Mail app on their phone. There is no way to export them/move them. Is there a way to get Dovecot to just download all the messages and folder structure from the client and restore it on the server? Your help is very very much appreciated. Thanks, ttyllc

4 5

Help Disaster Recovery
by Giovanni Bisanti 12 Nov '18

12 Nov '18

I lost the whole maildir from my server fro 3 users. They all have iPhones with all the messages safely stored on the Apple Mail app on their phone. There is no way to export them/move them. Is there a way to get Dovecot to just download all the messages and folder structure from the client and restore it on the server? Your help is very very much appreciated. Thanks, ttyllc

1 0

Disaster Recovery Help
by Giovanni Bisanti 12 Nov '18

12 Nov '18

I lost the whole maildir from my server fro 3 users. They all have iPhones with all the messages safely stored on the Apple Mail app on their phone. There is no way to export them/move them. Is there a way to get Dovecot to just download all the messages and folder structure from the client and restore it on the server? Your help is very very much appreciated. Thanks, ttyllc

1 0