- dovecot - dovecot.org

Self-signed TLS client certificates
by Marvin Gülker 16 Jun '19

16 Jun '19

Dear List, I self-host my e-mail and run Dovecot since ever I do that. Dovecot version is 2.3.4.1 (f79e8e7e4), running on Debian testing. Now I am trying to configure Dovecot for client TLS certificates. I have a self-signed certificate whose private key resides on a smartcard (Yubikey, to be exact). I wanted Dovecot to accept that TLS client certificate instead of a password. So I searched and found this wiki page: <https://wiki2.dovecot.org/SSL/DovecotConfiguration#Client_certificate_verif…> But that Wiki page says: > The CA file should contain the certificate(s) followed by the matching > CRL(s). Note that the CRLs are required to exist. I have now messed three hours or so with OpenSSL to get a CRL generated for my self-signed certificate, but I can't get that to work (the problem appearently being that OpenSSL doesn't play well with private keys on smartcards). It doesn't make sense anyway, why does one need a CRL for a self-signed certificate? If the self-signed certificate's key gets compromised, the CRL does not help at all. So, here are my questions: 1. Is a CRL really a hard requirement? 2. If not: can I just use the self-signed certificate of my private key for the ssl_ca setting? 3. If yes: any idea how I can generate a CRL for my smartcard-bound self-signed certificate? Marvin -- Blog: https://mg.guelker.eu

2 3

failed to pipe to program sa-learn-spam.sh
by ＠lbutlr 16 Jun '19

16 Jun '19

Error: program `/usr/lib/dovecot/sieve/sa-learn-spam.sh' terminated abnormally, signal 11 Error: sieve: pipe action: failed to pipe message to program `sa-learn-spam.sh': refer to server log for more information. [2019-05-29 17:59:12] What server log? This is all that get logged. # pwd /usr/lib/dovecot/sieve # ls -lsa > total 96 > 8 drwxrwxrwx 3 root wheel 512 Jun 18 2018 . > 8 drwxr-xr-x 3 root wheel 512 May 17 17:54 .. > 8 -rw-r--r-- 1 root wheel 86 Jun 15 2018 default.sieve > 8 drwxr-xr-x 2 root wheel 512 Jun 13 2018 global > 8 -rw-r--r-- 1 root wheel 62 May 14 2018 mark-read.sieve > 8 -rw-r--r-- 1 kremels wheel 192 Jun 17 2018 mark-read.svbin > 8 -rwxr-xr-x 1 root wheel 314 Feb 12 2018 report-ham.sieve > 8 -rw-r--r-- 1 lbutler wheel 448 Jun 18 2018 report-ham.svbin > 8 -rwxr-xr-x 1 root wheel 199 Feb 12 2018 report-spam.sieve > 8 -rw-r--r-- 1 kreme wheel 354 Jun 15 2018 report-spam.svbin > 8 -rwxr-xr-x 1 root wheel 131 Jun 18 2018 sa-learn-ham.sh > 8 -rwxr-xr-x 1 root wheel 54 Feb 12 2018 sa-learn-spam.sh # cat sa-learn-spam.sh > #!/bin/sh > exec /usr/local/bin/sa-learn -u ${1} --spam # ls -ls /usr/local/bin/sa-learn > 96 -rwxr-xr-x 1 root wheel 45939 May 29 09:59 /usr/local/bin/sa-learn report-spam.sieve: > require ["vnd.dovecot.pipe", "copy", "imapsieve", "environment", "variables"]; > > if environment :matches "imap.user" "*" { > set "username" "${1}"; > } > > pipe :copy "sa-learn-spam.sh" [ "${username}" ]; in doveconf I have: > 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 > > plugin { > imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve > imapsieve_mailbox1_causes = COPY > imapsieve_mailbox1_name = Junk > … It WAS working. -- Women and cats will do as they please, and men and dogs should relax an get used to the idea.

3 6

NOTIFY: bug on mailbox renaming and deletion ?
by kael 16 Jun '19

16 Jun '19

