- dovecot - dovecot.org

Feature request: ssl-cert config
by Marc Roos 16 Nov '19

16 Nov '19

I am not sure why this </ is used in the configuration. But I hoped it would concatenate the ssl_cert to have multiple certificates. So one could use it multiple times, as needed. It would be nice to be able to specify the intermediate certificate (bundle) separate from the certificate, so when updating the certificate I just have to replace this file. Something like local_name mail.xxxxxx.xxx { ssl_key = </etc/pki/tls/private/mail.xxxxxx.xxx.key ssl_cert = </etc/pki/tls/certs/mail.xxxxxx.xxx.crt ssl_cert = </etc/pki/tls/certs/SectigoIntermediate.crt } Or local_name mail.xxxxxx.xxx { ssl_key = </etc/pki/tls/private/mail.xxxxxx.xxx.key ssl_cert = </etc/pki/tls/certs/mail.xxxxxx.xxx.crt ssl_int = </etc/pki/tls/certs/SectigoIntermediate.crt } dovecot-2.2.36-3.el7_7.1.x86_64

1 0

SCRAM-SHA-1-PLUS / SCRAM-SHA-224(-PLUS) / SCRAM-SHA-256(-PLUS), SCRAM-SHA-384(-PLUS) and SCRAM-SHA-512(-PLUS) supports
by - Neustradamus - 15 Nov '19

15 Nov '19

Dear all, I send you a new email to know what is the progress of SCRAM-SHA-***(-PLUS) supports? Currently there is only SCRAM-SHA-1: https://doc.dovecot.org/configuration_manual/authentication/password_scheme…. - RFC6331: Moving DIGEST-MD5 to Historic: https://tools.ietf.org/html/rfc6331 - RFC5802: Salted Challenge Response Authentication Mechanism (SCRAM) SASL and GSS-API Mechanisms: https://tools.ietf.org/html/rfc5802 - RFC7677: SCRAM-SHA-256 and SCRAM-SHA-256-PLUS Simple Authentication and Security Layer (SASL) Mechanisms: https://tools.ietf.org/html/rfc7677 - since 2015-11-02 I have seen several months ago, commits about SCRAM-SHA-256. For your information, Cyrus SASL supports: - SCRAM-SHA-1(-PLUS) - SCRAM-SHA-224(-PLUS) - SCRAM-SHA-256(-PLUS) - SCRAM-SHA-384(-PLUS) - SCRAM-SHA-512(-PLUS) -> https://cyrusimap.org/sasl/sasl/authentication_mechanisms.html You can see more and more informations here: https://github.com/scram-xmpp/info/issues/1 Thanks in advance. Regards, Neustradamus

1 0

ACL's with SQL/from mysql table
by Jorge Bastos 15 Nov '19

15 Nov '19

Howdy, Would someone point me to a good howto on how to implement ACL from an sql table? Thanks in advanced,

1 0

IMAP4 extensions for Visual Voicemail (VVM)
by Rajesh Bansal 15 Nov '19

15 Nov '19

Hi Team, I need to develop Visual VoiceMail solution. In this solution I need a IMAP4 server, from which I can get a hit for each mail retrieval. Can anyone help me if dovecot can be used for this purpose. BR, Rajesh Bansal

5 5

SASL AUTH with postfix
by Jorge Bastos 15 Nov '19

15 Nov '19

Hi, I just moved from Cyrus SASL to Dovecot SASL, with postfix. Works great, and no issue with non-ascii chars, has i had with Cyrus. With Cyrus i was getting the username/passwd via SQL, with this: sql_select: select password from smtp_auth_users where username='%u@%r' and status='true' worked ok for users with email addresses, and i had some special users that were just a name, like "user-1", and i was able to AUTH it. Postfix had: smtpd_sasl_local_domain = fastmail and in the database i had the username in the format: user-1@fastmail and worked ok. How can i have the same with dovecot SASL? Thanks in advanced,

3 7

Crash when moving mail from Inbox to Trash
by marvin alcantara 14 Nov '19

14 Nov '19

Hi, I am developing a dovecot plugin, and inside my plugin I am implementing my own expunge function. Inside my function, I am calling the following lines of code: if (storage->v.mail_open(mail, &offset, &mail->open_file) < 0) return -1; The mail_open virtual function is an invalid address. The storage should be mdbox however, it seems that it didn't get the correct mdbox_mail_open of mdbox-storage. Do you have any suggestions as to why this is happening? dovecot version:2.3.7 (a3d493f) Sincerely,Marvin

1 0

RFC 5258 violation: incomplete response for "LIST ($OPT RECURSIVEMATCH) ..."
by Guilhem Moulin 12 Nov '19

12 Nov '19

