[Akonadi] [Bug 319226] produces 1-byte-sized on processing crm114 spam filter rules

[Martin Steigerwald]

https://bugs.kde.org/show_bug.cgi?id=319226

--- Comment #23 from Martin Steigerwald <Martin at Lichtvoll.de> ---
Okay, new findings:

I tested this with a clean kmail 4.10 / akonadi setup and it worked okay for
some days, no 1-byte sized files. Then I copied over my whole main mail account
with several GB of mails and tested with CRM114 and all filter rules enabled
and it just worked okay.

Then I tried moving my whole setup to the test user but this failed due to:

[Bug 325699] New: Akonadi stores absolute path to maildir resource maildir in
database, making it difficult to create a test setup

Today I thought I try the crm114 rules that worked just nice with my test
setup, and only those five crm114 rules where two of them are just for manual
marking mail as spam or good, on my production setup after I upgraded it to
KMail SC 4.11. It worked for the first bunchs of downloads but then I got:

martin at merkaba:~/.kde/share/config> find ~/.local/share/local-mail -size 1c |
wc -l
92

Thats 59 new broken mails that KMail displayed without body at first and on
next startup also with unknown subject. 33 are still broken from the initial
occuring of this issue. I didn´t yet fix them manually by comparing Message-Ids
from a backup from the server Maildir at this time.

Thus for me KMail / Akonadi still looses mails. ;-(((

This time I fixed it by removing approximately 122 UIDs from
akonadi_pop3_resource_0rc and having it redownload those from the POP3 server.

I have two ideas, but actually I do not really like to try even one of them:

1) Maybe since I migrated some severe database related consistency issues have
been fixed and now I still have a database with these issues. Thus I could try
to restart from scratch once again.

2) Maybe this just happens when several POP3 resources are configured. My test
setup just consisted of one.

3) Once bug #325699 is fully fixed I could again try to build up a test setup
with a second user and then if it works okay, just swap test and production
setups. This needs 325699 to be fixed.

-- 
You are receiving this mail because:
You are the assignee for the bug.