Bug 355938 - some messages become unread again and persist in folder
Summary: some messages become unread again and persist in folder
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: commands and actions (show other bugs)
Version: unspecified
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-26 12:38 UTC by Nicolas
Modified: 2022-11-18 05:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas 2015-11-26 12:38:43 UTC
On a mailbox I have some mails which I am unable to mark as read, they are *always* marked as unread again. Even movin the mails to another folder makes them reappear in the original folder (unread again). Also, after moving, the copied emails are impossible to delete.

Reproducible: Always

Steps to Reproduce:
1. mark all mails as read in folder
2. switch to other folder and back to inbox

Actual Results:  
mails are maked as unread again

Expected Results:  
mails stay marked as read

From the log:

When marking as read:
log_koalarmclient: Check: "Do. Nov. 26 13:31:08 2015"  - "Do. Nov. 26 13:32:07 2015"
log_akonadi_mime: Mark all as:  "R"
log_imapresource: "INBOX"
log_kimap: "46,50,52,53,55 +FLAGS (\Seen)"
log_kmail: A Resource started to synchronize, starting a mail check.
log_kmail: Last resource finished syncing, mail check done
log_koalarmclient: Check: "Do. Nov. 26 13:32:08 2015"  - "Do. Nov. 26 13:33:07 2015"
log_kmail: A Resource started to synchronize, starting a mail check.


After switching back to the folder:

log_imapresource: ".INBOX"
log_kmail: Last resource finished syncing, mail check done
log_messagelist: Using model: Akonadi::EntityTreeModel
log_imapresource: Starting retrieval for  "INBOX"
log_kmail: A Resource started to synchronize, starting a mail check.
log_imapresource: Server bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known problem with Courier IMAP.
log_imapresource: Starting message retrieval. Elapsed(ms):  16
log_imapresource: MessageCount:  57 Local message count:  57
log_imapresource: UidNext:  0 Local UidNext:  0
log_imapresource: HighestModSeq:  0 Local HighestModSeq:  0
log_imapresource: Invalid UIDNEXT
log_imapresource: Fetching complete mailbox  "INBOX"
akonadiagentbase_log: 57
57
log_imapresource: Fetching  3  intervals
Received:  57 In total:  57  Wanted:  57
log_imapresource: Retrieval complete. Elapsed(ms):  94
finished
log_imapresource: "INBOX"
log_kimap: "46 -FLAGS (\Seen)"
log_imapresource: "INBOX"
log_kimap: "50 -FLAGS (\Seen)"
log_imapresource: "INBOX"
log_kimap: "52 -FLAGS (\Seen)"
log_imapresource: "INBOX"
log_kimap: "53 -FLAGS (\Seen)"
log_imapresource: "INBOX"
log_kimap: "55 -FLAGS (\Seen)"
log_imapresource: ".INBOX"
log_kmail: Last resource finished syncing, mail check done
Comment 1 Nicolas 2015-11-26 12:40:23 UTC
This happens in kmail 5.0.2
Comment 2 Nicolas 2015-11-30 15:23:31 UTC
Further information:
The mails are marked only as unread again, when I open the folder. I.e. this does not happen during synchronization with the server, but is applied locally somewhere (when clicking on the folder).
Comment 3 Weng Xuetian 2015-12-03 06:35:49 UTC
I probably have similar issue. I'm using a gmail account with akonadi 15.08.3 and kmail 15.08.3. If a email is unread at the time that it's sync'ed to kmail, it will keep unread unless I read it locally from kmail. Read it from gmail.com doesn't change the unread state in kmail.
Comment 4 Weng Xuetian 2016-03-21 20:12:30 UTC
Ok, now I notice a thing.

The unread status currently (15.12.3) is never sync'ed if there's no new email/newly deleted mail in the folder. If there's a new email comes in , the unread status will be updated.
Comment 5 Justin Zobel 2022-10-19 22:10:53 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 6 Bug Janitor Service 2022-11-03 05:06:49 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2022-11-18 05:17:04 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!