I'm not using any scheduler.
It's just being activated by the standard replication-notify mechanism
in Dovecot.
Andy
On Thursday, March 28, 2024 12:56:18 AM PDT, Aki Tuomi wrote:
Hi!
We received some more information to this. Are you by chance
running these from some scheduler? It seems
>Am 27.03.24 um 18:49 schrieb Michael Grant via dovecot:
>>I could really use some help debugging issue.
>
>Timo gave some debugging tips in a similar case cf.
>https://dovecot.org/pipermail/dovecot/2023-March/126229.html
>
>In case you know how to use gdb, that should work and might get a
On 19. Mar 2024, at 0.43, Alex via dovecot wrote:
>
> Dovecot supports SAVEDATE IMAP extension [1].
> This is however not implemented correctly for Maildir storage.
>
> Compared to "internal date", "save date" is supposed to be the same
> but well-defined for APPEND and preserved when COPY
Sounds like
https://doc.dovecot.org/configuration_manual/authentication/auth_policy/
Aki
> On 28/03/2024 10:19 EET Stephan von Krawczynski wrote:
>
>
> Hello all,
>
> is it possible to include some post-auth check in the password authentication?
> So after dovecot has found a user allowed
On Thu, Mar 28, 2024 at 09:19:56AM +0100, Stephan von Krawczynski wrote:
> is it possible to include some post-auth check in the password authentication?
> So after dovecot has found a user allowed to login to execute some external
> script for checking additional conditions which gives back
Hello all,
is it possible to include some post-auth check in the password authentication?
So after dovecot has found a user allowed to login to execute some external
script for checking additional conditions which gives back simple true or
false wether the login should be allowed?
--
Regards,
Hi!
We received some more information to this. Are you by chance running these from
some scheduler? It seems that if dovecot is logging, some schedulers can
actually start blocking on log writes to stdout/stderr, which can lead to this
problem.
I wonder if this could be the case for you?
Aki
