From: Stefan Waldherr <swa@cs.cmu.edu>
Subject: Smart recipe for fancy-splitting
Date: 13 Oct 1997 17:49:45 -0400 [thread overview]
Message-ID: <upkbu0tmiyu.fsf@mind.learning.cs.cmu.edu> (raw)
Hi,
I recently receive a lot of spam from a jerk that uses (or used) the following
addresses:
vension@jumpoint.com
sales@number18.tierranet.com
nobody@nowhere.com
cjohnson@haz-uky.campus.mci.net
cypcomm@rocketmail.com
I could easily delete any mails matching one of the above addresses. However,
this is of no use, since the bozo changes his email address quite often. On
the other hand he sticks to one pattern: the `from' and `to' lines are always
identical.
Well, I wonder whether someone could provide me with a recipe for
nnmail-split-fancy that nukes every mail with identical `from' and `to' lines?
It would also be nice to have a recipe that matches bogus IP addresses, like
x.256.x.x or x.x.006.x. Any ideas?
cu
Stefan.
--
Stefan Waldherr office +1 (412) 268-3837
fax +1 (412) 268-5576
e-Mail swa@cs.cmu.edu
www http://mind.learning.cs.cmu.edu/
next reply other threads:[~1997-10-13 21:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-13 21:49 Stefan Waldherr [this message]
1997-10-14 1:13 ` Matt Simmons
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=upkbu0tmiyu.fsf@mind.learning.cs.cmu.edu \
--to=swa@cs.cmu.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;
as well as URLs for NNTP newsgroup(s).