Hi there, RFC 5258 (IMAP4 LIST command extensions) defines a ‘RECURSIVEMATCH’ selection option which “forces the server to return information about parent mailboxes that don't match other selection options, but have some submailboxes that do.” (Section 3.5 makes the requirement even clearer.) However that's not what Dovecot 2.3.7 does. AFAICT no LIST response is returned for mailboxes that don't meet the selection criteria, regardless of whether they have a child that does. The violation is visible when reproducing example #9 from Section 5 [0]: $ env -i USER=user HOME=/dev/shm/dovecot-test/user PATH=/usr/bin:/bin \ doveadm -c /tmp/dovecot.conf mailbox create foo2 baz2 $ env -i USER=user HOME=/dev/shm/dovecot-test/user PATH=/usr/bin:/bin \ doveadm -c /tmp/dovecot.conf mailbox create -s \ foo2/{bar1,bar2} baz2/{bar2,bar22,bar222} eps2 eps2/mamba qux2/bar2 $ env -i USER=user HOME=/dev/shm/dovecot-test/user PATH=/usr/bin:/bin \ doveadm -c /tmp/dovecot.conf exec imap S: * PREAUTH [CAPABILITY IMAP4rev1 … LIST-EXTENDED …] Logged in as user C: D01 LIST "" "*" S: * LIST (\Noselect \HasChildren) "/" qux2 S: * LIST (\HasNoChildren) "/" qux2/bar2 S: * LIST (\HasChildren) "/" eps2 S: * LIST (\HasNoChildren) "/" eps2/mamba S: * LIST (\HasChildren) "/" baz2 S: * LIST (\HasNoChildren) "/" baz2/bar222 S: * LIST (\HasNoChildren) "/" baz2/bar22 S: * LIST (\HasNoChildren) "/" baz2/bar2 S: * LIST (\HasChildren) "/" foo2 S: * LIST (\HasNoChildren) "/" foo2/bar2 S: * LIST (\HasNoChildren) "/" foo2/bar1 S: * LIST (\HasNoChildren) "/" INBOX S: D01 OK List completed (0.006 + 0.000 + 0.005 secs). C: D02 LIST (SUBSCRIBED) "" "*" S: * LIST (\Subscribed) "/" foo2/bar1 S: * LIST (\Subscribed) "/" foo2/bar2 S: * LIST (\Subscribed) "/" baz2/bar2 S: * LIST (\Subscribed) "/" baz2/bar22 S: * LIST (\Subscribed) "/" baz2/bar222 S: * LIST (\Subscribed) "/" eps2 S: * LIST (\Subscribed) "/" eps2/mamba S: * LIST (\Subscribed) "/" qux2/bar2 S: D02 OK List completed (0.001 + 0.000 secs). A LIST command with ‘RECURSIVEMATCH SUBSCRIBED’ selection options produces an incomplete response: C: D03 LIST (RECURSIVEMATCH SUBSCRIBED) "" "*" S: * LIST (\Subscribed) "/" foo2/bar1 S: * LIST (\Subscribed) "/" foo2/bar2 S: * LIST (\Subscribed) "/" baz2/bar2 S: * LIST (\Subscribed) "/" baz2/bar22 S: * LIST (\Subscribed) "/" baz2/bar222 S: * LIST (\Subscribed) "/" eps2 (CHILDINFO ("SUBSCRIBED")) S: * LIST (\Subscribed) "/" eps2/mamba S: * LIST (\Subscribed) "/" qux2/bar2 S: D03 OK List completed (0.001 + 0.000 secs). The following untagged LIST responses for ‘foo2’ and ‘baz2’ are missing. RFC 5258 mandates their inclusion because even though they're not subscribed to themselves, they each have (at least) a subscribed child. S: * LIST () "/" "foo2" ("CHILDINFO" ("SUBSCRIBED")) S: * LIST () "/" "baz2" ("CHILDINFO" ("SUBSCRIBED")) Cheers, -- Guilhem. [0] https://tools.ietf.org/html/rfc5258#section-5

1 0

How to send a test message directly to lmtp, to test proxying
by Marc Roos 12 Nov '19

12 Nov '19

How to send a test message directly to lmtp, to test proxying?

2 2

Howto pin user in proxy/director <-> backend server setup
by Marc Roos 12 Nov '19

12 Nov '19

I have 1x proxy/director server 2x backend mail server The backend servers are using a ldap database and do not have the option to put a proxy=y value. So I put this as a default in the passdb option in the proxy/director config. When I do telnet localhost 110 on the proxy/director, I can authenticate with a test account on svr1.local 1. Will automatically all users be directed to the first server configured in director_mail_servers = svr1.local svr2.local, when the do not have a proxy=y or host=? If this is the case maybe, we should write this somewhere on https://wiki2.dovecot.org/Director https://doc.dovecot.org/configuration_manual/authentication/proxies/ 2. If I change the host= in the ldap server, I think the proxy/director has archived the previous host and still redirects to the old value. Is there a way around this? (stopping/starting dovecot -F resolves this) 3. Do I need the director even in this setup?

1 0

[SOLVED] dovecot -2.2.24 on Fedora 31
by Frank Elsner 12 Nov '19

12 Nov '19

Hello Aki, thanks for your patience and help. I solved my problems by compiling dovecot-2.3.8 and following the migration hints I got it working. Happy, Frank

1 0