Bug 279153

Summary:	tagging doesnt work on all mails
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Thomas Jensch <riepernet>
Component:	Tag Resource	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	kdenis, luisfe, mail
Priority:	NOR
Version:	4.7
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Thomas Jensch 2011-08-02 10:49:10 UTC

Version:           4.7 (using KDE 4.7.0) 
OS:                Linux

some mails dont get included in the Tag Folder after tagging them. For these mails the tag icons also gets only updated after changing to another folder and then go back.
it happens with mails in Inbox as well as subfolders. other mails in the same folder behave as expected (tag mail > icon update + Tag Folder update). 
On a first glance, these mails dont have anything in common. some have attachments, some not, some are replies, some not etc...

Reproducible: Sometimes

Steps to Reproduce:
tag mails until bumping into a misbehaving one.

Actual Results:  
mail is tagged, but not picked up by the Tag Resource (with respective listing in the Virtual Folder)

Expected Results:  
tagging works on all mails

even after removing and readding the Tag Resource, these mails wont show up in the Tag Folder. However, the mail is marked as 'tagged with ...'

Comment 1 naraesk 2011-11-02 18:35:38 UTC

Same problem here with KDE 4.7.2

Comment 2 Denis Kurz 2016-09-24 20:37:00 UTC

This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 3 luisfe 2016-10-31 18:51:35 UTC

Is this bug still relevant? I think that tag folders where removed from kmail at some point. At least I cannot see how to define them in order to reproduce the bug.

Comment 4 Denis Kurz 2017-01-08 00:07:48 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.