Hi. Le lun. 11 févr. 2019 à 16:08, sebb <seb...@gmail.com> a écrit : > > On Mon, 11 Feb 2019 at 12:33, Gilles Sadowski <gillese...@gmail.com> wrote: > > > > Le lun. 11 févr. 2019 à 11:16, sebb <seb...@gmail.com> a écrit : > > > > > > On Mon, 11 Feb 2019 at 09:24, Gilles Sadowski <gillese...@gmail.com> > > > wrote: > > > > > > > > Hi. > > > > > > > > Le lun. 11 févr. 2019 à 10:02, sebb <seb...@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-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
