--===============1933592245==
Content-Type: multipart/signed; protocol="application/pgp-signature";
	micalg=pgp-sha1; boundary="Boundary-02=_0e9x/XjCL+aZ4oe";
	charset="us-ascii"
Content-Transfer-Encoding: 7bit


--Boundary-02=_0e9x/XjCL+aZ4oe
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

first of all, please keep kmail@kde.org CC'ed.

As you might have noticed the behavior of KMail when using Reply has=20
changed since KDE 3.1. The current KMail tries to address the reply to=20
the original sender of the message if Reply is used even for=20
mailing-lists which set the Reply-to header. Of course this only works=20
if KMail can figure out the mailing-list address and therefore can=20
ignore it in case it's present in the Reply-to header. Anyway, what I'd=20
like to know is whether this change is usability-wise a good change or=20
not.

The current behavior is:
Reply ('r') -> reply to the original sender
Reply to Mailing-list ('l') -> reply to the mailing-list

The old behavior was:
Reply ('r') -> reply to Reply-to address if present, else to From; in=20
case of Reply-to mangling mailing-list (seems to be the majority=20
nowadays) this resulted in a reply to the mailing-list
Reply to Mailing-list ('l') -> reply to the mailing-list

With the old behavior it was impossible to send a private reply without=20
using the mouse to right-click on the sender's address (which means=20
that's actually an accessibility problem). This is the main reason why=20
the new behavior was introduced.

Things which should be improved after KDE 3.2:
a) Rephrase "Reply" to "Reply to Sender"
b) Replace the two Reply buttons in the toolbar with a=20
KToolBarPopupAction which contains all three Reply actions (-> one=20
button less on the toolbar ;-) ) similar to the Forward button. The=20
standard behavior of this button could be Reply to Mailing-list for=20
mailing-list messages and Reply (to Sender) for normal messages.

The question now is whether it's necessary to revert the behavior to the=20
old behavior until the new behavior is improved like above. The only=20
valid reason for this is that probably many users always used Reply in=20
case they wanted to reply to a mailing-list and that this worked for=20
them up to now. A few people complained about this on kmail@kde.org and=20
kde-pim@kde.org and there were also already 1 or 2 bugs reports about=20
this. Of course, only those people complain that don't like the change.=20
Those who like the new much more logical behavior don't speak up.=20
Therefore I'd like to know what the usability team thinks about this.

Regards,
Ingo

--Boundary-02=_0e9x/XjCL+aZ4oe
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQA/x9e0GnR+RTDgudgRAhz7AKDDR00SdIJrdHfCpPwi/+DuefV6VQCgit6+
VySoCf+ik5cuO/n+bpyp8Vo=
=Qn+f
-----END PGP SIGNATURE-----

--Boundary-02=_0e9x/XjCL+aZ4oe--

--===============1933592245==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
kde-usability mailing list
kde-usability@mail.kde.org
https://mail.kde.org/mailman/listinfo/kde-usability

--===============1933592245==--