Op 14-11-2023 om 14:35 schreef Aki Tuomi:
On 14/11/2023 14:59 EET Kees van Vloten wrote:
Hi all,
After upgrading Debian Bullseye (Dovecot 2.3.13) to Bookworm (Dovcecot
2.3.19), submission-login returns an error on Kerberos authentication:
"Client sent invalid command: Command line is
Op 14-11-2023 om 14:35 schreef Aki Tuomi:
On 14/11/2023 14:59 EET Kees van Vloten wrote:
Hi all,
After upgrading Debian Bullseye (Dovecot 2.3.13) to Bookworm (Dovcecot
2.3.19), submission-login returns an error on Kerberos authentication:
"Client sent invalid command: Command line is too
> On 14/11/2023 14:59 EET Kees van Vloten wrote:
>
>
> Hi all,
>
>
> After upgrading Debian Bullseye (Dovecot 2.3.13) to Bookworm (Dovcecot
> 2.3.19), submission-login returns an error on Kerberos authentication:
> "Client sent invalid command: Command line is too long".
>
> When I
Hi all,
After upgrading Debian Bullseye (Dovecot 2.3.13) to Bookworm (Dovcecot
2.3.19), submission-login returns an error on Kerberos authentication:
"Client sent invalid command: Command line is too long".
When I initially set this up on Bullseye I have seen the same issue, but
adding
Hello,
Is it possible to configure SQL connection keepalive for Dovecot?
Probably what I have to do is "Note that the SQL backend must be used via
Proxy", however I was unsucsessful in figuring out how can I setup this to get use
of connection pool at Dovecot.
Thanks.
$ dovecot --version
Good morning,
OK (If I am wrong someone please update this!)
Trying to run multiple auth schemes when sasl is avaliable etc is overkill
Next trying to auth via AD (this is mainly another mess windows made) is
also impractible, sasl was invented as an auth layer in the first place
to then
