Quoting Rick Romero <r...@havokmon.com>:
Quoting Jan Schneider <j...@horde.org>:
Zitat von Brent <impu...@bitrealm.com>:
Quoting Michael M Slusarz <slus...@horde.org>:
Quoting D G Teed <donald.t...@gmail.com>:
I've just joined the list. Looking for way to control sender
replies in IMP.
Like Nick from a couple of days ago, our users (and helpdesk) are asking
for a way to make the default reply to sender only or always chosen.
While Michael Slusarz's reply is probably correct for many end users,
it isn't desired from a management point of view. You assume the
user is intelligent and observant. We are talking about people who
respond to phishing emails. Don't assume too much of the user!
So how is locking someone into the opposite behavior also NOT
assuming too much of the user? It's exactly the same, just with
a different default behavior.
Thus, the question becomes what is the proper default behavior.
I've given the reasoning why we choose Reply to All. I have yet
to see a single valid argument as to why Reply to Sender should
be the default.
The primary reasoning lies in the fact the button is labeled "Reply", which
in all other email programs means "reply to sender". If you're
going to default
the "Reply" button to "Reply to All", then it should be labeled as such.
It's not defaulting to Reply to All. Which reply type it is, is
decided dynamically, depending on who the original message's
recipient(s) were.
Attempting 3rd person observation...
As far as the basic user is concerned, it's always Reply to All. If
there is only one recipient, the 'All' is just the original Sender.
That's not fancy.
As far as I can tell this observation is correct: For the standard
user the functionality is not intelligent at all. Here the "automatic"
behavior always does a "Reply to All" which is labelled as "Reply".
That this is considered problematic seems reasonable to me.
Cheers,
Gunnar
BUT - If you add in that if one of the recipients is not your
identities, then it's definitely dynamic. Now, that's fancy for an
advanced user, most user's aren't going to run into that situation -
therefore the functionality appears incorrect to them.
Rick
--
IMP mailing list
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: imp-unsubscr...@lists.horde.org
--
Core Developer
The Horde Project
e: wro...@horde.org
t: +49 700 6245 0000
w: http://www.horde.org
pgp: 9703 43BE
tweets: http://twitter.com/pardus_de
blog: http://log.pardus.de
--
IMP mailing list
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: imp-unsubscr...@lists.horde.org
