From: Karl Kleinpaste <karl@jprc.com>
Subject: regexp syntax, nnmail split: "s1 not-followed-by s2"
Date: 10 Dec 1997 12:27:39 -0500 [thread overview]
Message-ID: <vxkn2i9nm5w.fsf@pocari-sweat.jprc.com> (raw)
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?
Obviously, this simple rule is not perfect, as it will mis-classify as
spam any mail in which one was properly addressed using Bcc:.
Also, in looking at the documentation for nnmail-split-fancy, because
I thought it might be necessary for my anti-spam effort (but now that
I think I understand -fancy, it won't help -- I have nnmail-crosspost
set to nil), the 1st line of the example contains a token `mail' (not
a string) which should be enclosed in quotes as a string.
next reply other threads:[~1997-12-10 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-10 17:27 Karl Kleinpaste [this message]
1997-12-10 19:36 ` Harald Meland
1997-12-10 22:15 ` Colin Rafferty
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=vxkn2i9nm5w.fsf@pocari-sweat.jprc.com \
--to=karl@jprc.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).