Hello, Testing the NOTIFY extension on imap.vivaldi.net, seems there's a bug when a mailbox is renamed or deleted. Requesting events with: A1 NOTIFY SET (inboxes (SubscriptionChange MailboxName)) Here are the sent events: - mailbox creation with automatic subscription (ok): * LIST () "." foo * LIST (\Subscribed) "." foo - mailbox renaming (bug ?): * LIST () "." bar ("OLDNAME" (foo)) * LIST (\Subscribed) "." bar * LIST () "." foo - mailbox deletion (bug ?): * LIST (\NonExistent) "." Trash.bar * LIST () "." Trash.bar It seems that for the two latter cases, the last received event is incorrect, Dovecot notifying of mailbox unsubscription after the mailbox has been renamed or deleted. In that case a client would consider those two last events not as mailbox renaming or deletion, but as a mailbox creation, wouldn't it ? Am I missing something ? Cheers. -- kael

1 0

sdbox format, quota not maildir, and public folder
by David Mehler 16 Jun '19

16 Jun '19

Hello, I'm using Dovecot 2.3.x and using dbox as mailbox storage format, specifically sdbox. I'm getting an error from quota about namespace is not maildir is there a setting I have to use for quota to use the sdbox?

1 0

Dovecot 2.3 error, FreeBSD 12 in a jail
by David Mehler 15 Jun '19

15 Jun '19

Hello, I'm trying to get Dovecot going on my system. It's a FreeBSD 12.0-RELEASE system and it's running dovecot 2.3 via ports in a jail. I'm getting the same error message(s) as in this bug report, which has been marked as closed: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225078 Dovecot is not starting at all in this jail when starting with service dovecot start. A service dovecot status also reveals the error message about /var/run/dovecot/dovecot.conf file, but a doveconf -n does not reveal any configuration file issues. I did put a symlink in /var/run/dovecot to /usr/local/etc/dovecot/dovecot.conf, this did not correct the issue. Any suggestions welcome. Thanks. Dave.

2 1

LMTP doesn't save to +mailbox
by ＠lbutlr 14 Jun '19

14 Jun '19

