Re: Reply to list vs. group reply [was: Inlclusive terminology...]

From	Geert Stappers <stappers@stappers.nl>
Newsgroups	linux.debian.user
Subject	Re: Reply to list vs. group reply [was: Inlclusive terminology...]
Date	2024-02-25 13:20 +0100
Message-ID	<IblE5-cwRV-3@gated-at.bofh.it> (permalink)
References	(5 earlier) <Ibg1H-ctyz-3@gated-at.bofh.it> <Ibhh7-cucc-1@gated-at.bofh.it> <IbiZz-cvfm-1@gated-at.bofh.it> <Ibj9g-cviv-13@gated-at.bofh.it> <IbjiV-cvlP-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

Summary:  exposing a troll

On Sun, Feb 25, 2024 at 10:48:17AM +0100, tomas@tuxteam.de wrote:
> On Sun, Feb 25, 2024 at 10:35:33AM +0100, Geert Stappers wrote:
> } troll tomas wrote:
> } } I think I'm out of it. *Plonk*
> [Adjusting the topic]
> 
> > For keeping that promise would it be better to use "Reply-To-List".
> > 
> > And in other cases is it also better to use "Reply-To-List".
> 
> I know it is a hot topic here. Preferences vary by the sender, which
> I can't perfectly know.
> 
> My e-mail client honours "Mail-Followup-To", which is the sender's
> way to state "hey, I'd prefer for you to send replies to...",
> usually to the list address.

There is no 'Mail-Followup-To" header in email sent by Zenaan Harkness.

There is difference in To headers from troll tomas in reply to Zenaan
messages. In https://lists.debian.org/debian-user/2024/02/msg01022.html
is the To this mailinglist. In https://lists.debian.org/debian-user/2024/02/msg01027.html
that is the email with "I think I'm out of it" is the To Zenaan and Cc
to the mailinglist.
I call the 'My e-mail client honours "Mail-Followup-To"' bullshit.

Then the promise of "I'm out of it" was broken.  Probably due my troll
feeding. I should have ignored the passive agressive "To: Zenaan"

> [...]
> 
> > P.S.
> > The better e-mail client has 3 reply buttons:
> > - Reply
> > - Reply-To-All
> > - Reply-To-List
> 
> Mine has those.

https://lists.debian.org/debian-user/2024/02/msg01029.html has
documented that the troll did choose "Reply-To-All".

> It *also* honours "Mail-Followup-To" (and could set it, if I cared
> the other way around, but my MDA eliminates dupes anyway, so I'm happy
> both ways).
> 
> If you care, you might consider setting your "Mail-Followup-To" header?

There is no technical problem, email headers and mail-user-agents wouldn't
help to solve it.  The challenge is to spend attention to what deserves
attention. Troll email doesn't deserve attention.

Time will tell if the signal noise ratio improves.

> Cheers
> -- 
> t

Groeten
Geert Stappers
Also wrote
- https://lists.debian.org/debian-user/2024/02/msg01035.html  (sad)
- https://lists.debian.org/debian-user/2024/02/msg00994.html  (hope)
-- 
Silence is hard to parse

Thread

