Recently upgraded to Kmail2, and actually despite a lot of the problems I've been reading about, that went off without a hitch...The problem occurred about a week later because of a power outtage.

When the power came back on everything started up fine but when Kmail loaded, it said the the index for the Inbox was corrupt. It would sit there churning trying to resync the inbox, get to 99% and then abort. So, thinking that it should just be matter of getting the old index out of the way, I closed kmail and renamed the inbox index files in my maildir. When I started it back up, the emails still displayed in the inbox, but i was getting the same resync/aborted messages.

So I got to thinking that maybe it would be easier to copy my maildir somewhere else and start with a blank one and import the old emails using the migration wizard. At this point every thing appeared to be going smoothly until it got into the migration and I would get a message that states "Unable to store downloaded messages. Unknown error. (Append failed)"

So I thought maybe i screwed up the directory permissions or something and I tried to create a new maildir and kept receiving the same error. At this point I decided to try and wipe my Kmail config files and reinstall it, but since some of the option are stored by Akonadi, I kept getting the same error. So I then uninstalled both Kmail and Akonadi, wiped out as many of the config files as I could find and recompiled.

Lo and behold...same error....

So in the long run....I'm just trying to figure out what it will take to wipe out my current configuration to such a state that I can reinstall cleanly with new configs and set things up from scratch and import my old emails.

Any help is appreciated.

Update:

Actually now when I force it to check my email account, the first time, I get the "Append failed" error, but after that it will connect and attempt to download the messages. But when it gets to 99% it sits there saying "Saving downloaded messages". I can't say it never finishes, but it has been stuck at 99% for almost an hour now. Luckily I remembered to set it not to delete the mail from the server so nothing gets lost into the void...

did you ever get a fix for this? I'm getting this exact sequence on a new install of kmail 4.10.1

What files did you delete to get back to a "clean" state?

mamamia wrote:did you ever get a fix for this? I'm getting this exact sequence on a new install of kmail 4.10.1

try by closing down akonadi (command line akonadictl stop) and then rename HOME/.kde/share/apps/nepomuk folder. Then command akonadictl start and reinding should restart, eating your cpu but eventually hopefully fix your problem

This suggestion will not fix the problem: it will just wipe the Nepomuk database (and so, everything associated with it like addresses and tags). That is why I asked what files were deleted: these problems often arise when not everything was wiped clean (which is in most of the cases not a recommended way to solve problems, although currently there's a lack of high-level tools for this).

You may also try "akonadictl fsck".

einar wrote:This suggestion will not fix the problem: it will just wipe the Nepomuk database (and so, everything associated with it like addresses and tags). That is why I asked what files were deleted: these problems often arise when not everything was wiped clean (which is in most of the cases not a recommended way to solve problems, although currently there's a lack of high-level tools for this).

You may also try "akonadictl fsck".

I know it is a "generic" solution but it actually does work a lot of times. I have done it myself more times than I care to remember. Hopefully in 4.10.x akonadi/nepomuk is more stable