(In reply to graham from comment #216)
> Was a KMail for what seems like forever (~2000?) (I've been a KDE user since
> it first came out in '96), but after dealing with workarounds and hacks for
> two+ years I eventually gave in and abandoned KMail back in mid-2017.
There is now a related bug about unreachable duplicates
that has already been reported as #388869.
(In reply to Tobias Leupold from comment #214)
> I think one should rather wonder if this even can be fixed
> inside this Akonadi monster I personally wouldn't even dare to look at
> the code, or if one should reconsider the whole thing.
kmail/akonadi handle my > 15GB maildir gracefully,
which is quite a performance. Congratulations !
So it is not perfect, but to me it is an amazing piece of software.
Please consider that it is very hard for maintainers
to fix a bug that is not reproducible on their setup.
(In reply to graham from comment #216)
> Was a KMail for what seems like forever (~2000?) (I've been a KDE user since
> it first came out in '96), but after dealing with workarounds and hacks for
> two+ years I eventually gave in and abandoned KMail back in mid-2017.
There was a commit in 2017-05-04 /phabricator. kde.org/ R206:43f2cde61f 98317eb13d98222 a57bc6df323a308
https:/
that was about this bug.
And indeed in openSUSE Leap-15 (kdepim-runtime 17.12.3),
there are much fewer duplicates than before.
There is now a related bug about unreachable duplicates
that has already been reported as #388869.
(In reply to Tobias Leupold from comment #214)
> I think one should rather wonder if this even can be fixed
> inside this Akonadi monster I personally wouldn't even dare to look at
> the code, or if one should reconsider the whole thing.
kmail/akonadi handle my > 15GB maildir gracefully,
which is quite a performance. Congratulations !
So it is not perfect, but to me it is an amazing piece of software.
Please consider that it is very hard for maintainers
to fix a bug that is not reproducible on their setup.