On Monday, June 11, 2012 08:40:09 PM Peter Maffter wrote:
Even if akonadi runs for some hours, KMail (KDE 4.8.3) does not show any body of the messages. The header lines are displayed. I suspect that upgrade to 4.8.3 did damage something.
@crash: if I move one folder and then another it crashes. If I restart, the 2nd moved folder is in its old location.
How can I start from scratch with KMail? Which directories have to be deleted, so that KMail starts right from the beginning? Do I have to delete certain akonadi databases?
Thanks in advance
----- Ursprüngliche Message ----- Von: Ricardo Chung <ricardo.a.chung@gmail.com> An: opensuse@opensuse.org CC: Gesendet: 21:38 Montag, 4.Juni 2012 Betreff: Re: [opensuse] SuSE 12.1: KMail 4.7.2 unusable
On Sunday, June 03, 2012 06:56:45 PM Sven Burmeister wrote:
Am Sonntag, 3. Juni 2012, 13:27:38 schrieb Peter Maffter:
-mailfolders are there but mails are not displayed at all
It takes some time until akonadi has created the cache. So waiting or maybe even restarting akonadi might help.
Regarding the crash, does it only crash if you move multiple folders or also when moving one folder at a time?
Sven
Like Sven mentioned Akonadi needs some time to recreate and read All mails (specially if you have many mails to download). The first thing it does is synchronize your folders with no mails inside. Once it makes some comparison what is local and what in your mail server the first folder to replenish should be Inbox ( it's my regular practice to not mess all mails around). Finished completely this phase, I usually go to refresh All Mails. This will sync the other mails on subfolders. And no more problems on my side.
Hope this make your transition easier.
Regards,
Peter, Just to keep mails archive logical to read and organize try to not post your comments on top of the content. It's better posting below the last mail you are answering. I found the directions below very helpful when migrating from one KMail version to another. This is quoted from The KMail Handbook 8.2 Clean start after a failed migration In case migration from KMail 1 to KMail 2 fails or you have weird problems after it, you can try to do a clean import of your data, instead of migrating the existing settings. Be warned, that needs more manual setup, so do only if you are confident with setting up again your KMail accounts, and it can generate a large amount of network traffic for IMAP resources. 1. Stop Akonadi and related applications quit KMail/Kontact/KOrganizer, and issue this command: akonadictl stop Make sure no Akonadi or MySQL process is running: ps ux | grep mysql ps ux | grep akonadi They should not show anything else but the grep process itself. 2. Remove old Akonadi database and config Delete the following folders • ~/.local/share/akonadi • ~/.config/akonadi Delete also the files starting with akonadi from ~/.kde4/share/config 3. Restart Akonadi server akonadictl start 4. Add back the accounts Now it is time to add back your account. You can use KMail (Kontact) for it, or you can use the akonadiconsole tool. In KMail: Settings → Configure KMail → Accounts and use Add. If you use IMAP, add a new IMAP E-Mail server. If you want disconnected mode (so you can read the mails offline), enable it on the Advanced tab. Be sure to check that you are subscribed to all your important folders. You might already see a Local folder resource. This points to a local maildir folder. You can either modify this to point to your existing maildir folders or you can add a new resource for local mails. When adding a maildir resource you can choose between KMail Mail Folder or Maildir. Unless you have a mixed folder containing both maildir folders and mbox files, you should choose Maildir. For independent mbox files, like the one in the /var/spool/mail, you can set up a new MBox folder. Add the POP3 accounts as well. In case you have multiple Local Folders set up, choose on the Advanced tab the destination folder where the newly downloaded mails are put. For all accounts, configure the mail check interval. For Local folders disable interval check- ing and also disable Include in manual mail check in the Retrieval options. Add the sending (SMTP) accounts. 5. Fix your filters, identities and favorite folders If you have client side filtering (common with POP3 mails), go to Settings → Configure Fil- ters and fix the destination folder for the filters, they most probably are wrong. Otherwise mails will end up in folders you don’t expect. Spam filter (at least in version 4.7.3 and earlier) does not work as expected in that the rule that the wizard creates does not send spam to the folder you have defined. The workaround for this is to change the ‘spam’ and ‘spam unsure’ (if the spam filter you use support that) from looking at Status-fields in the header X-Spam- Status to look Anywhere in headers for X-your spam filter -Classification: ‘SPAM or unsure’. Look at the filters the wizard creates and copy the ‘contains’ part. Example for Spambayes: ‘X- Spambayes-Classification: spam’ and ‘X-Spambayes-Classification: unsure’. You also need to verify the identity settings and set the sent-mail, drafts and templates fold- ers to point to the right folders. To do that go to Settings → Configure KMail → Identities, modify the identity, go to the Advanced tab and modify the above mentioned folder set- tings. Check also that your Favorite Folders are the ones you have chosen before. 6. Initiate a mail check Start a mail check for your accounts. It is suggested doing it per account. First do for IMAP, if you have. Next is to check (import) your local mails. One solution is to do a full check in one go File → Check Mail In and select the local account, the other is to click one by one on the folders, that should initiate the check for that folder (alternatively right click on the folder name and select Update Folder). The initial import might be slow and could use a lot of memory, especially in case you have folders with a large amount of mail. In that case per-folder check is preferred. In case the check (complete or for one folder) is finished and the memory usage is still high, you could restart the Akonadi server — as seen above — or just the maildir agent, if you use akonadiconsole. Do not worry, this high memory usage is only for initial import. Initiate a check mail for POP3 resources" Hopefully after these steps, you will have a much nicer KMail experience. Regards, -- Ricardo Chung | Panama Linux & FOSS Ambassador openSUSE Projects -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org