<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">On 10. Jun 2020, at 10.42, Marius Rasch <<a href="mailto:dovecot@email.marius-rasch.de" class="">dovecot@email.marius-rasch.de</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><div class="">Hi,<br class=""><br class="">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).<br class=""><br class="">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.<br class=""><br class="">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.<br class=""></div></div></blockquote></div><div class=""><br class=""></div><div class="">Thanks! This crash is another v2.3.10 regression in the COPY/MOVE code. Fix will be in v2.3.11 and here also: <a href="https://github.com/dovecot/core/commit/203b2b709b0477be8753ea4ae7830bedbfebb268" class="">https://github.com/dovecot/core/commit/203b2b709b0477be8753ea4ae7830bedbfebb268</a></div><br class=""><div class="">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.</div><div class=""><br class=""></div></body></html>