From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: bogofilter documentation
Date: Wed, 11 Jun 2003 12:36:55 -0400 [thread overview]
Message-ID: <4nbrx4sh94.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <m3smqg2228.fsf@merlin.emma.line.org> (Matthias Andree's message of "Wed, 11 Jun 2003 15:09:35 +0200")
On Wed, 11 Jun 2003, ma@dt.e-technik.uni-dortmund.de wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> Are you or someone else using Bogofilter interested in not only
>> fixing the docs, but adding code to use that threshold?
>> Alternatively, let me know the flag and I'll try to get it done. I
>> couldn't find the relevant info in the URL you mention above,
>> sorry.
>
> I just wanted to point out that the hint that the spam cutoff were
> compiled-in is no longer true.
The manual is fixed. If you or other Bogofilter users have features
you want in spam.el in the future, let me know and I'll do my best to
help implement them.
Thanks
Ted
prev parent reply other threads:[~2003-06-11 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 10:20 Matthias Andree
2003-06-10 15:03 ` Ted Zlatanov
2003-06-11 13:09 ` Matthias Andree
2003-06-11 16:36 ` Ted Zlatanov [this message]
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=4nbrx4sh94.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
/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).