- dovecot - dovecot.org

Sieve and OX push_notification_drive seem to not work together
by Ralf Becker 21 Jul '20

21 Jul '20

While it's documented that the OX push_notification_driver only supports MessageNew events, it does NOT generate any event if a Sieve script moves the message on arrival to an other folder, neither in INBOX were it original arrives by LMTP, nor in the folder Sieve moves the message. Is that a misconfiguration on my side, or a know / desired limitation or just a bug? I use LMTP to deliver mails from Postfix to Dovecot: protocol lmtp { mail_plugins = $mail_plugins notify push_notification } Does eg. the same need to be configured somehow for the Sieve plugin? Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0

2 2

Questions about Dovecot push notifications
by Ralf Becker 21 Jul '20

21 Jul '20

I read the docu available under: https://doc.dovecot.org/configuration_manual/push_notification/ I'm using Dovecot 2.2.36.4 with directors and a replicating pair of backends using a custom dict with proxy protocol for user- and passdb plus a userdb using sqlite for backup. I understand 2.2 only allows to notify about new arriving mails, not eg. flag-changes which would require 2.3 with LUA. I want to use the ox notification driver with a http url (https seems to be 2.3 only). I read to enable push notifications on a mailbox I need: a) IMAP metadata enabled incl. a backend/driver to store the metadata b) enable push for the individual mailbox using a doveadm command (maybe also via IMAP, which would be easier in my case) My questions are: 1. can I set some static metadata via userdb to enable push for all mailboxes? 2. if no, does setting the metadata on one replicating backend replicates it to the other one too? 3. what purpose does the user=<something@else> argument in the doveadm command to enable push server: doveadm mailbox metadata set -u user(a)example.com -s "" /private/vendor/vendor.dovecot/http-notify user=11@3 Does it replace "user(a)example.com" in the push payload with <something@else>? 4. can I set the required metadata via IMAP command preferable with a (already configured) master user? Thanks in advance :) Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0

1 1

History mails are stored in the tmp/ directory
by lty 21 Jul '20

21 Jul '20

We found that there are historically corrupted mails in the tmp/ directory, For example, Maildir/tmp/ or Maildir/.Drafts/tmp/ exists. We suspect that it may be caused by network transmission, or the user interrupted the network link. Can the dovecot team possibly fix this problem? dovecot --version 2.2.36

3 3

solr and dovecot-2.2.36.4
by Maciej Milaszewski 21 Jul '20

21 Jul '20

Hi Today i try run solr-8.6.0 + dovecot-2.2.36.4 and false I read https://doc.dovecot.org/configuration_manual/fts/solr/#fts-backend-solr Where I get schema.xml and solrconfig.xml for this version solr and dovecot ? I try schema.xml and solrconfig.xml from working solr-6.6.5 (dovecot) "dovecot: org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: Error initializing QueryElevationComponent"

2 1

submission proxy -- where to config/present client cert?
by PGNet Dev 20 Jul '20

20 Jul '20

I've a dovecot instance setup with submission proxy, protocols = imap lmtp submission sieve hostname = internal.mx.example.com submission_relay_host = internal.mx.example.com submission_relay_port = 465 submission_relay_trusted = yes submission_relay_ssl = smtps submission_relay_ssl_verify = yes service submission-login { inet_listener submission { address = 10.2.2.10, 127.0.0.1 port = 50465 ssl = yes } } protocol submission { ssl_cert = < /sec/vmail/mx.example.com.server.EC.crt.pem ssl_key = < /sec/vmail/mx.example.com.server.EC.key.pem ssl_verify_client_cert = no } It submits to a postfix instance, atm on the same host, [internal.mx.example.com]:465 inet n - n - - smtpd -o smtpd_tls_req_ccert=no with that setup, all works as expected. If I turn ON required client cert verification @ postfix, - -o smtpd_tls_req_ccert=no + -o smtpd_tls_req_ccert=yes with that add'l req't, postfix log reports "no client certificate presented" Jul 18 14:52:38 mx postfix/submit-from-dovecot/smtpd[37133]: connect from internal.mx.example.com[10.2.2.10] Jul 18 14:52:39 mx postfix/submit-from-dovecot/smtpd[37133]: Anonymous TLS connection established from internal.mx.example.com[10.2.2.10]: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384 Jul 18 14:52:39 mx postfix/submit-from-dovecot/smtpd[37133]: NOQUEUE: abort: TLS from internal.mx.example.com[10.2.2.10]: No client certificate presented Jul 18 14:53:09 mx postfix/submit-from-dovecot/smtpd[37133]: disconnect from internal.mx.example.com[10.2.2.10] commands=0/0 Clearly, I'm missing config. What in my dovecot submission config^^ do I need to change/add to get it to 'present' a client cert to the postfix relay for client cert verification?

