You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by sebb <se...@gmail.com> on 2019/02/11 15:08:19 UTC
Reply-To settings (was: [vote] fix the misconfiguration of the dev@
mailing list)
On Mon, 11 Feb 2019 at 12:33, Gilles Sadowski <gi...@gmail.com> wrote:
>
> Le lun. 11 févr. 2019 à 11:16, sebb <se...@gmail.com> a écrit :
> >
> > On Mon, 11 Feb 2019 at 09:24, Gilles Sadowski <gi...@gmail.com> wrote:
> > >
> > > Hi.
> > >
> > > Le lun. 11 févr. 2019 à 10:02, sebb <se...@gmail.com> a écrit :
> > > >
> > > > I checked a few other ASF lists and they all have Reply-To set either
> > > > to the current list or to dev@ for lists such as commits@ and
> > > > notifications@
> > >
> > > I had a look at that too.
> > > But IMO
> > > * "dev" and
> > > * "commits", "notifications", ...
> > > are different cases in that the former relays messages that originated
> > > from real people while the latter comes from a "bot" and it would make
> > > no sense to reply to it.
> >
> > Yes. That's deliberate, for the reason you state.
> > The point is that all the lists have Reply-To set.
>
> Sorry, I don't follow the reasoning; why should the setting be
> the same for two different cases?
Huh?
The setting is not the same.
They all have Reply-To set, however as I wrote, the actual setting is
not the same for all the cases.
> > > Gilles
> > >
> > > >
> > > > On Mon, 11 Feb 2019 at 08:47, Mark Thomas <ma...@apache.org> wrote:
> > > > >
> > > > > -1
> > > > >
> > > > > Changing the reply-to configuration increases the chances of message
> > > > > threads being moved off-list by accident. I am concerned about the risk
> > > > > of harm to the community that that represents.
> > > > >
> > > > > I vote to leave the current list configuration as it. I do not see any
> > > > > of the issues described. (I'm using Thunderbird.)
> > > > >
> > > > > On 11/02/2019 08:24, Eitan Adler wrote:
> > > > > > Hi all,
> > > > > >
> > > > > > The mailing list dev@commons.apache.org appears to always and forcibly
> > > > > > set the header Reply-To: Commons Developers List
> > > > > > <de...@commons.apache.org>. I had asked INFRA to remove this remove the
> > > > > > reply-to munging. They asked for documented consensus before making
> > > > > > this change.
> > > > > >
> > > > > > This is broken for multiple reasons.
> > > > > >
> > > > > > It violates RFC 2822 which requires that reply-to MUST only be used
> > > > > > for when " ... the author of the message suggests that replies be
> > > > > > sent."
> > > > > >
> > > > > > While this should be enough, it is useful to explain some of the
> > > > > > reasoning the standard is the way it is:
> > > > > >
> > > > > > - It breaks MUAs that have "reply to all" and "reply" (and maybe even
> > > > > > "reply to list"). In doing so, having this setting greatly increases
> > > > > > the chance of privacy violations by people that expect the mailing
> > > > > > lists to act normally. If you're trying to send a private reply using
> > > > > > the normal method to reply, the message will be made public.
> > > > >
> > > > > I don't see this.
> > > > >
> > > > > Reply - > original poster
> > > > > Reply List -> list
> > > > > Reply All -> List and OP
> > > > >
> > > > > > - It adds nothing: by means of copy and paste a private reply is still
> > > > > > possible, just annoying, and a workaround for a broken mailing list
> > > > >
> > > > > No need for this workaround in Thunderbird.
> > > > >
> > > > > > - Some mail readers provide 'personal mail' indicators. This only
> > > > > > triggered when you are on the CC or TO lines. The 'feature' breaks
> > > > > > this.
> > > > > > - Some people prefer mail CCed to them as well as the mailing list,
> > > > > > especially if reading a mailing list is lower priority than personal
> > > > > > mail.
> > > > >
> > > > > Both the above require that replies are sent to both the list and the
> > > > > OP. While some people might prefer this, others do not. And we have no
> > > > > way of telling which list subscribers fall into which camp.
> > > > >
> > > > > Mail clients usually have other ways to mark threads that are of interest .
> > > > >
> > > > > Mark
> > > > >
> > > > >
> > > > > > As such I'd like to vote that we fix the dev@ mailing list
> > > > > >
> > > > > > +1 = the mailing list misconfiguration will be removed
> > > > > > -1 = the mailing list will continue to remain broken
> > > > > >
> > > > > > --
> > > > > > Eitan Adler
> > > > > >
> > > > > > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > > > > For additional commands, e-mail: dev-help@commons.apache.org
> > > > > >
> > > > >
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > > > For additional commands, e-mail: dev-help@commons.apache.org
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > > For additional commands, e-mail: dev-help@commons.apache.org
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > For additional commands, e-mail: dev-help@commons.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Reply-To settings (was: [vote] fix the misconfiguration of the
dev@ mailing list)
Posted by Gilles Sadowski <gi...@gmail.com>.
Hi.
Le mar. 12 févr. 2019 à 17:49, Eitan Adler <li...@eitanadler.com> a écrit :
>
> (please make sure to add me to the CC as the mailing list is presently broken)
I confirm that with either "Reply" or "Reply all", the Gmail web interface
will *not* add your address to the CC. :-(
> On Mon, 11 Feb 2019 at 07:08, sebb <se...@gmail.com> wrote:
> >
> > On Mon, 11 Feb 2019 at 12:33, Gilles Sadowski <gi...@gmail.com> wrote:
> > >
> > > Le lun. 11 févr. 2019 à 11:16, sebb <se...@gmail.com> a écrit :
> > > >
> > > > On Mon, 11 Feb 2019 at 09:24, Gilles Sadowski <gi...@gmail.com> wrote:
> > > > >
> > > > > Hi.
> > > > >
> > > > > Le lun. 11 févr. 2019 à 10:02, sebb <se...@gmail.com> a écrit :
> > > > > >
> > > > > > I checked a few other ASF lists and they all have Reply-To set either
> > > > > > to the current list or to dev@ for lists such as commits@ and
> > > > > > notifications@
> > > > >
> > > > > I had a look at that too.
> > > > > But IMO
> > > > > * "dev" and
> > > > > * "commits", "notifications", ...
> > > > > are different cases in that the former relays messages that originated
> > > > > from real people while the latter comes from a "bot" and it would make
> > > > > no sense to reply to it.
> > > >
> > > > Yes. That's deliberate, for the reason you state.
> > > > The point is that all the lists have Reply-To set.
> > >
> > > Sorry, I don't follow the reasoning; why should the setting be
> > > the same for two different cases?
> >
> > Huh?
> >
> > The setting is not the same.
> >
> > They all have Reply-To set, however as I wrote, the actual setting is
> > not the same for all the cases.
>
> There are two different things:
> - having reply-to set
> - having reply-to munged
>
> The former happens by the user. The latter is changed by the mailing
> list. The right thing to do for commits@ is to have the *bot itself*
> set "reply-to" to the list and for the list to do nothing.
>
>
> On Mon, 11 Feb 2019 at 13:19, Gilles Sadowski <gi...@gmail.com> wrote:
> >
> > A message intended for the list that
> > is sent privately, or one intended to be private that is sent to a public
> > list?]
>
> Not exactly. In the broken case, public messages also run the risk of
> getting ignored. This is because replies don't go to the user and thus
> look like ordinary messages. As an example: I get an average of 200
> messages per day from public mailing lists. Unless a message is marked
> as "to me" or "I participated" it is much more likely to be missed.
>
> The tradeoffs are:
>
> Non-broken Pros:
> - Doesn't break the expectation of "reply" vs "reply all"
> - Private messages are not likely to go a public mailing list
> - No need to manually add people to CC
> - Messages are less likely to be lost to the author
> - Following internet standards
IMHO, that should be the primary reference...
> - Similar to other open source projects
And this too.
Gilles
> Cons:
> - Its possible to accidentally sent a private reply which will need to
> be redirected to the mailing list.
>
>
> Broken Pros:
> - It takes slightly more work to send a private reply which will need
> to be redirected to the mailing list.
>
>
>
> --
> Eitan Adler
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Reply-To settings (was: [vote] fix the misconfiguration of the
dev@ mailing list)
Posted by Eitan Adler <li...@eitanadler.com>.
(please make sure to add me to the CC as the mailing list is presently broken)
On Mon, 11 Feb 2019 at 07:08, sebb <se...@gmail.com> wrote:
>
> On Mon, 11 Feb 2019 at 12:33, Gilles Sadowski <gi...@gmail.com> wrote:
> >
> > Le lun. 11 févr. 2019 à 11:16, sebb <se...@gmail.com> a écrit :
> > >
> > > On Mon, 11 Feb 2019 at 09:24, Gilles Sadowski <gi...@gmail.com> wrote:
> > > >
> > > > Hi.
> > > >
> > > > Le lun. 11 févr. 2019 à 10:02, sebb <se...@gmail.com> a écrit :
> > > > >
> > > > > I checked a few other ASF lists and they all have Reply-To set either
> > > > > to the current list or to dev@ for lists such as commits@ and
> > > > > notifications@
> > > >
> > > > I had a look at that too.
> > > > But IMO
> > > > * "dev" and
> > > > * "commits", "notifications", ...
> > > > are different cases in that the former relays messages that originated
> > > > from real people while the latter comes from a "bot" and it would make
> > > > no sense to reply to it.
> > >
> > > Yes. That's deliberate, for the reason you state.
> > > The point is that all the lists have Reply-To set.
> >
> > Sorry, I don't follow the reasoning; why should the setting be
> > the same for two different cases?
>
> Huh?
>
> The setting is not the same.
>
> They all have Reply-To set, however as I wrote, the actual setting is
> not the same for all the cases.
There are two different things:
- having reply-to set
- having reply-to munged
The former happens by the user. The latter is changed by the mailing
list. The right thing to do for commits@ is to have the *bot itself*
set "reply-to" to the list and for the list to do nothing.
On Mon, 11 Feb 2019 at 13:19, Gilles Sadowski <gi...@gmail.com> wrote:
>
> A message intended for the list that
> is sent privately, or one intended to be private that is sent to a public
> list?]
Not exactly. In the broken case, public messages also run the risk of
getting ignored. This is because replies don't go to the user and thus
look like ordinary messages. As an example: I get an average of 200
messages per day from public mailing lists. Unless a message is marked
as "to me" or "I participated" it is much more likely to be missed.
The tradeoffs are:
Non-broken Pros:
- Doesn't break the expectation of "reply" vs "reply all"
- Private messages are not likely to go a public mailing list
- No need to manually add people to CC
- Messages are less likely to be lost to the author
- Following internet standards
- Similar to other open source projects
Cons:
- Its possible to accidentally sent a private reply which will need to
be redirected to the mailing list.
Broken Pros:
- It takes slightly more work to send a private reply which will need
to be redirected to the mailing list.
--
Eitan Adler
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Reply-To settings (was: [vote] fix the misconfiguration of the
dev@ mailing list)
Posted by Gilles Sadowski <gi...@gmail.com>.
Hi.
Le lun. 11 févr. 2019 à 16:08, sebb <se...@gmail.com> a écrit :
>
> On Mon, 11 Feb 2019 at 12:33, Gilles Sadowski <gi...@gmail.com> wrote:
> >
> > Le lun. 11 févr. 2019 à 11:16, sebb <se...@gmail.com> a écrit :
> > >
> > > On Mon, 11 Feb 2019 at 09:24, Gilles Sadowski <gi...@gmail.com> wrote:
> > > >
> > > > Hi.
> > > >
> > > > Le lun. 11 févr. 2019 à 10:02, sebb <se...@gmail.com> a écrit :
> > > > >
> > > > > I checked a few other ASF lists and they all have Reply-To set either
> > > > > to the current list or to dev@ for lists such as commits@ and
> > > > > notifications@
> > > >
> > > > I had a look at that too.
> > > > But IMO
> > > > * "dev" and
> > > > * "commits", "notifications", ...
> > > > are different cases in that the former relays messages that originated
> > > > from real people while the latter comes from a "bot" and it would make
> > > > no sense to reply to it.
> > >
> > > Yes. That's deliberate, for the reason you state.
> > > The point is that all the lists have Reply-To set.
> >
> > Sorry, I don't follow the reasoning; why should the setting be
> > the same for two different cases?
>
> Huh?
>
> The setting is not the same.
>
> They all have Reply-To set, however as I wrote, the actual setting is
> not the same for all the cases.
Sorry I didn't express myself clearly: While it makes perfect sense
to redirect to "dev" a reply to a mail that comes from e.g. "commits",
it is questionable to do the same for a mail that was sent by a real
person. [That is, unless the policy is to make it difficult to make a
private reply to someone who posted to the list. IMHO, it boils down
to decide which is more harmful: A message intended for the list that
is sent privately, or one intended to be private that is sent to a public
list?]
Gilles
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org