[Akonadi] [Bug 283682] KMail duplicates filtered messages

Frits Spieker bugzilla_noreply at kde.org
Wed Apr 5 08:34:54 BST 2017


Frits Spieker <s.pamme at spiekerbros.com> changed:

           What    |Removed                     |Added
                 CC|                            |s.pamme at spiekerbros.com

--- Comment #181 from Frits Spieker <s.pamme at spiekerbros.com> ---
(In reply to Andreas Mahel from comment #179)
> I'm experiencing email duplication after filter activity as well (openSUSE
> Tumbleweed, most recent versions).
> The filters move mainly mailing list traffic from a POP3 account into local
> sub folders.
> Duplication happens both for automatic filtering as well as executing the
> filters manually.
> In most cases, the duplicated entry shows a different size than the original
> one (but not always).
> On top, selecting any of the two entries will result in Kmail endlessly
> waiting for Akonadi.
> A akonadictl fsck and vacuum does not remove the duplicates; also a "Remove
> duplicate emails" from the "Folder" menu does'nt, and ends with an error
> message.
> In the meantime I have deleted the Akonadi database several times, as well
> as re-created the filters manually, to no avail.
> As a workaround for myself I've written a short SQL script to show / delete
> the offending rows from the database (from within akonadiconsole) - this is
> tedious, but at least allows me to read all mails.
> (How) can I gather more information about what exactly is going on? Both
> Kmail and Akonadi are kind of cryptic in their output - is there a way to
> increase verbosity?

Exactly as you describe. Sometimes I can get things going again for a short
time by doing a restart of akonadi, but lately more often than not this causes
akonadi to crash.

Weird thing though; in some sub-folders the "delete duplicates" functionality
works fine, in other sub-folders (underneath the same account) it will indeed
hang everything solid with an error message at the end, just like you describe.

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

More information about the Kdepim-bugs mailing list