Since switching to lmtp in dovecot, mail to user+mailboix(a)example.com does not get saved in ‘.mailbox’ as it did with LDA, instead it gets saved into the INBOX. If it matters, these are users who do NOT have a ~/.active_sieve file. I could understand (though it would bene a bit annoying) if the save overrode this mechanism. I did add lmtp_save_to_detail_mailbox = yes in the protocol lmtp block protocol lmtp { postmaster_address = postmaster(a)covisp.net # required mail_plugins = quota sieve info_log_path = /var/log/dovecot-lmtp.log lmtp_save_to_detail_mailbox = yes } This is the error I am getting when sending to luser+covisp(a)covisp.net lmtp(luser(a)covisp.net)<91193><EqkiJV70A105ZAEAIdGjjQ>: Error: sieve: msgid=<A3ED963A-97FB-4A1F-9F09-45F2AEA96CF6(a)kreme.com>: failed to store into mailbox 'covisp': Mailbox doesn't exist: covisp lmtp(luser(a)covisp.net)<91193><EqkiJV70A105ZAEAIdGjjQ>: Error: sieve: Execution of script /usr/lib/dovecot/sieve/default.sieve failed with unsuccessful implicit keep # cat /usr/lib/dovecot/sieve/default.sieve [13:32] [/var/log] require "fileinto"; if header :contains "X-spam-flag" "YES" { fileinto "Junk"; } (This file hasn’t changed in a year, so it worked fine with the lda instead of the lmtp setup. I mean, I can probably just write a sieve to do it. Let me think… if header :regex "to" “+(.*)@" { fileinto :create “${1}"; stop; } Seems like it should work. Should I add this to default.sieve? # 2.3.6 (7eab80676): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.6 (92dc263a) # OS: FreeBSD 11.2-RELEASE-p10 i386 # Hostname: mail.covisp.net auth_failure_delay = 5 secs auth_mechanisms = PLAIN LOGIN default_client_limit = 4096 default_process_limit = 1024 default_vsz_limit = 768 M disable_plaintext_auth = no first_valid_uid = 89 imap_id_log = * login_log_format_elements = user=<%u> %r %m %c mail_location = maildir:~/Maildir mail_max_userip_connections = 90 managesieve_notify_capability = mailto managesieve_sieve_capability = editheader fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Archive { auto = subscribe special_use = \Archive } mailbox Drafts { special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /usr/local/etc/dovecot/sql.conf driver = sql } plugin { imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/usr/lib/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * imapsieve_mailbox3_before = file:/usr/lib/dovecot/sieve/mark-read.sieve imapsieve_mailbox3_causes = COPY imapsieve_mailbox3_name = Archive quota_rule2 = .EXPUNGED:ignore sieve = file:~/.sieve;active=~/.active_sieve sieve_default = /usr/lib/dovecot/sieve/default.sieve sieve_default_name = spamassassin sieve_extensions = +editheader sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_pipe_bin_dir = /usr/lib/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms sieve_user_log = ~/sieve.log } service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } service imap-login { 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 } } service stats { unix_listener stats-reader { group = dovecot mode = 0666 user = } unix_listener stats-writer { group = dovecot mode = 0666 user = } } ssl_cert = </usr/local/etc/dehydrated/certs/covisp.net/fullchain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.1 userdb { args = /usr/local/etc/dovecot/sql.conf default_fields = uid=vpopmail gid=vchkpw mail_location=maildir:/usr/local/virtual/%u/Maildir mail=maildir:/usr/local/virtual/%u/Maildir driver = sql } protocol imap { mail_plugins = " imap_sieve" } protocol lmtp { info_log_path = /var/log/dovecot-lmtp.log lmtp_save_to_detail_mailbox = yes mail_plugins = quota sieve postmaster_address = postmaster(a)covisp.net }

1 2

Dovecot director: show user breakdown by director?
by Eirik Rye 14 Jun '19

14 Jun '19

Hi, We have recently started using the director in some tests. We are using the static passdb setup (proxy=y nopassword=y) for now, where authentication is done on the downstream IMAP servers. "dovecot director status" shows a breakdown of proxied connections per backend, but there does not seem to be a similar breakdown of user connections per director. The output of "doveadm who" is empty. I assume this is due to there being no local userdb/passdb on the directors? root@xxx:/etc/dovecot/conf.d# doveadm who username # proto (pids) (ips) Is there a way in Dovecot to see which (or even how many) users are connected to a specific director without having to count TCP connections? Best regards, Eirik Rye

2 2

Addheader specified field name `Reply-To:' is invalid.
by ＠lbutlr 14 Jun '19

14 Jun '19

Well, progress. At least now editheader loads. Sadly that brings up new errors. specified field name `Reply-To:' is invalid. if header :contains "List-id" "<users.spamassassin.apache.org>" { addheader "Reply-To:" "<users.spamassassin.apache.org>"; addheader "X-added-reply-To:" "True"; fileinto :create “spamassassin"; stop;} -- You only had to look into Teatime's mismatched eyes to know one thing, which was this: if Teatime wanted to find you he would not look everywhere. He'd look in only one place, which would be the place where you were hiding. —Hogfather

2 3

MultiMaster dsync (cluster1 cluster2 cluster3)
by Matthew Brown 14 Jun '19

14 Jun '19

Will MultiMaster dsync work fine or will be big problems ? I configured dovecot to dsync from serv1 to serv2 to serv3 and repeat to serv1 to serv2 to serv3 and repeat... When email received to serv2, it will be synced to serv3, and serv3 will sync it to serv1, and serv1 will sync it to serv2 and will stop here because emails matched. What problems can be with this kind of configuration ? (except that if one of server(cluster) will be stopped, sync will be stopped too until cluster is online again)

2 1

Sieve rewrite headers?
by ＠lbutlr 14 Jun '19

14 Jun '19

I’ve bene looking for examples on how to do this, but so far am coming up short. I want to check certain messages for a reply-ro header and if it is present, rewrite it to X-Reply-To: and then add my own reply-to header. I don’t see anything in the various sieve examples I’ve found on altering the actual message. There is the editheader extension, but I failed to find documentation or examples on how to use it. It appears that I can add a header and delete a header (addheader deleteheader?) but not rewrite one. So something like if header “Reply-to: foo(a)bar.xn--tld-9o0a { addheader "X-Reply-To: foo(a)bar.xn--tld-9o0a deleteheader “Reply-To:” addheader "X-Reply-To: bar(a)foo.xn--tld-9o0a } ?? Do I need to delete the header or will the add header overwrite the one that is there? Also, how do people manage different sieve files? Just cat them all into the active one, or is there a mechanism to import/switch/load other files?

2 1