On 10/09/2021 11.33, William Edwards wrote:
>>
>> 2.
>> We have 2 backends so that we can do maintenance on one of them while
>> users can still access their emails through the other backend.
>> However, we found that stopping dovecot on one backend left users unable
>> to access their mails.
>
On 10/09/2021 11.43, Aki Tuomi wrote:
>> https://www.zq1.de/~bernhard/temp/dovecot/ has some sysreports.
>
> It seems you are normalizing SQL usernames by doing SELECT username, but you
> are not doing it for LDAP.
>
> See if the problem goes away with
>
> pass_attrs = uid=username
I added
On 10/09/2021 11.32, Aki Tuomi wrote:
> Can you post your `doveconf -n`? LMTP should not end up in different backend.
# 2.3.15 (0503334ab1): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.15 (e6a84e31)
# OS: Linux 5.3.18-59.19-default x86_64
# Hostname: dovecot-director2.suse-dmz.suse.de
au
Hi,
I am one of the people taking over our new suse.de email setup
(consisting of dovecot+rspamd+postfix)
and wanted to report some issues we experience:
1.
we use dovecot-director to distribute users between 2 backend servers
that share an NFS mount.
We found that it proxies lmtp to a different
