Bug 324173 - mails from mbox resource often display correctly only after compaction
Summary: mails from mbox resource often display correctly only after compaction
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.11
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-28 15:10 UTC by Martin Koller
Modified: 2017-01-07 21:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Koller 2013-08-28 15:10:47 UTC
I have an mbox resource where an external program adds emails to the mbox file (via a cron job).
In addition I have lots of filters setup, mainly to redirect messages from mailing lists into different folders.
Very often kmail displays some mails in that mbox resource with "(No Subject)", "Unknown" sender, "Unknown" Date but with a sensible Size (e.g. currently I see only one mail there which shows 5,3 KiB)

This status does never change - except I open the accounts configuration, Modify the mbox resource and click "Compact Now" (where I have set "Never compact automatically").
E.g. now it shows "7 messages marked for deletion".

When I click "Compact now" then suddenly I see the correct Subject in the mail and then the filters trigger and the mail is moved correctly into the target folder.


Reproducible: Sometimes
Comment 1 Roman Fietze 2013-11-22 07:38:07 UTC
I can reproduce that using KDE 4.11.3, KMail2 4.11.3 using the openSUSE 12.3 KDE Release Repos.
Comment 2 Denis Kurz 2016-09-24 18:16:31 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 3 Denis Kurz 2017-01-07 21:42:58 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.