emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: <tomas@tuxteam.de>
To: emacs-orgmode@gnu.org
Subject: Re: Reply-All noise
Date: Fri, 9 Oct 2020 22:10:41 +0200	[thread overview]
Message-ID: <20201009201041.GA26193@tuxteam.de> (raw)
In-Reply-To: <4C7J0z6zLHz6tmH@submission01.posteo.de>

[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]

On Fri, Oct 09, 2020 at 09:24:34PM +0200, c.buhtz@posteo.jp wrote:
> Hi,
> 
> I had this discussion in several mailinglists but gave up.
> 
> But I am suprised to see this phenomenon in a emacs related (means:
> "super nerdy") mailinglist, too.
> 
> So tell me please how do you handle this "problem"? Or do I setup
> something wrong with my list account?

There is no clear-cut answer to that. For mailing lists which allow
posting by non-subscribers (this is one), reply-to-all makes more
sense to reply-to-all, since you can't be sure that everyone is
subscribed.

As for what I do, I have a mail filter (procmail) which weeds out
duplicates fairly effectively.

For this list, specifically, which is managed by Mailman, you can
tell the list manager [1] to not send you a duplicate when your
address is in the To: or Cc: header field. Note that you'll get
the copy sent to you, not the one sent via the list; if you are
filtering based on list headers, this might not be what you want.

To appreciate the whole "interesting" complexity see [2]. In a
nutshell, there's no ideal solution working for all tastes.

Cheers

[1] https://www.gnu.org/software/mailman/mailman-member/node21.html
[2] http://david.woodhou.se/reply-to-list.html

 - t

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2020-10-09 20:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09 19:24 Reply-All noise c.buhtz
2020-10-09 20:10 ` tomas [this message]
2020-10-09 20:41   ` tomas
2020-10-10  8:57     ` c.buhtz
2020-10-10  9:10       ` tomas
2020-10-10 10:45         ` c.buhtz
2020-10-10 14:40     ` Jens Lechtenboerger
2020-10-30 11:30   ` Russell Adams
2020-10-30 12:14     ` Eric S Fraga
2020-10-09 21:22 ` Tory S. Anderson
2020-10-10  8:03 ` Maxim Nikulin
2020-10-10  8:53   ` c.buhtz
2020-10-10  9:05     ` tomas
2020-10-10 13:57     ` Maxim Nikulin
2020-10-10 18:56       ` c.buhtz
2020-10-11 13:58     ` Eric S Fraga
2020-10-11 14:35       ` c.buhtz
2020-10-11 15:21         ` Eric S Fraga
2020-10-11 21:32           ` Tim Cross
2020-10-11 22:25             ` Eric Abrahamsen
2020-11-01 18:38 ` Anthony Carrico

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201009201041.GA26193@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).