Re: Jumping ship
Paul Campbell <[email protected]> Thu, 01 Dec 2011 08:31:49 +1300
| Newsgroups | gmane.org.user-groups.linux.new-zealand.general |
|---|---|
| Message-ID | <5654990.I0QeWiCFkX@rata> |
On Wed, 30 Nov 2011 20:44:12 cr wrote: > For the past few years I've been using Kmail under Gnome. I just installed > the 'latest' versions with Debian Squeeze. On starting kmail from the > command line (ssh'd in a terminal window from my laptop, that's why) I > noticed a lot of messages about akonadi. Googling showed it's some sort > of system- wide database that Kmail2 uses. A frantic and furious search > showed that my Maildir files are all still there. So if Kmail 1.13 still > uses Maildir why's it loading Akonadi? I went through this a couple of months ago by choosing to switch to Kubuntu OO. In general OO is a decidedly better KDE release than previous ones but this area - kmail transitions - it's pretty much a disaster .... as you've found out. KDE have moved all the mail handling into Akonadi - there's a migration app that's supposed to handle moving your mail files into the internal data base - it fails under a number of situations. In my case I was a (very!) early KDE adopter - KDE 1.0 - I had a mixture of maildir and mbox files. To fix your saved maildir files you can simply download akonadi console, run it (note the warning) and choose Local Files->Configure->Configure Natively and set the name of the directory where you keep your mail files Or there's a akonadiconsole option "Kmail maildir" in akonadiconsoile use Add- >Kmail Maildir - I haven't tried this - I think it allows you to add multiple directories Mbox files can be imported with akonadi console by choosing Add->Mbox and naming the mbox file ---- What caught me were my sent-mail and outbox - they're 'special' - in my case they were mbox format files (from KDE 1) problem- the KDE migration app just threw up its hands and I couldn't send mails for ages before I tried this - if I'd known I'd have copied these files somewhere else and deleted them before I can't describe the fix for this problem, there was a lot of floundering around, gnashing of teeth and tearing of hair - I didn't keep records - it involves moving the files somewhere else and hacking on the akonadi DB through akonadi console - then reimporting the data using a temporary akonadi mbox Paul _______________________________________________ NZLUG mailing list [email protected] http://www.linux.net.nz/cgi-bin/mailman/listinfo/nzlug