Gnus development mailing list
 help / color / mirror / Atom feed
From: Harald Meland <Harald.Meland@usit.uio.no>
Cc: ding@gnus.org
Subject: Re: regexp syntax, nnmail split: "s1 not-followed-by s2"
Date: 10 Dec 1997 20:36:22 +0100	[thread overview]
Message-ID: <d6d67ox6le1.fsf@octarine.uio.no> (raw)
In-Reply-To: Karl Kleinpaste's message of "10 Dec 1997 12:27:39 -0500"

[Karl Kleinpaste]

| Any suggestions?

The most straightforward setup I can think of which does this, is:

(setq nnmail-split-fancy 
      '(|	 
	("gnus-warning" ".*" "duplicates")
	(to "Karl Kleinpaste" "Personal")
	(from mail "Mailer-daemon")
	<bunch of splits saying where mail to and from known addresses
	 should go>
	"Junkmail"))

If you have included explicit splits for all the obscure aliases,
lists and whatnot you want to receive mail from, the "Junkmail"
mailbox will come very close to containing nothing but spam (and very
little of the spam I'm receiving has my name anywhere in it).  Bcc: is
a problem, but are there many of us who receive lots and lots of
Bcc'ed mail from different places all the time?

| 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.

Nope, see the variable `nnmail-split-abbrev-alist'.
-- 
Harald


  reply	other threads:[~1997-12-10 19:36 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 [this message]
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=d6d67ox6le1.fsf@octarine.uio.no \
    --to=harald.meland@usit.uio.no \
    --cc=ding@gnus.org \
    /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).