Feature #7773

Design and implement migration plan for Claws Mail persistent settings and data

Added by intrigeri 2014-08-11 13:13:11 . Updated 2016-05-10 04:31:03 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Persistence
Target version:
Tails_1.8
Start date:
2015-05-29
Due date:
% Done:

100%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
Affected tool:
Email Client
Deliverable for:
268

Description

At some point, when working on the return to Icedove, we’ll have to design and implement a migration plan for Claws Mail persistent settings and data. Some parts should be easy (e.g. email remotely stored over IMAP, just use Icedove’s account creation wizard to bootstrap a new config), some might be harder (e.g. locally stored MH mailboxes).

Subtasks

Feature #9494: Identify the most common Claws Mail persistence configurations Resolved

100
Feature #9495: Documentation migration from Claws Mail to Icedove Resolved

100
Feature #9496: Draft "sorry" documentation for remaining Claws Mail to Icedove migration known issues Rejected

100
Feature #9497: Polish the Claws Mail to Icedove migration documentation Rejected

100
Feature #9498: Enable Icedove persistence when Claws Mails persistence was enabled Resolved

100
Feature #10453: Provide a script to migrate from the default MH mailbox to Icedove Resolved

100
Feature #10457: Consider shipping the nmh package for some time Resolved

100
Feature #10458: Consider adding a warning when starting Icedove with Claws Mail persistence feature Resolved

100
Feature #10459: Consider adding a warning when starting Claws Mail once it's deprecated Rejected

100

History

#1 Updated by intrigeri 2014-08-12 13:39:16

  • Category set to 212

#2 Updated by intrigeri 2015-05-29 12:52:08

  • blocks #8668 added

#3 Updated by intrigeri 2015-05-29 12:53:01

  • Assignee deleted (None)
  • Target version set to 246

#4 Updated by intrigeri 2015-05-29 12:55:28

  • Category set to Persistence

#5 Updated by anonym 2015-10-21 02:30:18

  • Target version changed from 246 to Tails_1.7
  • QA Check set to Dev Needed

> Target version set to Tails_1.9

This feels odd now, given that the current plan is for Tails 1.7 to ship Icedove. I’m setting the target to 1.7. Please undo this if its wrong (and explain to me what the actual plan is). If it’s correct, please update all children to reflect this.

#6 Updated by intrigeri 2015-10-22 15:31:44

> This feels odd now, given that the current plan is for Tails 1.7 to ship Icedove. I’m setting the target to 1.7. Please undo this if its wrong (and explain to me what the actual plan is). If it’s correct, please update all children to reflect this.

Here as well, if not ready in time for the initial inclusion in 1.7, IMO this could wait for the more advertised 1.9: it’s not a blocker for early/power-users.

#7 Updated by Anonymous 2015-10-23 03:27:54

I’ve taken care of

  • Mail accounts -> manual migration is necessary, documentation will be provided.
  • Locally stored emails -> a script and documentation will be provided.
  • Remotely stored emails -> a migration is not necessary
  • Address books -> documentation will be provided

I still need to check if there is a special treatment for accounts using GPG or not.

#8 Updated by Anonymous 2015-10-23 04:20:28

GPG encrypted and signed emails seem to migrate very well. I’ll simply mention it in the documentation.

#9 Updated by Anonymous 2015-10-23 04:26:50

  • Assignee set to sajolida
  • QA Check changed from Dev Needed to Ready for QA

Hi sajolida,

would you care to take a first look please?
If you want to take over from here, please go ahead, otherwise please reassign back to me with comments :)

Thanks!

#10 Updated by Anonymous 2015-10-26 08:34:17

  • Assignee deleted (sajolida)
  • Feature Branch set to 451f:tails/feature/7773-Migration-Icedove

Taking back this ticket as it is simply the parent ticket.

#11 Updated by intrigeri 2015-11-02 04:04:35

  • Target version changed from Tails_1.7 to Tails_1.8

(Some subtasks are flagged for 1.8 so the parent can’t be fully completed for 1.7.)

#12 Updated by anonym 2015-11-02 15:40:38

  • Status changed from Confirmed to Fix committed
  • % Done changed from 63 to 100

Applied in changeset commit:133fbcddfa024d4e182174dd356dd2be0db5a5f2.

#13 Updated by intrigeri 2015-11-04 02:26:01

> Status changed from Confirmed to Fix committed

This can’t be “Fix committed” while some subtasks are still “Confirmed”. Perhaps these subtasks want to be reparented?

#14 Updated by sajolida 2015-11-04 07:57:49

  • Status changed from Fix committed to Confirmed
  • QA Check deleted (Ready for QA)
  • Feature Branch deleted (451f:tails/feature/7773-Migration-Icedove)

For me this task is not over until we clarified Feature #10458 and Feature #10459 which are part of the integration of the migration in Tails. But that can wait until 1.8.

#15 Updated by intrigeri 2015-11-05 02:44:20

  • Status changed from Confirmed to In Progress

#16 Updated by Anonymous 2015-11-10 05:09:45

  • Assignee set to anonym

Reassigning to anonym, as the only tickets not closed yet are also assigned to him.

#17 Updated by sajolida 2015-12-01 07:41:14

  • Assignee deleted (anonym)

All open subtasks are assigned to u now.

#18 Updated by Anonymous 2015-12-18 07:38:02

  • Status changed from In Progress to Resolved

All subtasks are done. Closing this ticket.

#19 Updated by intrigeri 2016-05-10 04:31:03

  • Assignee deleted ()