Version: 1.7 (using KDE KDE 3.3.1) Installed from: Debian testing/unstable Packages When answering a Mail, it would be nice to be able to mark it automatically read (normally if I answer a mail, I read it anyway), e.g. when pressing the reply-button or when the answer is really sent. As everybody has his own preferences, would nice to have it configurable. mfg /dirk
this used to work in kde 3.1, but now i upgraded to kde 3.5.1 and it does no longer work! :( the message *was* marked as read when the sending had complete, but it no longer does that. It just marks it as "replied".
Still true in KDE 4.3 . Great junior job.
*** Bug 100172 has been marked as a duplicate of this bug. ***
Still true in KDE 4.8
Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented. Thank you for your understanding.
Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2.
Still applies to kmail2, component: UI.
How? To reply to a message it first has to be selected, which in turn marks it as read.
@lycantrophe: That's configurable: Configure KMail -> Misc -> Mark selected message as read after. Many people set this to a value >0 sec.
I don't understand the problem. Is it not marked as read ?
@Bernd Makes sense, I suppose. How much interest is this for such a feature? It should not be that hard to implement.
@Laurent: Sorry for being a bit verbose: In most cases it will be marked read, even if "Mark selected message as read after" is set to a value >0 sec. This for the simple reason that writing the reply will take long enough, while the original message marked in the messagelist, so the threshold will be easily reached. However, it won't be necessarily marked read at least in the following case: - if the users hits "reply" but temporarily switches back to the messagelist (in order to open replies for more messages) And generally it won't be marked read at least in the following cases: - if "Mark selected message as read after" is completely switched off - if the Message preview pane is disabled Now, when replying to a mail, it can be assumed that the original mail has sufficiently been literally read, if it is quoted. And in most every case the original mail will be quoted, except the user for some reason removes %QUOTE from the template. But even then, an answer by definition references the original information. So we can safely assume that the user considers an answered mail as read. But to adapt to different preferences and stay on the secure side, we should make this configurable, yet enabled on default. Inline forwarding is a similar case, but this is often done quasi-automatic. Also forwarding information doesn't necessarily imply that the content has been acknowledged. So this one should be configurable as well, yet disabled on default. See also the feature requests regarding ignored threads (Bug #212897) and deleted messages (Bugs #196876, #117717). Taken together, the configuration would make up a nice little sub-section within "Appearance -> Message List" because that is the single common starting point where a marked message gets replied, deleted, forwarded etc. without being opened in a message window.
Ok I understand problem. But with a GUI we will add a lot of options. Not good to add more 5-6 options for it... But it's right I don't know to do it without make it optional. Will think it for 4.11
Created attachment 75507 [details] Patch This patch implements this feature. I also sent it by email to kdepim-bugs@kde.org. Feel free to review & critique it, or accept it if so.
as I wrote in comment 13 I don't like to add more options. Will look at for 4.11 (we are in string freeze/feature freeze)
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.
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.