From: Piers Cawley <pdcawley-ding@bofh.org.uk>
Subject: Adding a spam processor
Date: Wed, 14 May 2003 09:07:32 +0100 [thread overview]
Message-ID: <m2he7y54u3.fsf@huge.bofh.org.uk> (raw)
So, I started work on a Spamassassin spam processor now that
Spamassassin has its own rather lovely Bayesian system.
What I'd hoped to do was to have a spam-spamassassin.el which would
have all the spamassassin related code, without having to alter any of
the main gnus distribution files (mostly because I want to be able to
distribute the resulting code without having to fart about signing
papers).
But, of course, I can't.
In an ideal world, I want to be able to do
(spam-add-post-processor "spamassassin")
and have that magically insert the appropriate entries into the
spam-process gnus-group parameter definition, tweak
spam-summary-prepare-exit, etc.
But on looking at the code, everything appears to be hardwired. So
would there be an interest in adding things like:
(gnus-group-param-add-choices (PARAM &rest CHOICES))
and modifying spam-summary-prepare-exit to be rather more dynamic?
Also, on a Spamassassin specific note, Spamassassin currently does a
quite dramatic modification of messages that it thinks are spam,
hiding the original message away in a MIME part. This can be stripped
away with 'spamassassin -d'. It occurs to me that this could be dealt
with rather neatly by adding a 'filter' parameter to
gnus-summary-move-article (or adding a new function), which would
filter the message through an arbitrary command before inserting it in
the destination mailbox.
--
Piers
next reply other threads:[~2003-05-14 8:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 8:07 Piers Cawley [this message]
2003-05-20 18:21 ` 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=m2he7y54u3.fsf@huge.bofh.org.uk \
--to=pdcawley-ding@bofh.org.uk \
/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).