Bug 232121

Summary:	Message marked as unread using dIMAP
Product:	[Unmaintained] kmail	Reporter:	Frank Niethardt <frank>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	alessandro.crismani, jsardid
Priority:	NOR
Version:	1.13.1
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Frank Niethardt 2010-03-25 16:26:00 UTC

Version:           1.13.1 (using KDE 4.4.1)
OS:                Linux
Installed from:    Unlisted Binary Package

I'm using KMail within Kontact on Archlinux with KDEmod packages. I have one google apps account configured as dIMAP. When I get a new message in INBOX, read it and move it to another folder, it is in that new folder after the next sync. After syncing twice it it marked unread again.

In gmail / google apps mail moving a message to another folder means, that the message get a new label and the label inbox is removed. So I would understand it, if the eMail was in both folders, so it just don't get the "I have been read", but just get the new label without beeing marked read.

Comment 1 Alessandro Crismani 2010-07-26 23:50:49 UTC

Confirmed here. Read messages from Gmail IMAP (withdIMAP on Kmail) are marked as unread on next sync. If I read them again they stay read (fortunately).

All seems to work fine with my university server (dIMAP on Kmail as well). Read messages here does not raise to unread status with no reasons.

Cheers,
Alessandro

Comment 2 avlas 2011-04-13 03:23:06 UTC

same here, this is duplicate from this other bug: https://bugs.kde.org/show_bug.cgi?id=169177

Comment 3 avlas 2011-04-13 03:39:41 UTC

I just want to say that bug https://bugs.kde.org/show_bug.cgi?id=169177 is NOT resolved. The thing is that this ONLY happens for GMAIL accounts, and I guess Ruchir Brahmbhatt tried with other accounts.

Comment 4 Laurent Montel 2015-04-12 09:49:05 UTC

Thank you for taking the time to file a bug report.

KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2.

We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.