From: "Troy Dack" <troy@tkdack.com>
To: <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Gentoo-sources vs "stock" kernels
Date: Fri, 24 Jan 2003 11:23:47 +1100 [thread overview]
Message-ID: <39070.203.10.231.228.1043367827.squirrel@tkdack.bpa.nu> (raw)
In-Reply-To: <034b01c2c31a$5e5dd950$0605010a@VELDYT>
Thomas T. Veldhouse said:
> Addressing your postscript. The list configuration should be changed.
> If I hit reply, it goes to just you. If I hit reply-all, it goes to all
> recipients including you and the list. The list should be reconfigured
> to change the reply-to address to that of the list. I refuse to worry
> about the recipient list for each and every reply I send to this list.
>
The list configuration should *not* be changed, see:
http://www.unicom.com/pw/reply-to-harmful.html
In addition to the points listed in the URL, the gentoo lists have
previously been the victim of poorly configured mail clients that resulted
in the list(s) being spammed with "Joe User's Mailbox is full, please try
later". With reply-to munging this went to the list, back to Joe User and
then bounced again, lather, rinse, repeat!
Evolution as reply-to list, as does SquirrelMail. I believe that Mozilla
has an option to mark a folder as belonging to a mailing list and allows
you to specify a default reply-to address for that folder.
Kim Nielsen said:
> Ps. Don't send a message directly to me, I follow this list so I will
> see your message
Configure procmail appropriately on your mail server (or local box) and
you won't get the duplicates either (see:
http://www.linux.gr/cgi-bin/man2html/usr/share/man/man5/procmailex.5.gz)
--
Troy Dack
http://linux.tkdack.com
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-01-24 0:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 19:05 [gentoo-dev] Gentoo-sources vs "stock" kernels Dewet Diener
2003-01-23 19:16 ` Peter Ruskin
2003-01-23 19:20 ` Kim Nielsen
2003-01-23 19:33 ` Dewet Diener
2003-01-23 19:41 ` Kim Nielsen
2003-01-23 19:48 ` Thomas T. Veldhouse
2003-01-23 19:55 ` Kim Nielsen
2003-01-23 20:02 ` Thomas T. Veldhouse
2003-01-23 20:08 ` Kim Nielsen
2003-01-23 20:21 ` Thomas T. Veldhouse
2003-01-23 21:25 ` Paul de Vrieze
2003-01-23 21:28 ` Thomas T. Veldhouse
2003-01-23 21:33 ` Paul de Vrieze
2003-01-23 21:41 ` Thomas T. Veldhouse
2003-01-23 21:20 ` Paul de Vrieze
2003-01-24 0:23 ` Troy Dack [this message]
2003-01-24 0:58 ` [gentoo-dev] Gentoo-sources vs "stock" kernels Thomas T. Veldhouse
2003-01-23 20:06 ` [gentoo-dev] Gentoo-sources vs "stock" kernels Mike Lundy
2003-01-25 2:04 ` Peter Ruskin
2003-01-23 19:34 ` Dylan Carlson
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=39070.203.10.231.228.1043367827.squirrel@tkdack.bpa.nu \
--to=troy@tkdack.com \
--cc=gentoo-dev@gentoo.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