You could try changing login processes to high-performance configuration,
https://doc.dovecot.org/admin_manual/login_processes/#high-performance-mode
and see if this makes any difference
Aki
> On 03/07/2024 09:40 EEST m--- via dovecot wrote:
>
>
> For further testing and because I could no
Thank you for the swift answer. Thats what I tried without success.
service imap-login {
process_limit = 15000
process_min_avail = 48
service_count = 0
vsz_limit = 2 G
}
But I also now tried to set both userdb and passdb to static, to rule out any
caching internals. Performance stood in
You could also try this:
service imap {
process_min_avail = 10
service_count = 1024
}
Aki
> On 03/07/2024 10:22 EEST m--- via dovecot wrote:
>
>
> Thank you for the swift answer. Thats what I tried without success.
>
> service imap-login {
> process_limit = 15000
> process_min_ava
That one truly fixed it, it yields 4500-5000 cycles per second now and the
latency is superb.
In my understanding from the docs this means that before there was only a
single process, doing a single service to the imap-login and then exiting, thus
limiting the login process where now we have at
Hi John,
again you're hitting the point!
I put a "report-spam.sieve fired!" and "report-ham.sieve fired!" debug message
in the scripts and monitored with "journalctl -u dovecot -f | grep fired".
The APPEND event (move to junk) triggers BOTH scripts while the APPEND (move
from junk to elsewhere)
Hi
I've used Dovecot for a long time but I never stop learning about the
depth of features I've never used I just discovered the
login_access_sockets setting when reading this page:
https://doc.dovecot.org/admin_manual/login_processes/
The compilation using --with-libwrap configure sett
On 03/07/2024 20:53, postfix_dovecot--- via dovecot wrote:
Hi John,
again you're hitting the point!
I put a "report-spam.sieve fired!" and "report-ham.sieve fired!" debug message in the
scripts and monitored with "journalctl -u dovecot -f | grep fired".
The APPEND event (move to junk) trigge
Hi John,
the ham script runs only if the target folder is the inbox. So, if a user moves
an email from spam to any other folder, it will not be marked as ham.
Meanwhile, I have spent so much time on this to know that it makes no sense to
investigate further. I found a few websites describing the
