[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] Re: RAQs for sale site? (Sorry!)
- Subject: [cobalt-users] Re: RAQs for sale site? (Sorry!)
- From: Charlie Summers <charlie@xxxxxxxxxx>
- Date: Mon Jan 7 22:37:18 2002
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
At 8:21 PM -0500 1/7/02, KJV1611@xxxxxxxxxxxx is rumored to have typed:
> Ooops! I guess it helps if I replace the address to make it private. Sorry
>about
> that.
Actually, there's a simple procmail recipe that will solve your problem
and forever keep you from additional embarassment by removing the unnecessary
and annoying Reply-To: header field that mailman adds to this list. Removing
it will allow you to default replies to the sender, yet still easily mail to
the list with a simple Reply-To-All (which even MS email clients can handle,
I've been told). You can ignore the subject munge removal if you _are_ using
an email client that can't filter on arbitrary header fields (like that MS
client I mentioned), and I'm not including my footer removal recipies to keep
from annoying the tolerant folks who manage the list.
Charlie (who thinks these munges cause more trouble then
they're worth; obviously simple rewrites will
let you use this for other lists as well)
# cobalt-users mailing list;
# uses mailman, so X-Been-There: header field loop identifier
:0
* ^X-BeenThere: cobalt-users@xxxxxxxxxxxxxxx
{
# Remove the subject munge...will need to be changed
# if the [listname] section is altered.
:0 fhw
| sed -e '/^Subject:/ s/ \[cobalt-users\]//g'
# Default replies to the author instead of the list,
# allowing Reply-To-All to send to list if desired;
# SmartList has the sense not to munge an existing header
# field, but since I don't know about mailman, be cautious
# and only change if it's set to the list itself...
:0 fhw
* ^Reply-To: cobalt-users@xxxxxxxxxxxxxxx
| formail -R Reply-To: Old-Listadded-Reply-To:
# Sort it into whatever mailfolder, file, or whatever here...
# or don't and let processing continue, your call.
:0:
/path/to/mailbox/or/folder
}