From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Reply to on list
Date: Fri, 05 Oct 2007 15:38:59 +0000 [thread overview]
Message-ID: <47065A93.9020706@riverviewtech.net> (raw)
On 10/05/07 10:29, Mohan Sundaram wrote:
> I just realised that reply goes to the member instead of the list.
> Has this changed recently?
No, I don't think this has changed.
I have gotten tired of trying to get list administrators to set the list
up correctly for discussion mailing lists. As such, I set up a Procmail
rule on my system to run formail to change the Reply-To: header for
messages from the mailing list to direct messages back to the mailing
list. So, all I have to do is hit reply, where as most people will have
to reply to all. *SIGH* I'm going to stop before I get fully on my
tainted high horse....
Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2007-10-05 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 15:38 Grant Taylor [this message]
2007-10-05 15:41 ` [LARTC] Reply to on list Mohan Sundaram
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=47065A93.9020706@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=lartc@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox