From: usotsuki@buric.co (Steve Nickolas)
Subject: [TUHS] A Talk on Early Unix
Date: Thu, 30 Jun 2016 07:03:17 -0400 (EDT) [thread overview]
Message-ID: <alpine.BSF.2.02.1606300701080.84389@frieza.hoshinet.org> (raw)
In-Reply-To: <CAD-qYGo5RBsOf-kik16UX43b3Z72nfNSe2Q85rwG44nL7dFUnw@mail.gmail.com>
On Thu, 30 Jun 2016, Andrew Warkentin wrote:
> I really should stop using Gmail's web interface and find an MUA that
> has a "reply to list" feature and defaults to replying to the list for
> messages from the list (it would presumably need explicit filters to
> detect messages from some lists because not all lists use the
> List-Post header). It's annoying when I try to reply to the list and
> instead end up replying to only the poster (I know about the problems
> with Reply-To munging; I'm not sure why it isn't more common for MUAs
> to have a "reply to list" feature to better deal with lists that don't
> munge Reply-To).
I have to go through a bunch of finagling to reply to some lists,
including this one, via Alpine. At least if I select "reply all", I can
just cut-and-paste the addresses. I think it's configurable in the list
manager daemon.
I do seem to remember it being a bigger pain with Google mailing lists.
-uso.
next prev parent reply other threads:[~2016-06-30 11:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 6:56 Warren Toomey
2016-06-30 7:10 ` arnold
2016-06-30 10:30 ` Andrew Warkentin
2016-06-30 10:39 ` Andrew Warkentin
2016-06-30 11:03 ` Steve Nickolas [this message]
2016-06-30 12:17 ` [TUHS] List reply-to Warren Toomey
2016-06-30 14:27 ` Steve Nickolas
2016-06-30 22:34 ` Dave Horsfall
2016-06-30 22:58 ` Random832
2016-07-02 5:59 ` Greg 'groggy' Lehey
2016-06-30 22:22 ` [TUHS] A Talk on Early Unix Dave Horsfall
2016-06-30 14:11 ` Nemo
2016-06-30 12:41 Doug McIlroy
2016-06-30 12:53 ` Ronald Natalie
2016-07-01 3:48 ` Lyndon Nerenberg
2016-07-02 1:57 ` Steve Simon
2016-07-03 1:17 ` Brad Spencer
2016-06-30 13:02 ` Dan Cross
2016-06-30 16:34 Doug McIlroy
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.BSF.2.02.1606300701080.84389@frieza.hoshinet.org \
--to=usotsuki@buric.co \
/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.
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 NNTP newsgroup(s).