Bug 290874

Summary: Empty e-Mail tags assigned to e-mails during initial akonadi resource configuration
Product: [Applications] kmail2 Reporter: Vasco <Druid>
Component: miscAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Screenshot 1 to explain the issue.
second screenshot
third and last screenshot

Description Vasco 2012-01-07 13:16:24 UTC
Created attachment 67540 [details]
Screenshot 1 to explain the issue.

Version:           unspecified
OS:                Linux

Recently I intenionly deleted all akonadi files in my homefolder in order to reconfigure my KDE from scratch.

After I reconfigured my akonadi mail resources (Pop3 server and local mail directory), I realized that a huge amount of "empty" or "human-unreadable" mail tags had been created. 
Please see the atached screenshots to understand what I mean.

Reproducible: Always

Steps to Reproduce:
Delete your akonadi settings, create new resources an point the path to an existing mail folder that already contains emails.

Actual Results:  
Empty e-Mail tags will be created.

Expected Results:  
Don't invent any e-Mail tags or at least stick to one tag (No need to produce the same tag over and over again)

S | Name                                     | Typ   | Version     | Arch | Repository       
--+------------------------------------------+-------+-------------+------+------------------
i | akonadi                                  | Paket | 4.7.4-312.4 | i586 | (Systempakete)   
i | akonadi-runtime                          | Paket | 1.6.2-110.2 | i586 | KDF Core Packages
i | kdebase4-workspace-plasma-engine-akonadi | Paket | 4.7.4-708.3 | i586 | (Systempakete)   
i | kdepim4                                  | Paket | 4.7.4-312.4 | i586 | (Systempakete)   
i | kdepim4-debuginfo                        | Paket | 4.7.4-312.4 | i586 | (Systempakete)   
i | kdepim4-runtime                          | Paket | 4.7.4-111.2 | i586 | KDF Core Packages
i | kdepim4-wizards                          | Paket | 4.7.4-312.4 | i586 | (Systempakete)   
i | kdepimlibs4                              | Paket | 4.7.4-256.2 | i586 | (Systempakete)   
i | libakonadi4                              | Paket | 4.7.4-256.2 | i586 | (Systempakete)   
i | libakonadi4-debuginfo                    | Paket | 4.7.4-256.2 | i586 | (Systempakete)   
i | libakonadiprotocolinternals-devel        | Paket | 1.6.2-110.2 | i586 | KDF Core Packages
i | libakonadiprotocolinternals1             | Paket | 1.6.2-110.2 | i586 | KDF Core Packages
i | libkde4                                  | Paket | 4.7.4-458.9 | i586 | (Systempakete)   
i | libkde4-debuginfo                        | Paket | 4.7.4-458.9 | i586 | (Systempakete)   
i | libkde4-devel                            | Paket | 4.7.4-458.9 | i586 | (Systempakete)   
i | libkdepim4                               | Paket | 4.7.4-312.4 | i586 | (Systempakete)   
i | libkdepimlibs4                           | Paket | 4.7.4-256.2 | i586 | (Systempakete)   
i | libkdepimlibs4-devel                     | Paket | 4.7.4-256.2 | i586 | (Systempakete)   
i | plasma-addons-akonadi                    | Paket | 4.7.4-150.2 | i586 | (Systempakete)
Comment 1 Vasco 2012-01-07 13:17:03 UTC
Created attachment 67541 [details]
second screenshot
Comment 2 Vasco 2012-01-07 13:17:29 UTC
Created attachment 67542 [details]
third and last screenshot
Comment 3 Denis Kurz 2016-09-24 18:17:03 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:42:54 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.