Robert Marianski wrote:
On Wed, Aug 20, 2008 at 10:30:46AM -0700, Rob Miller wrote:
Robert Marianski wrote:
I'm forwarding this to the listen dev list, since it seems more
appropriate here.
Listen always sets the Reply-To header to the mailing list. Currently
there's no way to toggle that.
But we can certainly add a way to toggle this. I'm not sure if we'd want
to expose this through the ui though. There are other settings that I'd
put into this category as well. Maybe an advanced settings section?
i'm not necessarily averse to putting this in the UI... i've been on a lot
of mailing lists over the years, and their reply-to behaviour is something
about which people can get fairly religious at times, it's not a bad knob
to expose. the whole listen UI could use some love anyway.
even before that, though, i'd say we should change the default behaviour.
i think the ideal default would be for 'reply' to go to the list, and
'reply-all' to go to the list, the original senders, and any other To: or
Cc: recipients. i'm not very familiar w/ how mail clients interpret
message headers, though... anyone know if there's a way to tell clients
that this is the desired behaviour?
-r
Ideal default is up for debate, which is why it's become so religious. :)
indeed.
Some would argue that reply should go to just the sender, and reply-all
tacks on everybody.
right. i guess 'ideal' was the wrong word to use. i think it would be a big
improvement to what we have now, while causing the minimum amount of change
relative to the current defaults.
There's an rfc that talks a little bit about this (section 4.4.4):
http://www.ietf.org/rfc/rfc822.txt
I'm not sure why reply-all in some clients doesn't add in everybody. I'm
able to choose with mine. Maybe there's a setting in clients that
controls that.
possibly. i just did a quick test... on my Ubuntu box i used Thunderbird and
Evolution, and i used Mail.app on OSX, in each case reply-all only replied to
the mailing list, it did not include the sender. a quick peek at the config
screens didn't turn up any obvious ways to change this. i don't know if
there's some combination of headers that will get these clients to do what i'm
proposing.
Listen sets the Reply-To header to the mailing list itself. This
explains why replying goes to the list. It doesn't look like the rfc
specifies anything at all about reply to all behavior. It does mention
that Reply-To should supersedes sending to the from though.
right... it seems weird to me that the Reply-To header causes the reply-all
behaviour i'm seeing, but them's the breaks i guess.
I'm not sure we can get the behavior that Rob mentioned above, but if we
removed the Reply-To header, then most clients would have reply go to
just the sender (not including the list) and reply to all would set the
To with the sender and cc the list. Currently reply sends a message to
the list.
this is a very typical default setting... i'm not averse to making this our
default, but if we do we should definitely include the option to change it.
existing lists should retain the same behaviour unless they're explicitly
changed, new lists could use the new default.
-r
--
Archive:
http://www.openplans.org/projects/listen/lists/listen-dev/archive/2008/08/1219259171072
To unsubscribe send an email with subject "unsubscribe" to [EMAIL PROTECTED]
Please contact [EMAIL PROTECTED] for questions.
