February 2017 - dovecot

Sieve Script Replication Gliches (Report #2)
by Reuben Farrelly 26 Feb '17

26 Feb '17

Hi, I've observed some odd behaviour with dsync replication between two hosts, specifically to do with sieve script replication. In short, I have two hosts which replicate in a master-master type setup where almost all of the reads and writes happen to just one of the two hosts. They are both running 2.2.devel (9dc6403), which is close to the latest 2.2 -git . Pigeonhole is running master-0.4 . This is on x86_64 Gentoo. Normal mail replication between Maildir's for all users works fine, however it appears that something recently committed to the code has broken sieve script replication between the two. I am sure this did once work. Replication is via tcps: . Sieve scripts on the lesser-used host are not up to date by an order of days/weeks with the main host and they don't seem to re-replicate - even if the rules don't exist at all on the replica. The symptoms and effects look to be the same as this (unanswered) post from December: http://dovecot.org/list/dovecot/2015-December/102690.html I am not sure how to view the transaction log files, but I am seeing the same symptoms, ie no live replication, and on the lesser-used host almost all the scripts were old and some had the 1970 date on them. Even after forcing a [dsync replication replicate '*'] the scripts are not replicated. As it stands now there are no sieve scripts on one of the two members and the system seems unable to replicate by itself. Secondly, I am also seeing some doubled up outputs if I run 'doveadm sieve list -A': thunderstorm reuben # doveadm sieve list -A reuben rules ACTIVE liam rules ACTIVE kaylene rules ACTIVE reuben rules ACTIVE liam rules ACTIVE kaylene rules ACTIVE ... Has anyone else experienced the replication problem? Are sieve scripts actually replicating in live time for other 2.2.24/2.2.25 users as well? For me I didn't notice this till I went looking so I wonder if other people are experiencing this but just not aware of it yet...? Reuben

4 9

Replication sieve scripts.
by Luescher Claude 26 Feb '17

26 Feb '17

Hello, Following up on old thread: http://www.dovecot.org/pipermail/dovecot/2014-December/099003.html I have the exact same issue with 2.2.10: ii dovecot-antispam 2.0+20130822-2 amd64 Dovecot plugins for training spam filters ii dovecot-core 1:2.2.10-1 amd64 secure POP3/IMAP server - core files ii dovecot-imapd 1:2.2.10-1 amd64 secure POP3/IMAP server - IMAP daemon ii dovecot-ldap 1:2.2.10-1 amd64 secure POP3/IMAP server - LDAP support ii dovecot-lmtpd 1:2.2.10-1 amd64 secure POP3/IMAP server - LMTP server ii dovecot-managesieved 1:2.2.10-1 amd64 secure POP3/IMAP server - ManageSieve server ii dovecot-mysql 1:2.2.10-1 amd64 secure POP3/IMAP server - MySQL support ii dovecot-pop3d 1:2.2.10-1 amd64 secure POP3/IMAP server - POP3 daemon ii dovecot-sieve 1:2.2.10-1 amd64 secure POP3/IMAP server - Sieve filters support As even his version should already support sieve replication through dsync mine would have to support it for sure but I would like to hear a confirmation from the developers. The mail sync just works perfectly between the 2 nodes, it is only the sieve scripts which don't get replicated. I have tried to add additional sieve related options to the replicator: service replicator { process_min_avail = 1 } plugin { mail_replica = tcp:1.2.3.4 replication_full_sync_interval = 1 hours #Added (makes no difference) sieve = ~/.dovecot.sieve sieve_dir = ~/sieve_after sieve_extensions = +vnd.dovecot.duplicate sieve_duplicate_period = 1h #Added (makes no difference) } service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } It did not help. If there is one way I would like to get this work without upgrading dovecot. Thank you.

4 12

v2.2.28: var-expand.c
by Ruga 26 Feb '17

26 Feb '17

var-expand.c:687:17: warning: passing an object that undergoes default argument promotion to 'va_start' has undefined behavior [-Wvarargs] va_start(args, key2); ^ var-expand.c:674:58: note: parameter of type 'char' is declared here var_expand_table_build(char key, const char *value, char key2, ...) ^

2 1

v2.2.28: patches (to use libressl 2.4.5) and test error (strftime)
by Ruga 26 Feb '17

26 Feb '17

t_strftime and variants now .......................................... : ok test-time-util.c:123: Assert failed: strcmp(t_strftime(RFC2822_FMT, gmtime(&ts)), exp) == 0 test-time-util.c:124: Assert failed: strcmp(t_strfgmtime(RFC2822_FMT, ts), exp) == 0 t_strftime and variants fixed timestamp .............................. : FAILED timings 0 ............................................................ : ok

4 7

sieve_imapsieve centos 7
by Matthew Broadhead 25 Feb '17

25 Feb '17

i am using CentOS 7 centos-release-7-3.1611.el7.centos.x86_64 with dovecot dovecot-2.2.10-7.el7.x86_64. i am trying to set up AntiSpam with IMAPSieve but the package seems to be lacking sieve_imapsieve. is there anything i can do? i am not really interested in compiling from source because i like to receive security updates automatically. 2017-02-24 21:57:00auth: Error: net_connect_unix(anvil-auth-penalty) failed: Permission denied 2017-02-24 21:57:00master: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) 2017-02-24 21:57:00managesieve: Fatal: Plugin 'sieve_imapsieve' not found from directory /usr/lib64/dovecot/sieve 2017-02-24 21:57:00config: Error: managesieve-login: dump-capability process returned 89 2017-02-24 21:57:05imap: Fatal: Plugin 'imap_sieve' not found from directory /usr/lib64/dovecot 2017-02-24 21:57:05imap: Fatal: Plugin 'imap_sieve' not found from directory /usr/lib64/dovecot 2017-02-24 21:57:08imap: Fatal: Plugin 'imap_sieve' not found from directory /usr/lib64/dovecot 2017-02-24 21:57:08imap: Fatal: Plugin 'imap_sieve' not found from directory /usr/lib64/dovecot 2017-02-24 21:57:10imap: Fatal: Plugin 'imap_sieve' not found from directory /usr/lib64/dovecot 2017-02-24 21:57:10imap: Fatal: Plugin 'imap_sieve' not found from directory /usr/lib64/dovecot

