Please don't munge ‘Reply-To’

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Vincent Ladeuil wrote:
>>>>>> "Ben" == Ben Finney <bignose+hates-spam at benfinney.id.au> writes:
> 
>     Ben> John Arbash Meinel <john at arbash-meinel.com> writes:
>     >> Just as a side-comment, when sending out announcements like this, we
>     >> should set the "Reply-To" to be just the bzr mailing list.
> 
> <snip/>
> 
>     Ben> Why would that happen accidentally, unless the ‘Reply-To’ field is
>     Ben> incorrectly set in the first place?
> 
> John want the *sender* ('when sending announcements' refers to the
> release managers, not the mailing list software) of the announce
> to set the Reply-To, nobody talked about changing mailing list
> settings.
> 
> <URL:http://woozle.org/~neale/papers/reply-to-still-harmful> says
> (itself citing <URL:http://www.ietf.org/rfc/rfc2822.txt>:
> ,----
> |     When the "Reply-To:" field is present, it indicates the
> |     mailbox(es) to which the author of the message suggests
> |     that replies be sent.
> `----
> 
> Which is exactly John's point, we don't want replies to be sent
> accidentally elsewhere. If people know better and are allowed to
> mail elsewhere, they hopefully know how to deal with it.
> 
>        Vincent

Specifically, the bazaar at lists.canonical.com mailing list does *not*
munge the Reply-to: field. Because of this, it is recommended practice
to always use "Reply-to-all" rather than just "Reply".

However, for announcements, it generally goes to several low-volume
announce lists. And responders should not be replying to those lists.
(In general, they are moderated, and humans will manually filter them
out, but it is a pain for the moderators.)

So the only time I'm suggesting it is when sending to low-volume
announce lists, which are not meant for general use.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkj5+ksACgkQJdeBCYSNAAM9VwCfUFfZp8noNEgfmpp39ewzN5zb
YEsAmwSAlz4VLLYMXDH/MwzUCjSeQX7V
=xv82
-----END PGP SIGNATURE-----