Thank you alot! I'll wait for v2.3.11 to check if the problem is solved!
Am 11.06.20 um 15:04 schrieb Timo Sirainen:
On 10. Jun 2020, at 10.42, Marius Rasch <dove...@email.marius-rasch.de
<mailto:dove...@email.marius-rasch.de>> wrote:
Hi,
since one or two month I have a problem with Dovecot not updating the
read-flag on mails using IMAP. I receive new mails, but when reading,
they still unread on other devices (but shown as read on the first
device).
When I remember correct, this problem doesn't come with an update of
dovecot, but just occured at some time. But I've updated dovecot since
then a few times.
Whenever a client connects to dovecot I get an panic in the log. I
therefore added a log file and my dovecot configuration (is this fine
or does it need to be in the mail body?). There are system information
in the output of dovecot -n; the filesystem dovecot is running on is ext4.
Thanks! This crash is another v2.3.10 regression in the COPY/MOVE code.
Fix will be in v2.3.11 and here also:
https://github.com/dovecot/core/commit/203b2b709b0477be8753ea4ae7830bedbfebb268
If the read-flag problem happened before v2.3.10 also, it's probably not
related to the crash but something to do with virtual folders not
syncing flags correctly. There aren't any known problems with it right
now though, so I'm not sure about it.