3 3

Re: sieve_imapsieve centos 7
by Aki Tuomi 25 Feb '17

25 Feb '17

imapsieve needs much newer dovecot and sieve. ---Aki TuomiDovecot oy -------- Original message --------From: Ben <ben+dovecot(a)list-subs.com> Date: 25/02/2017 12:33 (GMT+02:00) To: dovecot(a)dovecot.org Subject: Re: sieve_imapsieve centos 7 >> i am using CentOS 7 centos-release-7-3.1611.el7.centos.x86_64 with >> dovecot dovecot-2.2.10-7.el7.x86_64. i am trying to set up AntiSpam >> with IMAPSieve but the package seems to be lacking sieve_imapsieve. is >> there anything i can do? i am not really interested in compiling from >> source because i like to receive security updates automatically. > The imapsieve plugin for pigeonhole was introduced in version 0.4.14 > for dovecot 2.2.24, with your current packages i'd say there is > nothing you can do except to find some sort of extra packages (i'm not > familiar with centos...) I have dovecot and sieve working on CentOS 7 Only using two packages dovecot.x86_64 1:2.2.10-7.el7 @base dovecot-pigeonhole.x86_64 1:2.2.10-7.el7 @base

2 1

sieve file backend: invalid option `active=~/.dovecot.sieve'
by Ben 25 Feb '17

25 Feb '17

Hi, I am seeing the followin error in my logs (doveconf -n at the bottom of this mail): Feb 13 16:59:59 mxf dovecot: lmtp(45560, bp(a)example.com) Error: cs3NOQ7moVj4sQXXXXX: sieve: sieve file backend: invalid option `active=~/.dovecot.sieve' Feb 13 16:59:59 mxf dovecot: lmtp(45560, bp(a)example.com) Error: cs3NOQ7moVj4sQXXXXX: sieve: failed to access user's Sieve script file:~/sieve;active=~/.dovecot.sieve (temporary failure) Looking at http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration, the syntax "sieve = file:~/sieve;active=~/.dovecot.sieve" in my config is correct ? Is this a false error that is only appearing because this is a newly created user with no sieve file ? If this is the case, how do I tell dovecot not to error out and allow the mail ? Thanks ! # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-514.6.1.el7.x86_64 x86_64 CentOS Linux release 7.3.1611 (Core) auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = sha1 first_valid_uid = 1000 mail_location = maildir:~/Maildir 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 environment mailbox date ihave enotify 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 } passdb { driver = pam } passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap lmtp service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = its_virtmail mode = 0660 user = its_virtmail } } service imap-login { process_min_avail = 3 } service lmtp { process_min_avail = 5 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } user = its_virtmail } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieves { address = port = 5190 ssl = yes } } ssl = required ssl_cert = <REMOVED ssl_cipher_list = REMOVED ssl_dh_parameters_length = 2048 ssl_key = </REMOVED ssl_prefer_server_ciphers = yes ssl_protocols = !SSlv2 !SSLv3 userdb { driver = passwd } userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } protocol lmtp { mail_plugins = sieve postmaster_address = me(a)example.com } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address = postmaster quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r } protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 20 }

2 4

Users with multiple password
by Eirik Rye 24 Feb '17

24 Feb '17

Hi! ~ dovecot --version 2.2.22 (fe789d2) I am wondering if there is a way to set up virtual users with multiple valid passwords. We want to be able to provide users with device/app-specific passwords for their email accounts, as well as being able to create temporary "access tokens" for technical support when required. I quickly found out that passdb using passwd-file or an sql-backend does not support returning multiple entries ("Error: passwd-file /etc/dovecot/virtual.passwd: User rye exists more than once"). The documentation mentions that you can pass the plain-text password on to the MySQL-server for verification, and I suppose multiple passwords could could work, given a query like this (pseudo-SQL): `SELECT password FROM account WHERE user = '%u' AND domain = '%d' AND password = TO_BASE64((SHA2('%w', 512));` However, having Dovecot pass the plain-text password and letting the database deal with the hashing and encoding doesn't seem like a very "clean" solution. Preferably, dovecot should be the only piece of software touching the plain-text. Ideally, I would like the following behavior: 1. passdb results multiple possible hashed passwords for the user 2. dovecot attempts the passwords in order 3. login fails normally if none of the passdb results match Does anyone have any experience, or tips for setting up this type of behavior? Other ideas we have touched upon are: 1. Different usernames (eg. 'user_device' or 'user_application') 2. Multiple passdbs(?) Best regards, Eirik Rye

2 2

doveadm "-v" optoin doesn't do anything ?
by Ben 24 Feb '17

24 Feb '17

Hi, On 2.2.10, running the following doveadm -v -o mail_fsync=never backup -R -u my(a)example.com imapc: There is zero output ? Running -D instead of -v it spews out debug messages. Any ideas ? Ben

1 0

Re: Problem with Let's Encrypt Certificate
by Joseph Tam 23 Feb '17

23 Feb '17

yacinechaouche(a)yahoo.com writes: > Interesting. Is there any particular benefit in having only one file > for both certificate and private key ? I find that putting private key > in a separate file feels more secure. It's convenient to have key and cert in one place if you don't need the certificate to be publically readable. Keeping it in separate files would add slightly more security (defense in depth), that would protect from, for example, an admin fumble or bug in the SSL library. "Michael A. Peters" <mpeters(a)domblogger.net> writes: >> I use dehydrated (with Cloudflare DNS challenges) and as far as I know, >> it seems to generate a new private key every time. > > Yeah that would be a problem for me because I implement DANE. It's on my to-do list, but I think you can use dehydrated in signing mode. --signcsr (-s) path/to/csr.pem Sign a given CSR, output CRT on stdout (advanced usage) In this way, you can reuse private key, as well as making it more secure by removing a privileged operations (private key acces) allowing dehydrated to be run as a non-privilged/separate user. Joseph Tam <jtam.home(a)gmail.com>

2 2