Bug 8612

Summary:	No local mail migration from evolution 2 in MGA 1 to evolution 3 in MGA 2
Product:	Mageia	Reporter:	Jim Darby <uberscubajim>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	Normal	CC:	stormi-mageia
Version:	2
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	evolution-3.4.1-1.mga2	CVE:
Status comment:

Description Jim Darby 2013-01-06 16:36:44 CET

Description of problem:


Version-Release number of selected component (if applicable):

Evolution 3.4.1

How reproducible:

Every time


Steps to Reproduce:
1. Use evolution in MGA 1
2. Upgrade to MGA 2
3. Where's my mail?

The problem is caused by evolution moving from mbox style storage of mail to maildir type storage. This is actually a good idea but the way it's ended up in MGA 2 is unsatisfactory.

Rumour on the web has it that evolution 3.0 could migrate but it appears that 3.4.1 can't.

What this really needs is a tool that finds the mbox files in the older evolution and migrates them to the newer maildir format. There are some tools out there but I think we need something a bit more automatic, foolproof and evolution specific.

Any ideas?

Comment 1 Samuel Verschelde 2013-08-28 18:23:17 CEST

Hi, 

Automated mail migration from mga1 to mga2 would have been good, although in my opinion evolution should have handled it, not Mageia. However, now most Mageia 1 users have migrated, so I don't think it would be worth using our small dev and packaging ressources for that, unfortunately.

Best regards.

Status: NEW => RESOLVED
CC: (none) => stormi
Resolution: (none) => WONTFIX

Comment 2 Samuel Verschelde 2013-08-28 18:44:58 CEST

I found another bug report that says that evolution 3.4.4 handles the migration. See bug #7155