Gnus development mailing list
 help / color / mirror / Atom feed
From: David Z Maze <dmaze@MIT.EDU>
Subject: Re: Spam Management When Using nnimap
Date: Fri, 16 May 2003 12:43:38 -0400	[thread overview]
Message-ID: <871xyyu9j9.fsf@cag.lcs.mit.edu> (raw)
In-Reply-To: <76of23di1o.fsf@newjersey.ppllc.com> (Jake Colman's message of "Thu, 15 May 2003 17:19:31 -0400")

Jake Colman <colman@ppllc.com> writes:

>>>>>> "CG" == Chris Green <cmg@sourcefire.com> writes:
>
>    CG> http://lifelogs.com/spam/spam.html seems to be the best tutorial for
>    CG> this.
>
> But where is the determination of what constitutes a spam email?  Unless I
> missed something, there is nothing in that tutorial that shows me how/what to
> use as hook in gnus so that messages are automatically clasified as spam or
> ham.

Those are the various spam-use-* flags.  If you wanted to add your own
classifier, you'd need to add it to spam-list-of-checks.  The check
functions appear to be called with no parameters with the current
buffer narrowed to the headers of the article in question, and return
t if the article is ham, spam-split-group (or another group name) if
the article is spam, and nil for undecided.

-- 
David Maze             dmaze@mit.edu          http://www.mit.edu/~dmaze/
"Theoretical politics is interesting.  Politicking should be illegal."
	-- Abra Mitchell




  reply	other threads:[~2003-05-16 16:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-15 20:10 Jake Colman
2003-05-15 21:05 ` Chris Green
2003-05-15 21:19   ` Jake Colman
2003-05-16 16:43     ` David Z Maze [this message]
2003-05-16 19:10       ` Jake Colman
2003-05-17 23:38         ` David Abrahams
2003-05-20 18:45       ` Ted Zlatanov
2003-05-20 18:41   ` Ted Zlatanov
2003-05-20 18:39 ` Ted Zlatanov

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=871xyyu9j9.fsf@cag.lcs.mit.edu \
    --to=dmaze@mit.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).