After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 523399 - Maildir speedup when moving items to another Maildir
Maildir speedup when moving items to another Maildir
Status: RESOLVED FIXED
Product: evolution-data-server
Classification: Platform
Component: Mailer
unspecified
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[maildir]
Depends on:
Blocks:
 
 
Reported: 2008-03-19 16:50 UTC by Philip Van Hoof
Modified: 2011-08-18 13:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Philip Van Hoof 2008-03-19 16:50:32 UTC
These patches will speedup moving items to another Maildir:

http://tinymail.org/trac/tinymail/changeset/3511
http://tinymail.org/trac/tinymail/changeset/3510

Perhaps they can't easily be applied to upstream Camel's Maildir implementation. Because this code has been disabled in the Evolution UI, it has aged. Therefore quite a lot of its code had to be fixed and adapted in Tinymail's Camel-lite.

Perhaps it's time to merge all this work back to upstream Camel?

Anyway, stop using mbox for the local folders of Evolution, and start using Maildir. I don't really get it why Evolution is using mbox for those ...

I can list ~ 10 seriously good reasons why you want to switch to Maildir. Including things like potential data corruption and enormous performance problems when for example deleting items from a mbox store. Issues that don't exist with Maildir (and why the cache directory formats of IMAP and POP look a little bit like Maildir, and not like mbox).
Comment 1 Matthew Barnes 2008-03-19 18:44:29 UTC
Migration is the real issue here, as I understand it.  Any suggestions there?
Comment 2 Philip Van Hoof 2008-03-20 08:53:41 UTC
A one time migration code with a nice little dialog-box with a progressbar and a fallback solution (keep the original mbox file and keep supporting mbox for the local folders in Evolution too, and a "Don't ask me again, I want to keep using mbox in stead" answer).

A reason why the migration could file would be disk full. During the migration you will need twice as much disk space.

If migration succeeded, you can bz2 his/her mbox file and put it for example in $HOME or somewhere that he/she can see it. Make a very clear note in the UI that this has happened and that once the user has verified everything, he/she can remove that backup.
Comment 3 Milan Crha 2008-06-02 13:38:24 UTC
Philip, that's the question for the other bug, what about those two offered patches you showed us? It seems fine from my point of view. Matt, what do you think?
Comment 4 André Klapper 2008-11-15 22:10:40 UTC
any news here, guys?
Comment 5 Milan Crha 2009-10-14 09:48:18 UTC
Created commit bd02d40 in eds master (2.29.1+)

Slightly modified version, adapted to upstream camel.
Comment 6 Milan Crha 2011-08-18 13:20:09 UTC
OK, the patch has a little regression, see bug #651469