Version: (using KDE KDE 3.5.0) Installed from: Debian testing/unstable Packages Some mailing-lists set a reply-to itself, so that if you press reply, you send the mail to the list, not to the sender. It is kind of anoying if this happens. Eventhough I am long time used to handle mailinglist, this happens from time to time. Before I switched to Linux, I had an old DOS-Client running which was so kind to ask "Send to Sender" or "To List". I am aware that you can choose whom to answer to manually from the context-menu. In my opinion it would great if kmail also had the additional option of asking whom to send.
Use Reply to List (L), Reply to Author (Shift+A) or Reply to All (A) if you don't like the standard Reply (R) method.
I am aware of this shortcuts, but I think this is a question of usability. Dor the one thing, I mostly work with the mouse. Second, in the standard-setting of kmail, the reply-to header is not displayed, so it is not always clear which policy the list has. (Is there any way of changing this setting, so that I can see the Reply-to header?) The other thing: I think would better for workflow to have the possibility to klick just once/press just one key and just in case there is a mailinglist kmail asks me, to whom I want to send that mail. Pressing reply ist just the normal way in the most mail clients. So from my standpoint that is easier. Of course this should be optional (to be turned off) and the existing ways of dealing with this should remain. Since there is a lot of talk about usability in KDE, this may be something which could be discussed with usability people.
Agreed. Please discuss with the usability people and, when you come to a conclusion, reopen this bug report with the result. BTW, you can click & hold on the Reply button on the KMail toolbar to choose other options, or you can add more icons to your toolbar by configuring it.
ok, is there anyone special to contact for kmail?
Please re-close this report as duplicate of: https://bugs.kde.org/show_bug.cgi?id=83339
*** This bug has been marked as a duplicate of bug 83339 ***