Re: [PLUG] Change in Reply-To field of PLUG list on 7/14/2019...

[Walt Mankowski via plug <plug@lists.phillylinux.org>]

Hi Fred,

This was intentional and due to the problems on the list that we were
having at the time. I'd have to go through the archives to refresh my
mind about it, but I won't have time for that until the weekend.

There's a setting in Mailman for this and it's currently set to set
the Reply-To header to the poster. That's the recommended
setting. Here's what the docs say about that:

  reply_goes_to_list (general): Where are replies to list messages
  directed? Poster is strongly recommended for most mailing lists.

  This option controls what Mailman does to the Reply-To: header in
  messages flowing through this mailing list. When set to Poster, no
  Reply-To: header is added by Mailman, although if one is present in
  the original message, it is not stripped. Setting this value to
  either This list or Explicit address causes Mailman to insert a
  specific Reply-To: header in all messages, overriding the header in
  the original message if necessary (Explicit address inserts the
  value of reply_to_address).

  There are many reasons not to introduce or override the Reply-To:
  header. One is that some posters depend on their own Reply-To:
  settings to convey their valid return address. Another is that
  modifying Reply-To: makes it much more difficult to send private
  replies. See `Reply-To' Munging Considered Harmful for a general
  discussion of this issue. See Reply-To Munging Considered Useful for
  a dissenting opinion.

  Some mailing lists have restricted posting privileges, with a
  parallel list devoted to discussions. Examples are `patches' or
  `checkin' lists, where software changes are posted by a revision
  control system, but discussion about the changes occurs on a
  developers mailing list. To support these types of mailing lists,
  select Explicit address and set the Reply-To: address below to point
  to the parallel list.

I find it a little annoying at times too, but I generally only reply
to the list from mutt which has some features to handle this. I'd be
open to changing it back, but I'd like to be sure I understand any
potential ramifications first.

Walt

On Fri, Jan 22, 2021 at 09:59:45AM -0500, Fred Stluka via plug wrote:
> PLUG folks,
> 
> I just noticed that the behavior of Reply-To changed on 7/14/2019.
> 
> Before that a reply went to the entire list by default.  Since that
> date, the Reply-To field has been changed, so a reply goes only to
> the original poster (OP).  You can see the transition clearly in the
> archives, where the Reply-To field is shown for each message.
> 
> This may be related to the message (appended below) posted by
> Walt on 7/7/2019, where he talks about making changes to the
> list's email box.
> 
> I looked through my Sent folder and found a bunch of replies that
> I had intended to send to the entire list in the past 18 months, that
> only went to the OP.  I had caught and re-sent some of them at the
> time because the OP noticed and asked why I had sent only to him,
> not the entire list.  Or because I was surprised at the lack of replies
> to my reply.
> 
> I suspect others of you may have made the same mistake.  Please
> don't take it personally.  We're not ignoring your posts.  We're simply
> not seeing them.
> 
> Walt, can you or someone please look into this?  Was it an intentional
> change or an accident?  Thanks!
> 
> --Fred
> ------------------------------------------------------------------------
> Fred Stluka -- http://bristle.com -- Glad to be of service!
> Open Source: Without walls and fences, we need no Windows or Gates.
> ------------------------------------------------------------------------
> 
> > *[PLUG] Mailing list admin notice -- DMARC changes*
> > 
> >   * /From/: Walt Mankowski via plug <plug@lists.phillylinux.org
> >     <mailto:plug%40lists.phillylinux.org>>
> >   * /To/:plug@lists.phillylinux.org <mailto:plug%40lists.phillylinux.org>
> >   * /Subject/: [PLUG] Mailing list admin notice -- DMARC changes
> >   * /Date/: Sun, 7 Jul 2019 19:50:24 -0400
> >   * /Dkim-signature/: v=1; a=rsa-sha1; c=relaxed; d=pobox.com;
> >     h=date:from:to :subject:message-id:mime-version:content-type;
> >     s=sasl; bh=yJzokl hxSNkpER36kOQcAIKJGDQ=;
> >     b=QdyHdrv0SIpR1uviLxvFMLYZS6qUXlU9BRuKIa
> >     o8tWxHT4VPIk3JvdOUFghXRFxdyG7IaSHtY1dddW9WOD3CQx8v59oUnDJ9xhNufx
> >     jEXcCr261lS/OnLAOQKUhqWoTP9pZAwLS8bNtFqNEVb5nRd8ZHbd1NT5gkhDVrLW
> >     mNNvE=
> >   * /Reply-to/: Walt Mankowski <waltman@pobox.com
> >     <mailto:waltman%40pobox.com>>, Philadelphia Linux User's Group
> >     Discussion List <plug@lists.phillylinux.org
> >     <mailto:plug%40lists.phillylinux.org>>
> >   * /Sender/: "plug" <plug-bounces@lists.phillylinux.org
> >     <mailto:plug-bounces%40lists.phillylinux.org>>
> >   * /User-agent/: Mutt/1.10.1 (2018-07-13)
> > 
> > ------------------------------------------------------------------------
> > Hi everyone,
> > 
> > It sounds like it might take a few weeks to get our email box updated
> > to the latest version of Debian. In the meantime I've gone ahead and
> > changed the "from_is_list" setting from "No" to "Munge From". That
> > will change the "From:" mail header and may potentially break some
> > users' mail filters.
> > 
> > You should be able to compare the headers on this message to other
> > ones I've sent to the list to see how it's changed.
> > 
> > Walt
> > 
> 
> ___________________________________________________________________________
> Philadelphia Linux Users Group         --        http://www.phillylinux.org
> Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
> General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug

Attachment: signature.asc
Description: PGP signature

___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug