Version: 1.5.94 (using KDE 3.1.94 (CVS >= 20031206), compiled sources) Compiler: gcc version 3.3.1 OS: Linux (i686) release 2.6.0 Sometimes i notice that the "To:" field is empty when i try to reply to a message. After little investigation i found that this only happens when i try to reply to messages sent by myself (mailinglists for example, or when i send a short reminder to myself). Pleyse try these steps to reproduce: - Send a new message to yourself. you should not have a reply-to address defined in your identity. also your mail should not pass a mailinglist that sets some kind of "Mailinglist:" header or such. Just a plain message to yourself. - fetch new mail - try to reply to this message, press "R". What i see: The "To:" field in the reply-composer window is empty. This is the relevant debug output from kmail when i press "R": --- snip --- tr:~$ kmail: ### INCOMPLETE with protocol = imap kmail: enable progress kmail: ImapJob::slotGetMessageResult - retrieved part kmail: KMMessage::setDrafts drafts kmail: Check whether "Thomas Reitelbach" <tr@erdfunkstelle.de> is one of my addresses kmail: Removing "Thomas Reitelbach" <tr@erdfunkstelle.de> from the address list kmail: ** ** ObjectTreeParser::parseObjectTree( node OK, showOnlyOneMimePart: TRUE ) ** ** --- snap --- The bug does not occur when i choose "reply to sender", it only happens with "R" and "L" (yes, L doesn't make sence when replying to only one person... but i was curious ;-)). It seems kmail tries to be smart, and above behaviour does make perfect sence when replying to "all" or to a mailinglist. But in this special case kmail should not remove my own address from the list. Thomas
This will be fixed in KDE 3.2.1. For now please try the attached patch.
Created attachment 4208 [details] proposed patch
Your patch fixes it here locally. Thank you very much :-) It'd be nice to see the fix in post-3.2 Therefore i leave the bug so that it doesn't get lost.
I've committed the patch for KDE 3.2.1.
Forgot to close the bug report. Sorry, for the noise.
*** Bug 74094 has been marked as a duplicate of this bug. ***