More of my users are accessing mail remotely, which probably explained
why I started seeing
Mar 18 05:50:34 dovecot: master: Warning: service(imap-login):
process_limit (2) reached, client connections are being dropped
I played around with increasing limits, but made the
On 3/24/22 1:49 PM, Paul Kudla (SCOM.CA Internet) wrote:
and it just simply DOES NOT WORK
> ...
p...@scom.ca incremental Waiting for dsync to finish
Have you tried debugging dsync to see what it's doing?
https://doc.dovecot.org/configuration_manual/replication/
"If you
would someone please send me the standard that you are working towards
(rfc stuff)
in the mean time a bad email or folder or both are simply causing
replication not to work
no there is no logging of any kind of an error
i would appreciate the info as i will start ripping down the c code to
> On 24/03/2022 09:32 Aki Tuomi wrote:
>
>
> > On 24/03/2022 09:29 Aurel Mihai wrote:
> >
> >
> > Hello,
> > after upgrade to version 2.3.18, we enconter a lot of errors, such as:
> >
> > Mar 22 14:08:32 mail2 dovecot: pop3(user@domain)<52269><3y3GeM3aQ+tWadtM>:
> > Panic: file
> On 24/03/2022 09:29 Aurel Mihai wrote:
>
>
> Hello,
> after upgrade to version 2.3.18, we enconter a lot of errors, such as:
>
> Mar 22 14:08:32 mail2 dovecot: pop3(user@domain)<52269><3y3GeM3aQ+tWadtM>:
> Panic: file lib-event.c: line 585 (event_reason_code_prefix): assertion
> failed:
Hello,
after upgrade to version 2.3.18, we enconter a lot of errors, such as:
Mar 22 14:08:32 mail2 dovecot: pop3(user@domain)<52269><3y3GeM3aQ+tWadtM>:
Panic: file lib-event.c: line 585 (event_reason_code_prefix): assertion
failed: (name[0] != '\0')
Mar 22 14:08:32 mail2 dovecot:
