On Wed 31 Aug 2016 at 16:10:37 (+0200), Nicolas George wrote:
> Le quartidi 14 fructidor, an CCXXIV, David Wright a écrit :
> > The error might have been mine. I think I CC'd Lisi in error.
> > The other list I'm on expects people to group-reply.
> > I forgot myself.
After some experiments, I think I have to withdraw that explanation.
Group-reply would have put
To: Lisi ..., debian-user@lists.debian.org
whereas my posting had
To: debian-user@lists.debian.org
Cc: Lisi ...
which is what list-reply writes¹.
In fact, the problem was that the posting I replied to had
Mail-Followup-To: Lisi ..., debian-user@lists.debian.org
in the header, which mutt dutifully obeyed *and* copied into my reply.
I might have spotted that Lisi was CC'd, but the copying of
Mail-Followup-To into my posting happens behind the scenes,
like handling References.
I suppose I could set a blank Mail-Followup-To in my composition
editor to prevent its auto-generation. (I don't do anything
sophisticated like posting to multiple lists.) But that might defeat
people who use Mail-Followup-To as a way of receiving replies without
being subscribed to the list, so maybe that's not a good idea.
> Systematic group-reply is the correct way of using mailing-lists, because it
> is the only way that does not require the user to waste time for each mail
> deciding the proper key to hit.
>
> This clause of the code of conduct is unsustainable, and therefore should be
> ignored until the configuration is fixed and the corresponding clause
> updated.
>
> In the meantime, let the whiners whine; the non-whiners can unilaterally fix
> things for themselves by setting the reply-to header, just like you or me.
Yes, I can't understand why more people don't set it.
In the dim and distant past, I put
:0 Wh: $HOME/msgid.lock
| formail -D 199999 $HOME/msgid.cache
into my .procmailrc file which got rid of any duplicates.
¹ only when replying to that particular posting of course.
Cheers,
David.
