Bug 293025 - new mails without header, sender, recipient and date
Summary: new mails without header, sender, recipient and date
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.8
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-01 08:38 UTC by Jens Mander
Modified: 2017-01-07 22:02 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jens Mander 2012-02-01 08:38:06 UTC
Version:           4.8
OS:                Linux

a large number of new mails is diplayed without header, sender, recipient and date.
What I can see is the contents.

What happens to the mail?
When it reaches my computer header, sender, recipient and date are stripped by Kmail2.
I'm really desperate. I tried to stick with Kmail and managed the disaster in Okt 2011.
But now?

Reproducible: Sometimes

Steps to Reproduce:
every time

Actual Results:  
none

Expected Results:  
that mails are displayed right

I'm really desperate. I tried to stick with Kmail and managed the disaster in Okt 2011.
But now?
Are there still users of Kmail out there or did they all change to othere-mail Suits?
Nobody can work this way.
It#s a pity because I'm working on Kmail for a very long time. It was reliable and nice to handle.
Comment 1 Ilya Hegai 2012-02-02 11:27:53 UTC
same as https://bugs.kde.org/show_bug.cgi?id=293013

spam filtering seems to be broken
Comment 2 Denis Kurz 2016-09-24 18:23:41 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 22:02:43 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.