Also, nowadays Lua would be a better way to do custom authentication and we're
more careful not to break that.
> On 21. Jun 2022, at 13.47, Timo Sirainen wrote:
>
> Oh, I think your problem is that you've implemented a separate dict-server.
> And looks like we forgot to mention in v2.3.17 rele
Oh, I think your problem is that you've implemented a separate dict-server. And
looks like we forgot to mention in v2.3.17 release notes that the dict protocol
had to be changed due to some improvements. Your dict server should verify that
the VERSION line's major version number is as expected,
Hi Timo,
attached is the log with auth_debug=true from the starting process and
running "doveadm auth test ralfimapt...@egroupware.org" and one other
regular passdb lookup.
I replaced passwords and the customer email with XX.
I also run "doveadm user '*'" to test the iteration, which wor
Hi Timo,
Am 20.06.22 um 12:17 schrieb Timo Sirainen:
On 20. Jun 2022, at 10.03, Ralf Becker wrote:
Fixes: Panic: file userdb-blocking.c: line 125 (userdb_blocking_iter_next):
assertion failed: (ctx->conn != NULL)
As the above Panic is fixed I tried again (see my attached mail to the 2.3.1
On 20. Jun 2022, at 10.03, Ralf Becker wrote:
>> Fixes: Panic: file userdb-blocking.c: line 125
>> (userdb_blocking_iter_next): assertion failed: (ctx->conn != NULL)
>
> As the above Panic is fixed I tried again (see my attached mail to the 2.3.19
> release) and I can confirm to no longer get
Hi Aki,
Am 14.06.22 um 12:24 schrieb Aki Tuomi:
Hi everyone!
Due to a severe bug in doveadm deduplicate, we are releasing patch release
2.3.19.1. Please find it at locations below:
https://dovecot.org/releases/2.3/dovecot-2.3.19.1.tar.gz
https://dovecot.org/releases/2.3/dovecot-2.3.19.1.tar.g
