Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: new spam.el parameters: spam-autodetect and spam-autodetect-methods
Date: Sat, 13 Dec 2003 22:50:53 -0500	[thread overview]
Message-ID: <4nu144kqg2.fsf@collins.bwh.harvard.edu> (raw)

After testing it for a week, I added the spam-autodetect and
spam-autodetect-methods parameters (they have corresponding variables
you can customize if you don't want to use group/topic parameters).

spam-autodetect associates nil or t with groups or topics.  You could
use a regex to get all nntp groups, for instance.  When enabled,
spam-autodetect tells spam.el (through spam-find-spam, which is run
when you enter a buffer) that all UNSEEN articles should be checked
for spam.  This is done through the spam-autodetect-methods, which
can be a list of methods, or the default methods you use for
spam-split anyway.  spam-autodetect-methods is also associated with
groups or topics in a flexible way - as a parameter or a regex.

There are two things: the registry can be optionally used to make sure
that messages (by ID) that have already been tagged as spam don't get
rechecked, and the user can ask that ALL, not just the unseen
articles, be checked when you enter the buffer.

Spam autodetection is a little slow, because spam-split can currently
only be invoked on one article at a time.  I'll see if I can improve
this, but meanwhile keep in mind that fast checks are best.

Finally, the new parameters have made group/topic parameters (`G c')
very slow to generate for me.  Maybe it something in my setup, but it
might be a bug in my customization declarations.  Please let me know
if it's the latter.

This is the last change to spam.el I am making for No Gnus.  From now
on, only bug fixes and documentation updates will be made.  I'll
update the Gnus manual to take note of all the spam.el changes.
Thanks for everyone's patience with me.

Ted



                 reply	other threads:[~2003-12-14  3:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4nu144kqg2.fsf@collins.bwh.harvard.edu \
    --to=tzz@lifelogs.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).