Bug 310897

Summary:	Reading mbox files is extremely slow and often fails to show message body
Product:	[Applications] kmail2	Reporter:	Neil <hispeed.bz>
Component:	folders	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	major	CC:	fresh.road1272
Priority:	NOR
Version:	4.9.3
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Neil 2012-11-29 23:31:32 UTC

After moving from kmail to kmail2 I takes forever to read messages from mbox files.  I often end up at the "Retrieving folder contents" message but the message never shows up.  
Originally I thought this was because of big mbox files but it even happens with mbox files with as little as 60 messages.  With large mbox files (10k+ messages) I usually just read the mail from the shell instead of waiting for kmail to show the message.


Reproducible: Always

Steps to Reproduce:
1. Open kmail
2. Click on a folder that corresponds to an mbox file.

Actual Results:  
Message bodies usually don't show up, and if I get lucky and they do it's after a long pause with a "Retrieving folder contents" message where the message body should be.

Expected Results:  
Would expect messages to show up quickly like in the previous version of kmail.

Comment 1 Frits Spieker 2012-12-04 07:38:17 UTC

Most likely the same bug as 288364 which has been around now for more than a year.

Comment 2 Neil 2012-12-04 14:50:28 UTC

Agreed - seems like the same problem.  The fact that it's been around for more than a year probably means i'll have to follow the pack and ditch kmail2.

I still can't believe what a mess kmail2 is.  A MAJOR step backwards from kmail1.   Of all the things to screw up...

Comment 3 Denis Kurz 2016-09-24 18:05:42 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.

Comment 4 Frits Spieker 2016-09-24 18:51:13 UTC

As far as I know the bug is no longer there.

Comment 5 Denis Kurz 2017-01-07 22:18:52 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.