Read Status doesn't get synced

[kyoforkshomebrews]

Checklist

• [X] I have used the search function to see if someone else has already submitted the same bug report.
• [X] I will describe the problem with as much detail as possible.

App version

5.806

Where did you get the app from?

F-Droid

Android version

10

Device model

Huawei P Smart 2019 (Codename POT-LX1)

Steps to reproduce

1. Read any mail by tapping it
2. Hit the back button
3. Refresh mails
4. See that the mail you just read appears as unread again

or

1. Read any mail
2. Log in on the web page of your email provider
3. See that the mail you read appears as unread there as well

Expected behavior

Mail appears read on the website and the app

Actual behavior

Mail appears unread on website and app

Logs

No response

[cketti]

1. Are you using an IMAP account?
2. Is Settings → [Account] → Reading mail → Mark as read when opened checked?

If the answer to both questions is yes, please record a debug log while trying to mark a message as read (or opening the message for viewing). See https://github.com/k9mail/k-9/wiki/LoggingErrors

[kyoforkshomebrews]

It's weird, it seems like the issue resolved itself. I'll be sure to get a log if it happens again though.

Edit: and yes to both of your questions btw.

[Tonus1]

I think the status isn't synced immediatly and the delay is sometimes a bit too long. (Have same problem from time to time)

[ByteHamster]

This read status quirk sometimes happens to me as well (maybe like once a month) - usually when I open a message while refresh is still in progress.

Here's the logs: https://drive.google.com/file/d/1VIyudyeqiSWyztivpQAcJ_FjACMHQvzW/view?usp=sharing I'm on a pretty old version (e72df96603af8e1aafd9559c69898766a6fd5f8d)

[cketti]

According to the log the following happened:

1. Message was opened for reading 1.1. Message was marked as read locally 1.2. Command (A) to mark the message as read on the server was enqueued
2. Folder was synchronized in the background 2.1. Local flags were synchronized with the server → message was marked as unread locally
3. Queued command A was executed → message was marked as read on the server

At that point the message was marked as read on the server, but marked unread locally. Refreshing the folder will "fix" the local state.

I guess we'll have to add a mechanism that will ignore changes from the server for a particular flag if we have an outstanding command to change that flag in the command queue.

[ByteHamster]

At that point the message was marked as read on the server, but marked unread locally.

Oh, so it is probably not exactly the same thing that this issue is about (because in the issue it stays unread on the server). Should I open a new issue?

[cketti]

Oh, so it is probably not exactly the same thing that this issue is about (because in the issue it stays unread on the server). Should I open a new issue?

Unless a log is provided that shows the command to mark a message as read on the server fails (or is never issued), I'll assume it's the same problem (with step 3 maybe being delayed a bit more than in your case).

[McTwist]

I have a similar problem, and more info about how to reproduce it.

Conditions:

1. Account needs to be custom, with specific imap address.
2. The mail needs to be located within a folder, probably not part of the 1st or 2nd class set.

This bug applies to any state, even when removing mail. I could do more tests if needed.

This means that Google, Outlook and all other known hosts will work as normal.

[cketti]

@McTwist: Please open a new issue and provide a debug log.

[inertia666]

I have this problem but only with the Mailfence service. I have reported this issue with Mailfence but they say it's a K9 bug. In my case, there is no delay in marking as read as a refresh will show the message as unread again. I cannot get messages to be permanently marked as read until I read them in another client or via the webclient.

I tried another Android email client (VM ware Boxer client) and the "mark as read" works instantaneously.

I also use IMAP with GMX mail service and I have no issue with mails not being marked as read.

I am wondering if there's a difference in IMAP servers that K9 is not handling like other clients?

[cketti]

@inertia666: Sounds like a slightly different problem. Please open a new issue and don't forget to add a debug log. See https://github.com/k9mail/k-9/wiki/LoggingErrors