2 2

Set mail to only display mail within 30 or 60 days
by lty 20 Jul '20

20 Jul '20

Set mail to only display mail within 30 or 60 days, Here are two examples. 1. normal E.g: A654 FETCH 2:4 (FLAGS BODY[HEADER.FIELDS (DATE FROM)]) * 2 FETCH (FLAGS (\Seen) BODY[HEADER.FIELDS (DATE FROM)] {73} Date: Tue, 07 May 2020 12:26:55 +0800 From: <test(a)www.chengmail.ml> ) * 3 FETCH (FLAGS (\Seen) BODY[HEADER.FIELDS (DATE FROM)] {62} Date: Tue, 07 May 2020 12:35:34 +0800 From: lty(a)cndns.com ) * 4 FETCH (FLAGS (\Seen) BODY[HEADER.FIELDS (DATE FROM)] {62} Date: Tue, 07 Jul 2020 17:41:53 +0800 From: lty(a)cndns.com ) A654 OK Fetch completed (0.002 + 0.000 + 0.001 secs). 2. Set to display mail within 30 days E.g: A654 FETCH 2:4 (FLAGS BODY[HEADER.FIELDS (DATE FROM)]) * 4 FETCH (FLAGS (\Seen) BODY[HEADER.FIELDS (DATE FROM)] {62} Date: Tue, 07 Jul 2020 17:41:53 +0800 From: lty(a)cndns.com ) A654 OK Fetch completed (0.002 + 0.000 + 0.001 secs). Is there any way to display the result of case 2? I found lua. https://doc.dovecot.org/admin_manual/lua/#mail-lua But I don't know how to edit the lua script, Are there more examples? I also watched the help, but it doesn't help much. https://doc.dovecot.org/configuration_manual/authentication/lua_based_authe… https://doc.dovecot.org/configuration_manual/push_notification/#lua-push-no… Can Lua fulfill my needs?

1 0

I need some help with my Dovecot and Postfix configs - I'm unable to log in on my mail server
by Nils 19 Jul '20

19 Jul '20

