From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: spam/ham autolearn (spamassassin) markings in summary
Date: Tue, 23 Dec 2003 13:13:46 -0500 [thread overview]
Message-ID: <4n1xqv1jxh.fsf@collins.bwh.harvard.edu> (raw)
In-Reply-To: <plop877k0utxyk.fsf@gnu-rox.org> (Xavier Maillard's message of "Thu, 18 Dec 2003 07:57:23 +0100")
On Thu, 18 Dec 2003, zedek@gnu-rox.org wrote:
> Why not integrating this into spam.el directly ? AFAIK, spamassassin
> is probably one of the most important spam backend missing IMO. It
> would be cool if you can add this in terms of a spam.el
> processor.
There's a SA patch that will be merged sometime after the new year -
it's not written by me, and the author needed to fix a few minor
things.
> Dunno how difficult it would be to write it though (spam.el is quite
> obscure to me).
I'll make sure to update the "black box" example to show how to write
a new backend for spam.el.
Ted
next prev parent reply other threads:[~2003-12-23 18:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 18:07 spam/ham autolearn (spamassassin) markings in summary example Wes Hardaker
2003-12-18 6:57 ` spam/ham autolearn (spamassassin) markings in summary Xavier Maillard
2003-12-23 18:13 ` Ted Zlatanov [this message]
2003-12-18 16:41 ` Ted Zlatanov
2003-12-19 18:04 ` Wes Hardaker
2003-12-23 18:17 ` Ted Zlatanov
2003-12-18 16:55 ` Jeremy Maitin-Shepard
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=4n1xqv1jxh.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).