Re: Dovecot authentication through proxy

Hi Sami,

thank you for your answer.

I use GlusterFS because the dovecot replication does not work with the mailcrypt plugin. I will wait and see how reliable it works for me. I have only a very small personal mail server. So it is not really critical if something does not work.

The dovecot-sql.conf has the following content:

driver=mysql connect = "host=192.168.20.24 dbname=vmail user=*** password=***" default_pass_scheme = SHA512-CRYPT

password_query = SELECT username AS user, domain, password, '%w' AS userdb_mail_crypt_private_password, 'yes' AS proxy, 'any-cert' AS 'ssl', 'any-cert' AS starttls, 'Y' as nopassword FROM accounts WHERE username = '%n' AND domain = '%d' and enabled = true; user_query = SELECT concat('*:storage=', quota, 'M') AS quota_rule FROM accounts WHERE username = '%n' AND domain = '%d' AND sendonly = false;

iterate_query = SELECT username, domain FROM accounts where sendonly = false;

Best regards

Daniel

Am 28.01.2020 um 07:54 schrieb Sami Ketola sami.ketola@dovecot.fi:

...

On 27 Jan 2020, at 11.56, Daniel Niewerth mailto:daniel@niewerth.it> wrote:

Hi everybody,

I run two redundant Dovecot servers with a shared Maildir on a GlusterFS volume and a SQL authentication backend based on a mirrored MariaDB database. Because of the splitbrain situation I would like to add two Dovecot Director as proxies.

I would not run on GlusterFS because of bad experiences and index corruptions on the past experiments.

...

Can someone explain me how to solve this problem?

### Proxy Config ### ####################

passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql }

please show contents of this file.

...

passdb { driver = pam }

please remove this if you are using sql as auth db.

Sami

-- This email was Malware checked by vsrv-dus6-fwl01