Bug 357064 - Mail not accessible after migration
Summary: Mail not accessible after migration
Status: REPORTED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Maildir Resource (show other bugs)
Version: 4.13
Platform: openSUSE Linux
: NOR grave
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-22 19:43 UTC by Richard Bos
Modified: 2021-03-09 05:46 UTC (History)
0 users

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 Richard Bos 2015-12-22 19:43:48 UTC
Mail not accessible after migration.  The migration was done after updating from openSUSE_13.1
to openSUSE_leap

kmail created a new resource called "Local Folders", but the old previous folders "Kmail folders" were not migrated to the new Local Folders.  Very frustrating.

After many attempts, using various ways, fortunately having backup arounds, I started kmail, from the command line.  Kmail finished the migration, spitting the following line 10 times per second and never stopping:
   Resource id's don't match: "akonadi_maildir_resource_1" "akonadi_maildir_resource_0"

Looking for this results in this bug report:
   https://bugs.kde.org/show_bug.cgi?id=255104
(Thus that report is still not solved)!  The bugreport points to: https://forum.kde.org/viewtopic.php?f=215&t=120777#p308518
Which has the solution.  At the bottom at states:
  https://forum.kde.org/viewtopic.php?f=215&t=120777#p347175
For me it was sufficient to remove the local trash folder:
rm -rf .local/share/local-mail/trash/

Have this fixed please, because it takes a whole day to work out the problem, it is frustrating as it looks like old email is no longer accessible, etc.





Reproducible: Always

Steps to Reproduce:
1.  See above
2.
3.

Actual Results:  
Email is no longer accessible!  very bad.

Expected Results:  
Nice smooth migration, and emails always accessible
Comment 1 Justin Zobel 2021-03-09 05:46:34 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.