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. I hope I provided all information needed and seeing forward to get a hint what the problem might be. Marius -------------- next part -------------- A non-text attachment was scrubbed... Name: dovecot-journalctl.rtf Type: text/rtf Size: 7293 bytes Desc: not available URL: <https://dovecot.org/pipermail/dovecot/attachments/20200610/10edbe7d/attachment.bin> -------------- next part -------------- A non-text attachment was scrubbed... Name: dovecot-n.rtf Type: text/rtf Size: 2599 bytes Desc: not available URL: <https://dovecot.org/pipermail/dovecot/attachments/20200610/10edbe7d/attachment-0001.bin>
On 10 Jun 2020, at 01:42, Marius Rasch <dovecot at email.marius-rasch.de> wrote:> 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 this has happened to me its been a permission error on the server in the user?s mail folders.> Whenever a client connects to dovecot I get an panic in the log.Well, that is not good and knowing what the panic is might be helpful. Panic is always bad and whatever this is you need to fix it.> I hope I provided all information needed and seeing forward to get a hint what the problem might be.IF it?s not permissions you need to provide doveconf -n output. Bloglines for any fall, panic, or error level events at a minimum.
On 10 Jun 2020, at 23:18, @lbutlr <kremels at kreme.com> wrote:> IF it?s not permissions you need to provide doveconf -n output. Bloglines for any fall, panic, or error level events at a minimum.Apologies, I did not see the attachments. Will look on a real screen later.
On 10. Jun 2020, at 10.42, Marius Rasch <dovecot at 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 <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. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20200611/f2e7c2eb/attachment.html>
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 <dovecot at email.marius-rasch.de > <mailto:dovecot at 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. >