Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Alex Schroeder <alex@emacswiki.org>
Subject: Re: spam-stat.el -- filtering spam based on statistics as suggested by Paul Graham
Date: Sun, 01 Sep 2002 02:37:28 +0200	[thread overview]
Message-ID: <87heha4kaf.fsf@emacswiki.org> (raw)
In-Reply-To: <87znv5fqlz.fsf@emacswiki.org>

Hm, I've been using it in my .gnus for a while now, and I get errors
in nnml-split-fancy when I use the following setup.  This setup does
some spam filtering beforehand, then it uses the BBDB to split, and
then at very end, I try to figure out wether the remaining mail should
go into mail.misc or mail.spam.  This is where I use the split 
(: spam-stat-split-fancy).  The errors, however, results in several mails
getting split into the bogus group.  Does anybody know what is wrong
with my code?  Suggestions as to debug it?  Maybe wrap the body of
spam-stat-split-fancy in a condition-case or something?
Perhaps this is related to some problems with cl.el specific functions
being used without a (require 'cl) in the file in Emacs?  At startup
that could mean that these functions fail, but after a while cl.el is
loaded and the error disappears?

Alex.


(setq nnmail-crosspost nil
      nnmail-split-methods 'nnmail-split-fancy
      bbdb/gnus-split-default-group nil
      bbdb/gnus-split-nomatch-function nil
      bbdb/gnus-split-myaddr-regexp gnus-ignored-from-addresses
      nnmail-expiry-wait 28
      gnus-total-expirable-newsgroups
      (regexp-opt '("mail.guile"
		    "mail.gnutella"
		    "mail.emacs.devel"
		    "mail.emacs.ilisp"
		    "mail.frieden.jetzt"
		    "mail.baeckeranlage"))
      nnmail-split-fancy
      `(| ("Gnus-Warning" "This is a duplicate" "mail.spam.duplicates")
	  ;; spam filtering based on spam assassin
	  ;; ("X-Spam-Flag" "YES" "mail.spam")
	  ("X-Spam-Level" "\\*\\*\\*\\*\\*\\*\\*" "mail.spam")
	  ;; computer challenged people I know sending me HTML mails
	  ("From" "Sarah Leiken" "mail.family")
	  ;; remaining HTML only mail is spam
	  ("Content-Type" "text/html" "mail.spam")
	  ;; weird character sets are spam, too
	  ("Subject" "=?ks_c_5601-1987" "mail.spam")
	  ;; virus detection is spam
	  ("Subject" "^Norton AntiVirus detected" "mail.spam")
	  ;; temporary spam stuff
	  (any "machine365.com" "mail.spam")
	  ;; now use the BBDB to split
	  (: (lambda ()
	       (car (bbdb/gnus-split-method))))
	  ;; some of the packages I maintain
	  ("Subject" "\\(color-theme\\|ansi-color\\)" "mail.emacs")
	  ;; spam filtering based on statistics
	  (: spam-stat-split-fancy)
	  ;; mail from and to me, mail to any of the emacswiki addresses
	  (any ,gnus-ignored-from-addresses "mail.misc")
	  (any ".*@emacswiki.org" "mail.emacs.wiki")
	  ;; anonymous mail, probably spam
	  "mail.spam"))


      parent reply	other threads:[~2002-09-01  0:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87hehtirad.fsf@emacswiki.org>
     [not found] ` <87wuqm6egm.fsf@emacswiki.org>
     [not found]   ` <87lm6t5hwl.fsf@emacswiki.org>
     [not found]     ` <m3lm6sapqc.fsf@defun.localdomain>
     [not found]       ` <87bs7nlr3m.fsf@emacswiki.org>
2002-08-28 11:14         ` Kai Großjohann
     [not found]     ` <8765xvlr1o.fsf@emacswiki.org>
     [not found]       ` <87znv5fqlz.fsf@emacswiki.org>
2002-09-01  0:37         ` Alex Schroeder [this message]

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=87heha4kaf.fsf@emacswiki.org \
    --to=alex@emacswiki.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).