From: Colin Rafferty <craffert@ml.com>
Subject: Re: regexp syntax, nnmail split: "s1 not-followed-by s2"
Date: 10 Dec 1997 17:15:00 -0500 [thread overview]
Message-ID: <ocrn2i8j15n.fsf@ml.com> (raw)
In-Reply-To: Karl Kleinpaste's message of "10 Dec 1997 12:27:39 -0500"
Karl Kleinpaste writes:
> I want to experiment with an acquaintance's 2-rule anti-spam trap. If:
> 1. Neither To: nor Cc: contains one's own address, and
> 2. The origin is not a known mailing list,
> then it's probably spam. I've got a bunch of other spam-avoidant
> rules, but I'd like to try these out. Unfortunately, it's not clear
> to me how I go about expressing a not-followed-by condition in a
> regexp. Any suggestions?
Check out the Gnus Info:
Gnus -> Various -> Thwarting Email Spam
It has a topic on exactly what you want to do.
Basically, I end nnmail-split-fancy with this:
(
....
(to "craffert" "mail.misc")
"mail.auto.spam")
--
Colin
next prev parent reply other threads:[~1997-12-10 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-10 17:27 Karl Kleinpaste
1997-12-10 19:36 ` Harald Meland
1997-12-10 22:15 ` Colin Rafferty [this message]
1997-12-11 3:15 ` Karl Kleinpaste
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=ocrn2i8j15n.fsf@ml.com \
--to=craffert@ml.com \
/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).