[Kde-pim] Marketing blocker collection, DEADLINE: 2013-03-10

[Martin Steigerwald]

Hi Georg,

Am Mittwoch, 8. Mai 2013, 09:22:23 schrieb Georg C. F. Greve:
> On 2013-05-07 20:39, Martin Steigerwald wrote:
> >> Unfortunately I lack the time to go through the list right now.
> > 
> > Did you compile the list somewhere or is it all still in the mail
> > thread?
> 
> It's all in the mail thread.
> 
> Much of it could be ignored because it was meta-discussion, but I think
> there were 10-15 issues in there.
> 
> In any case I would always generously apply the "if it's not in
> Bugzilla, it does not exist" clause.
> 
> > If its all still in the mail thread, I think I prefer to work on the
> > bugs I
> > reported to get then down to repeatable reproducers. Its important
> > that I
> > spend my time wisely. And well, for me personally, my bugs matter most
> > 
> > :)
> 
> Of course. And this would be the other way to go about it: Those who
> filed issues for the blocker collection could just check whether their
> issue still exists, and then let us know whether it is resolved or
> continues to exist.

I think I will do it this way. Thanks.

> > I will have a go trying KDEPIM SC 4.10.2 with our Zimbra IMAP server
> > at work.
> > Likely tomorrow. Thing is, I am not convinced that all of the bugs I
> > reported
> > are related to maildir storage or POP3.
> 
> My experience is that KDE PIM + IMAP is a productive setup. Not
> perfect, occasionally issues do get introduced but then KDE PIM is
> actively being worked on, so long as issues disappear fast enough, I'm
> okay. [1]

Okay. I now tested KDEPIM SC 4.10.2 with our Zimbra 8.0.2 and my honest 
feedback:

Thats seems to be way better. At least with disabled full text indexing 
for mails and with online imap. Since KMail was blocked for some time 
during initial indexing I raised innodb buffer pool size from 80 MiB to 200 
MiB here as well.

But heck, I can even access the kernel-ml folder with about 338000 unread 
mails. I never have been able to with KMail-1 within any reasonable amount 
of time. After some synchronization minute on first access, it now displays 
almost instantly, but typing this mail is a bit jerky while KMail is 
processing 13000 from 61000 threads. I stopped it now in order to fluently 
complete this mail.

There have been no error messages from Akonadi yet.

So, yes, this is impressive! Thank you KDEPIM / Akonadi devs! I admit that 
its easy to generalize after having had bad experiences, but I am able to 
see that generalization now. IMAP appears to be in a way better state. At 
least from my first tests.

I will have a good look at KMail 2 and IMAP next week during holding a 
training.

> [1] https://bugs.kde.org/show_bug.cgi?id=312460#c22

I do not care that much about cosmetic issues with my POP3 / maildir setup 
right now as other more pressing issues exist, but with my current 
workarounds it seems to behave stable :)

Thanks,
-- 
Martin Steigerwald - teamix GmbH - http://www.teamix.de
gpg: 19E3 8D42 896F D004 08AC A0CA 1E10 C593 0399 AE90
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/