Bug 232798 - not able to import mixed dir structure of KMail 1
Summary: not able to import mixed dir structure of KMail 1
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Migration (show other bugs)
Version: 4.5
Platform: Compiled Sources Linux
: HI normal
Target Milestone: ---
Assignee: Kevin Krammer
URL:
Keywords: akonadi-ports-regression
Depends on:
Blocks: 223438
  Show dependency treegraph
 
Reported: 2010-03-31 08:17 UTC by Mikolaj Machowski
Modified: 2010-05-21 20:12 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 Mikolaj Machowski 2010-03-31 08:17:08 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

Recently KMail started to try import old Mail dir structure into Akonadi. This report applies to 2010-03-30 version of trunk.

I have old Mail dir dating back to 2000, it has mixed structure of mboxes and maildirs. When trying to convert this directory into Akonadi KMail just says "not maildir structure" and hangs.

First I hope in final version KMail will be able to import not only maildirs but also mixed structures.

For the time being I think it would be good to add info about inability of mbox conversion to warning dialog (now it speaks only about IMAP) or more graceful abandoning of procedure. TIA.
Comment 1 Thomas McGuire 2010-05-21 12:53:53 UTC
Assigning to Kevin.

Kevin, if this works now after your changes, please close this bug.
Comment 2 Kevin Krammer 2010-05-21 13:14:45 UTC
Mails in both maildir and mbox work already, I am now working on meta data such as tags.
Changing to assigned
Comment 3 Kevin Krammer 2010-05-21 20:12:46 UTC
KMail's mail directory is now handled by a "Mixed" maildir resource, which understands maildir and mbox folders within each other.

It also has read-only access to the index files generated by KMail, so it can read flags and tags stored there.

Flags are then stored in Akonadi as metadata to the message item object, tags are imported to Nepomuk and message objects are associated with these tags accordingly.

When being used with the migration tool that the new KMail starts on first invokation, tag information such as color are added to the respective tag in Nepomuk.