Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <teodor.zlatanov@divine.com>
Subject: Re: Wanted: Gnus plugin to submit spam to ordb.org
Date: Tue, 30 Apr 2002 15:39:25 -0400	[thread overview]
Message-ID: <m3adrl2cya.fsf@onyx.nimbus.northernlight.com> (raw)
In-Reply-To: <m3ofg1f187.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Tue, 30 Apr 2002 15:13:54 -0400")

On Tue, 30 Apr 2002, prj@po.cwru.edu wrote:
> Ted Zlatanov <teodor.zlatanov@divine.com> wrote:
>> My major concern (and the reason why I haven't been doing too much
>> work on this) is that generally, in Gnus marks do not trigger
>> actions directly.
> 
> The 'expire mark does, sort of.  But if you'd like to avoid that, a
> function could be added to gnus-summary-exit-hook to look for
> articles with the spam mark and report them.  This isn't too great a
> one-time burden for the users, is it?

On the contrary, as I said, I think it makes perfect sense :) My only
concern was that other Gnus users would think it strange that marking
an article suddenly takes a few seconds and actually performs an
action.  From the lack of an outcry, and from yours and Kai's
comments, I guess everyone is OK with having the 'spam' mark trigger
the spam actions.

OK, for the plan of action.  Note that this is very general at this
point, I'm looking to define what's needed.  Variable names are
definitely subject to change - suggestions are welcome.  Ditto for
invocation methods.

Let's define spam checking and reporting backends.  Right now we
have blacklists, whitelists, and spam-blackhole-servers:

(defvar spam-blackhole-servers
  '("bl.spamcop.net" "relays.ordb.org" "dev.null.dk"
    "relays.visi.com" "rbl.maps.vix.com"))

I'd like to break the blackhole servers into individual symbols.  The
users would say something like:

(add-to-list spam-checking-backends 'spamcop)
(add-to-list spam-checking-backends 'ordb)
(add-to-list spam-checking-backends 'blacklist)
(add-to-list spam-checking-backends 'whitelist) ; scores everything but whitelisted senders down 1000, for instance

and then they would add the spam-check function to their nnml-split or
nnimap-split.  So we'll have spamcop, ordb, dev-null-dk, visi, vix.
Or should this be a generic 'blackhole symbol which uses the list of
blackhole servers?  How likely is the list of blackhole servers to
change or need modification by the user?

Should the split function just score things down or actually move them
to a "spam" forlder?

The spam-reporting-backends would be triggered (as a hook) by marking
an article as spam.  The user would do:
(add-to-list spam-reporting-backends 'blacklist)
(add-to-list spam-reporting-backends 'ordb)

I need lists of reporting and checking backends that don't follow the
blackhole-servers conventions (using DNS for checks).  See spam.el for
what's already in place for blackhole checks.

Thanks
Ted




  reply	other threads:[~2002-04-30 19:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-29  3:05 Kirk Strauser
2002-04-29  7:58 ` Simon Josefsson
2002-04-29 11:04   ` Oystein Viggen
2002-04-29 11:09     ` Oystein Viggen
2002-04-29 15:43     ` Kirk Strauser
2002-04-29 16:05       ` Ted Zlatanov
2002-04-29 16:10         ` Kirk Strauser
2002-04-29 16:26           ` Ted Zlatanov
2002-04-29 16:53             ` Kai Großjohann
2002-04-30 19:13             ` Paul Jarc
2002-04-30 19:39               ` Ted Zlatanov [this message]
2002-04-30 19:53                 ` Paul Jarc
2002-04-30 21:23                   ` Oystein Viggen
2002-05-01 10:26                 ` Frank Tegtmeyer
2002-05-01 12:11                 ` Malcolm Purvis
2002-04-30 20:46               ` Kai Großjohann
2002-04-30 22:11                 ` Simon Josefsson
2002-05-01 12:44                   ` Jorge Godoy
2002-05-08  8:01                     ` Steinar Bang
2002-04-30 22:18                 ` Paul Jarc
2002-05-01 12:51                   ` Kai Großjohann
2002-05-01 16:11                     ` Paul Jarc

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=m3adrl2cya.fsf@onyx.nimbus.northernlight.com \
    --to=teodor.zlatanov@divine.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).