Hello Timo,
We had been running version 2.3.20 previously, not 2.3.19. We will upgrade to
version 2.3.22 when it is out and monitor if these errors stop.
Thank you,
Nikos
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to d
Thank you for your recommendation. We will try to increase the vsz_limit for
these services and see if it helps to mitigate the issue.
But is there a possible bug in dovecot 2.3.21 version linked with the mdbox
format that is causing the `inconsistency in map index` in the first place or
it is
We are using the Shared Mailboxes in Dovecot Cluster architecture so the user`s
mailbox should only be accessed by a single backend. We have been running with
this architecture for about 2 years with dovecot version 2.3.19 and we had not
seen any `Inconsistency in map index` messages in the log
Hello,
We have been running dovecot version 2.3.21 since July on debian
bookworm system. After upgrading we have seen in the logs similar
messages to the following:
2024-08-29T19:33:27.755399+03:00 server1 dovecot:
lmtp(us...@modulus.gr)<481240><7TMeHNei0GYpeTkA1g8ogQ:P1>: Warning:
mdbox
```
On 22/5/23 16:25, Nikolaos Pyrgiotis wrote:
Have you tried adding the line below to your submision config?
submission_client_workarounds = whitespace-before-path
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to
Have you tried adding the line below to your submision config?
submission_client_workarounds = whitespace-before-path___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
Hello,
I want to make a correction on my first post. We are using version
2.3.19.1 for all our dovecot servers. Is there any update regarding this
issue? I would be happy to provide more details if necessary.
Best Regards,
Nikos Pyrgiotis
On 8/9/22 17:47, Nikolaos Pyrgiotis wrote:
Hello
Hello,
We recently migrated our mail server to a dovecot cluster of 5nodes, a
dovecot proxy, 2directors and 2dovecot backends.
All dovecot nodes run version 2.19.1. We use a glusterfs mounted volume
on the backends forthe mail storage.
We noticed that when issuing the IMAP command to check forUN
