Bug 93944

Summary: Mails copied in evolution to mbox do not get updated with Kmail headers
Product: [Applications] kmail Reporter: jeff pitman <symbiont>
Component: mboxAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: bjoern
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description jeff pitman 2004-11-26 05:59:46 UTC
Version:            (using KDE KDE 3.3.1)
Installed from:    Unlisted Binary Package

I have the unfortunate disadvantage of being encumbered with using an Exchange server, so I use Evolution to download my emails.  When I first began experimenting with the Evolution solution, I copied the emails directly into my inbox (mbox format).  (My current solution is much better, I deliver the messages from Exchange to my local mail spool via a filter and pipe to sendmail.)

But, while I was hacking it, I noticed that Kmail doesn't reconstruct the mail headers for existing messages, for example:

Status: R
X-Status: NC
X-KMail-EncryptionState:  
X-KMail-SignatureState:  
X-KMail-MDN-Sent:  

So, when one has to delete the indices (which I have to do all the time now--still trying to find this bug...) the messages show up as being unread again because the state information was not committed to the mbox file.  It will only commit to the index.

I did not import my messages, like Bug #60459.

I copied direct in with evolution processing the mbox file directly. (I stopped doing this, by the way)

Anyway, so, maybe in connection with Bug #93943, there could be some better validation routines to clean things up.

I realize maildir folders are more robust, but it would be nice to have a more failsafe mbox support. (Or, maybe mbox should be totally dropped in a future release if it's a totally hopeless venture.)
Comment 1 Laurent Montel 2015-04-12 09:52:41 UTC
Thank you for taking the time to file a bug report.

KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2.

We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.