From: Russ Allbery <rra@stanford.edu>
Subject: Some more bogofilter information
Date: Tue, 10 Jun 2003 09:08:36 -0700 [thread overview]
Message-ID: <87isrdc3uj.fsf@windlord.stanford.edu> (raw)
I haven't had time to turn this into a patch to the manual, and I'm not
sure if I will have time, but I just finished setting up bogofilter and
wrote up some of the things that I found confusing as well as some random
notes on the process.
(One of the things that I found confusing was that the documentation
really did not explain how to set the relevant variables by hand if one
didn't want to use group properties or customize. I appreciate that lots
of people like the newfangled customize way, but being a programmer, I
really like a programmatic API that I can write in Lisp.)
Anyway, here are the notes:
<http://journals.eyrie.org/eagle/archives/000052.html>
I'll be happy to answer any questions about what I mean.
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
next reply other threads:[~2003-06-10 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 16:08 Russ Allbery [this message]
2003-06-11 16:58 ` spam.el configurations needed (also: Some more bogofilter information) 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=87isrdc3uj.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
/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).