Inclusive terminology (instead of master/slave) for network  bonding/LACP Ralph Aichinger <ra@h5.or.at> - 2024-02-22 11:40 +0100
  Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Andy Smith <andy@strugglers.net> - 2024-02-23 07:10 +0100
  Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Mariusz Gronczewski <xani@devrandom.pl> - 2024-02-23 10:50 +0100
    Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP <tomas@tuxteam.de> - 2024-02-23 11:00 +0100
      Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Marco Moock <mm@dorfdsl.de> - 2024-02-23 11:10 +0100
        Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP tomas@tuxteam.de - 2024-02-23 11:20 +0100
      Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Mariusz Gronczewski <xani@devrandom.pl> - 2024-02-23 12:20 +0100
    Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Alain D D Williams <addw@phcomp.co.uk> - 2024-02-23 11:10 +0100
      Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Marco Moock <mm@dorfdsl.de> - 2024-02-23 11:30 +0100
        Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP <tomas@tuxteam.de> - 2024-02-23 19:30 +0100
      Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Mike Castle <dalgoda+debian@gmail.com> - 2024-03-14 19:30 +0100
        Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Emanuel Berg <incal@dataswamp.org> - 2024-03-15 01:50 +0100
          Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Alain D D Williams <addw@phcomp.co.uk> - 2024-03-15 09:50 +0100
            Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Mike Castle <dalgoda+debian@gmail.com> - 2024-03-15 17:10 +0100
              Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP <tomas@tuxteam.de> - 2024-03-15 17:20 +0100
              Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Emanuel Berg <incal@dataswamp.org> - 2024-03-15 17:40 +0100
            Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Emanuel Berg <incal@dataswamp.org> - 2024-03-15 17:30 +0100
          Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Will Mengarini <seldon@eskimo.com> - 2024-03-15 19:20 +0100
            Please terminate this faecal matter - the whole thread appears to be  a troll.....Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Bret Busby <bret@busby.net> - 2024-03-15 20:00 +0100
              Re: Please terminate this faecal matter - the whole thread appears to  be a troll.....Re: Inclusive terminology (instead of master/slave) for  network bonding/LACP Jeffrey Walton <noloader@gmail.com> - 2024-03-15 23:30 +0100
            Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Emanuel Berg <incal@dataswamp.org> - 2024-03-15 21:50 +0100
    Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Arno Lehmann <al@its-lehmann.de> - 2024-02-23 12:50 +0100
      Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Marco Moock <mm@dorfdsl.de> - 2024-02-23 13:20 +0100
      Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Mariusz Gronczewski <xani@devrandom.pl> - 2024-02-23 13:40 +0100
      Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Zenaan Harkness <zenaan@gmail.com> - 2024-02-24 23:30 +0100
        Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Karen Lewellen <klewellen@shellworld.net> - 2024-02-25 00:20 +0100
          Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP <tomas@tuxteam.de> - 2024-02-25 07:30 +0100
            Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Zenaan Harkness <zenaan@gmail.com> - 2024-02-25 08:40 +0100
            Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Mariusz Gronczewski <xani@devrandom.pl> - 2024-02-25 12:50 +0100
    Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Andy Smith <andy@strugglers.net> - 2024-02-23 15:50 +0100
  Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Marco Moock <mm@dorfdsl.de> - 2024-02-23 11:10 +0100
    Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Roger Price <roger@rogerprice.org> - 2024-02-23 11:50 +0100
      Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Mariusz Gronczewski <xani@devrandom.pl> - 2024-02-23 12:20 +0100
        Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Andy Smith <andy@strugglers.net> - 2024-02-23 15:40 +0100
    Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Jeffrey Walton <noloader@gmail.com> - 2024-02-23 17:30 +0100
      Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Dan Ritter <dsr@randomstring.org> - 2024-02-23 19:10 +0100
        Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Gremlin <scott-andrews@columbus.rr.com> - 2024-02-23 19:20 +0100
          Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Jeffrey Walton <noloader@gmail.com> - 2024-02-23 21:00 +0100
        Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Marco Moock <mm@dorfdsl.de> - 2024-02-23 20:00 +0100
          Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Emanuel Berg <incal@dataswamp.org> - 2024-02-24 12:30 +0100
            Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP jeremy ardley <jeremy.ardley@gmail.com> - 2024-02-24 12:40 +0100
              Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Emanuel Berg <incal@dataswamp.org> - 2024-02-24 14:50 +0100
                Re: Inclusive terminology (instead of master/slave) for network bonding/LACP The Wanderer <wanderer@fastmail.fm> - 2024-02-24 15:10 +0100
                Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Alain D D Williams <addw@phcomp.co.uk> - 2024-02-24 18:00 +0100
                Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP <tomas@tuxteam.de> - 2024-02-24 19:40 +0100
                Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Zenaan Harkness <zenaan@gmail.com> - 2024-02-24 23:20 +0100
                Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP <tomas@tuxteam.de> - 2024-02-25 07:20 +0100
                Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Zenaan Harkness <zenaan@gmail.com> - 2024-02-25 08:40 +0100
                Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP tomas@tuxteam.de - 2024-02-25 10:30 +0100
                Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Geert Stappers <stappers@stappers.nl> - 2024-02-25 10:40 +0100
                Reply to list vs. group reply [was: Inlclusive terminology...] <tomas@tuxteam.de> - 2024-02-25 10:50 +0100
                Re: Reply to list vs. group reply [was: Inlclusive terminology...] Geert Stappers <stappers@stappers.nl> - 2024-02-25 13:20 +0100
                Postel's Law (Was Re: Inclusive terminology (instead of  master/slave) for network bonding/LACP) Andy Smith <andy@strugglers.net> - 2024-02-24 22:40 +0100
                Re: Postel's Law (Was Re: Inclusive terminology (instead of  master/slave) for network bonding/LACP) Jeffrey Walton <noloader@gmail.com> - 2024-02-25 01:50 +0100
                Re: Postel's Law (Was Re: Inclusive terminology (instead of  master/slave) for network bonding/LACP) Mariusz Gronczewski <xani@devrandom.pl> - 2024-02-25 12:10 +0100
                Re: Postel's Law (Was Re: Inclusive terminology (instead of  master/slave) for network bonding/LACP) Alain D D Williams <addw@phcomp.co.uk> - 2024-02-25 12:30 +0100
                Re: Postel's Law (Was Re: Inclusive terminology (instead of  master/slave) for network bonding/LACP) Mariusz Gronczewski <xani@devrandom.pl> - 2024-02-25 13:00 +0100
                Re: Postel's Law (Was Re: Inclusive terminology (instead of  master/slave) for network bonding/LACP) Nicholas Geovanis <nickgeovanis@gmail.com> - 2024-02-25 02:00 +0100
                Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Emanuel Berg <incal@dataswamp.org> - 2024-03-14 18:00 +0100
                Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Mariusz Gronczewski <xani@devrandom.pl> - 2024-02-24 21:50 +0100
                Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Marco Moock <mm@dorfdsl.de> - 2024-02-25 00:30 +0100
                Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Zenaan Harkness <zenaan@gmail.com> - 2024-02-25 00:50 +0100
                Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Mariusz Gronczewski <xani@devrandom.pl> - 2024-02-25 12:40 +0100
    Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Ralph Aichinger <ra@h5.or.at> - 2024-02-23 21:20 +0100
  Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Andy Smith <andy@strugglers.net> - 2024-02-23 15:50 +0100
    Re: Inclusive terminology (instead of master/slave) for network bonding/LACP fxkl47BF@protonmail.com - 2024-02-23 16:00 +0100
      Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Mariusz Gronczewski <xani@devrandom.pl> - 2024-02-23 18:20 +0100
        Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Andy Smith <andy@strugglers.net> - 2024-02-23 21:20 +0100
          Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Ralph Aichinger <ra@h5.or.at> - 2024-02-23 21:50 +0100
            Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Andy Smith <andy@strugglers.net> - 2024-02-23 22:20 +0100
          Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Zenaan Harkness <zenaan@gmail.com> - 2024-02-24 03:40 +0100
            Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Andy Smith <andy@strugglers.net> - 2024-02-24 04:00 +0100
              Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Zenaan Harkness <zenaan@gmail.com> - 2024-02-24 23:20 +0100
                Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Andy Smith <andy@strugglers.net> - 2024-02-24 23:30 +0100
    Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Mariusz Gronczewski <xani@devrandom.pl> - 2024-02-23 18:20 +0100
      Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Ralph Aichinger <ra@h5.or.at> - 2024-02-23 21:30 +0100
        Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Charles Curley <charlescurley@charlescurley.com> - 2024-02-23 22:40 +0100
  Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Jeffrey Walton <noloader@gmail.com> - 2024-02-23 20:40 +0100

csiph-web