Hello, currently I'm working on my first mailserver but I can't log in to the account I made. For now my client (Mozlla Thunderbird) detects the server config (STARTTLS, Port, ...) but it is "Unable to log in at server. Probbly wrong configuration, username or passsword". I know that I added username and password correctly so there must something else be wrong. I run Debian 10 x64 on a fresh installation. Installed are: postfix, postfix-pcre, dovecot-core, dovecot-imapd and dovecot-pop3d. Dovecot is version 2.3.4.1, Postfix is 3.4.10. Here are my configurations: Postfix main.cf: https://pastebin.com/S17jWDQd Postfix master.cf: https://pastebin.com/W0nynZG6 dovecot.conf: https://pastebin.com/tMD90Znn This is what my server logs (mail.info, mail.warn) tell me: root@bgrsld-mail0:~# tail /var/log/mail.info Jul 17 18:22:08 bgrsld-mail0 postfix/submission/smtpd[8472]: improper command pipelining after EHLO from unknown[192.168.2.110]: QUIT\r\n Jul 17 18:22:08 bgrsld-mail0 postfix/submission/smtpd[8465]: disconnect from unknown[192.168.2.110] ehlo=1 quit=1 commands=2 Jul 17 18:22:08 bgrsld-mail0 postfix/submission/smtpd[8472]: disconnect from unknown[192.168.2.110] ehlo=1 quit=1 commands=2 Jul 17 18:24:59 bgrsld-mail0 postfix/submission/smtpd[8485]: warning: dict_nis_init: NIS domain name not set - NIS lookups disabled Jul 17 18:24:59 bgrsld-mail0 postfix/submission/smtpd[8485]: connect from unknown[192.168.2.110] Jul 17 18:24:59 bgrsld-mail0 postfix/submission/smtpd[8485]: improper command pipelining after EHLO from unknown[192.168.2.110]: QUIT\r\n Jul 17 18:24:59 bgrsld-mail0 postfix/submission/smtpd[8485]: disconnect from unknown[192.168.2.110] ehlo=1 quit=1 commands=2 Jul 17 18:28:19 bgrsld-mail0 postfix/anvil[8473]: statistics: max connection rate 2/60s for (submission:192.168.2.110) at Jul 17 18:22:08 Jul 17 18:28:19 bgrsld-mail0 postfix/anvil[8473]: statistics: max connection count 2 for (submission:192.168.2.110) at Jul 17 18:22:08 Jul 17 18:28:19 bgrsld-mail0 postfix/anvil[8473]: statistics: max cache size 1 at Jul 17 18:22:08 root@bgrsld-mail0:~# tail /var/log/mail.warn Jul 17 18:21:50 bgrsld-mail0 postfix/postfix-script[8290]: warning: symlink leaves directory: /etc/postfix/./makedefs.out Jul 17 18:22:08 bgrsld-mail0 postfix/submission/smtpd[8465]: warning: dict_nis_init: NIS domain name not set - NIS lookups disabled Jul 17 18:22:08 bgrsld-mail0 postfix/submission/smtpd[8472]: warning: dict_nis_init: NIS domain name not set - NIS lookups disabled Jul 17 18:24:59 bgrsld-mail0 postfix/submission/smtpd[8485]: warning: dict_nis_init: NIS domain name not set - NIS lookups disabled (I removed any information from older issues that are already solved, thats why mail.warn misses a few lines and there is no mail.err, mail.err hadn't any newer messages) Here is my only line from dovecot's userpass file (/maildata/userpass): nils@intern.xxx.xxx:{CRYPT}$2y$05$kkxElxFGsLSyTJwbEaPZzO/QA33vGY3oGyHcgEZa9rpklgBTKQw9O My postfix vhosts file (/maildir/vhosts) intern.xxx.xxx My postfix vmaps file (/maildir/vmaps) nils(a)intern.xxx.xxx intern.xxx.xxx/nils/ I've also created the hased database with 'postmap /maildata/vmaps' This is the script I've used to create my user database: https://pastebin.com/9uViNqjB I haven't worked with postfiy or dovecot yet so there are many things I don't know. Because of this a lot of my configurations is copied from an iRedMail installation. I know that taking these configs may cause some problems but I don't know where to change them or what else is wrong or missing. Thank you for any help!

6 11

Sieve and handling multiple addresses
by ＠lbutlr 19 Jul '20

19 Jul '20

I an trying to write a sieve action that will take mail that is addressed to a user only it is filed in a mailbox (e.g. "Direct") if it is to the email AND to any other email address, then file it in a mailbox named, e.g. "Cc". And if the mail is not addressed to the user at all, sieve does nothing with it. Message 1: to foo(a)example.com => Direct Message 2: to/cc foo(a)example.com & to/cc to anyone(a)anydomain.tlf => CC Optional: If it contains a specific header like "X-bypass: secret string" => no action Message 3: NOT to/cc foo(a)example.com => no action I've gotten exactly nowhere so far Something like if :allof (header :contains ["to"] ["foo#example.com"], header :contains ["cc"] ["foo#example.com"]) Takes care of the first part of the message 1 and 2 criteria. But then what? -- Was it everything you wanted to find? and did you miss me while you were looking for yourself out there?

5 8

problem with client using TLS
by ratatouille 18 Jul '20

18 Jul '20

Hello! On my testserver running CentOS8 I have installed dovecot v2.3.8. I can connect to the server using claws-mail on my PC but can't using K9-mail on android device. Jul 18 12:24:57 imap-login: Debug: SSL: where=0x10, ret=1: before SSL initialization Jul 18 12:24:57 imap-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization Jul 18 12:24:57 imap-login: Debug: SSL: where=0x2002, ret=-1: before SSL initialization Jul 18 12:24:57 imap-login: Debug: SSL: where=0x2002, ret=-1: before SSL initialization Jul 18 12:24:57 imap-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization Jul 18 12:24:57 imap-login: Debug: SSL alert: where=0x4008, ret=582: fatal protocol version Jul 18 12:24:57 imap-login: Debug: SSL: where=0x2002, ret=-1: error Jul 18 12:24:57 imap-login: Debug: SSL error: SSL_accept() failed: error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Jul 18 12:24:57 imap-login: Info: Disconnected (no auth attempts in 0 secs): user=<>, rip=87.182.44.142, lip=185.84.81.115, TLS handshaking: SSL_accept() failed: error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol, session=<uppwr7SqrrpXtiyO> Jul 18 12:24:57 imap-login: Debug: SSL error: SSL_accept() syscall failed: Invalid argument Tried different settings without luck. grep -v '^#' 10-ssl.conf ssl = yes ssl_cert = </etc/letsencrypt/live/smtp.dualbit.de/fullchain.pem ssl_key = </etc/letsencrypt/live/smtp.dualbit.de/privkey.pem ssl_dh = </etc/dovecot/dh.pem ssl_min_protocol = TLSv1.2 ssl_cipher_list = PROFILE=SYSTEM ssl_prefer_server_ciphers = yes Can somebody help solving this? Kind regards Andreas

3 8

Non-standard socket locations w/ Dovecot + AWS Linux
by Antonio Leding 18 Jul '20

18 Jul '20

# === The post relates to Dovecot v2.2 running on AWS Linux v1 === # Hello all… The Dovecot sockets on this server are installed in two different locations one of which is different from what I have on my other Dovecot installations which run on Centos-7. Here are the sockets paths: — all sockets EXCEPT "auth-master” —> "/usr/local/var/run/dovecot” <<<<< this appears to be the default for this server — "auth-master” —> "/var/run/dovecot” <<<<< without this statement, Dovecot authentication always failed. The config stanza for this is shown below: service auth { unix_listener auth-userdb { path = /var/run/dovecot/auth-master mode = 0600 user = vmail } } ============ The above has been working great for several years but the time eventually came where I needed to upgrade. This of course meant I had to move lots of maildata between the servers. Unfortunately, the “auth-userdb" config mentioned above prevented “dsync" from working properly. This is the error I received when trying “dsync”: Error: userdb lookup: connect(/usr/local/var/run/dovecot/auth-userdb) failed: No such file or directory This error led me to the eventual fix which was adding the following to the “dovecot.conf” file: auth_socket_path = /var/run/dovecot/auth-master ============ So, to my questions: (1) Why would the socket path on this AWS installation be different from what I see on my Centos-based Dovecot servers and also what I’ve read in several Dovecot mailer discussions? (2) Can the default socket path be set at compile time? If so, then I'm thinking maybe the AWS folks — for whatever reason — decided to install all sockets (except ”auth-master”) in the “/usr/local/var/run/dovecot” directory. Are there any benefits or reason to do this? (3) Is there any requirement that the “auth-master” socket be located in the “/var/run/dovecot” directory? Also, there is nothing else in that directory — just the “auth-master” socket file — that’s it. (4) Why is “dsync" looking for "auth-userdb" in the “/usr/local/var/run/dovecot” directory despite the “auth" stanza stating it is located elsewhere in "/var/run/dovecot”? (5) And last, why do I need to add the “auth_socket_path” statement to get “dsync” working even though the socket path is stated in the “auth" stanza? Thanks in advance for your time on this. I know this is mostly to help educate me on what is going on so I really appreciate your feedback…

1 0