From: Billy Harvey <Billy.Harvey@thrillseeker.net>
To: Jauder Ho <jauderho@carumba.com>
Cc: linux-kernel@vger.rutgers.edu
Subject: Re: Forwarded mail....
Date: Wed, 03 Jun 1998 10:47:10 -0500 [thread overview]
Message-ID: <m0yhFkt-000OwsC@maestro.thrillseeker.net> (raw)
In-Reply-To: Your message of "Wed, 03 Jun 1998 02:30:11 PDT." <Pine.LNX.3.96.980603022914.30744A-100000@marvin.transmeta.com>
Jauder,
What works well for me is to put the following in my procmail:
M=.Mail
L=$LOCKEXT
R=/usr/lib/mh/rcvstore
T=Trash
# :0 c:$M/$T/$L
# | $R +$T
# Check for duplicate messages and send them to the Trash
:0 Whc: .msgid.lock
| formail -D 65536 .msgid.cache
T=Trash
:0 a:$M/$T/$L
| $R +$T
# Trash stuff sent directly to linux lists instead of via vger
T=Trash
:0 :$M/$T/$L
* ^Sender: owner-linux-.*@vger\.rutgers\.edu
# * ! ^(((To|Cc):)|( )).*linux-.*@vger\.rutgers\.edu
* ! ^(((To|Cc):)|( )).*linux
| $R +$T
# Trash subscribe/unsubscribe messages
T=Trash
:0 :$M/$T/$L
* ^Subject: .*subscr
| $R +$T
# Trash non-delivery messages
T=Trash
:0 :$M/$T/$L
* ^Subject:.*non-delivery*
| $R +$T
This moves suspicious stuff into a 'Trash' folder, which I can then examine at
my leisure. It's fairly easy to scan all the subjects and delete the contents
of the folder in about 3 seconds, or read a specific email that was mistakenly
filed.
This works fairly well on the linux lists since spammers usually leave the To:
header blank.
Regards,
Billy Harvey
>
> I think someone is trolling the listserver again. This sucks. I
> can't even filter for this.
>
> --jauder
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
parent reply other threads:[~1998-06-03 14:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.LNX.3.96.980603022914.30744A-100000@marvin.transmeta.com>]
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=m0yhFkt-000OwsC@maestro.thrillseeker.net \
--to=billy.harvey@thrillseeker.net \
--cc=jauderho@carumba.com \
--cc=linux-kernel@vger.rutgers.edu \
/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
all inboxes | Powered by JetHome®