From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: spam.el not saving spam-stat dictionary
Date: 13 Oct 2005 13:49:41 -0400 [thread overview]
Message-ID: <4noe5te28a.fsf@lifelogs.com> (raw)
In-Reply-To: <873bncpz21.fsf@stupidchicken.com> (Chong Yidong's message of "Fri, 07 Oct 2005 21:39:18 -0400")
On 7 Oct 2005, cyd@stupidchicken.com wrote:
> I've been trying to set up the spam-stat spam filtering library, and I
> noticed that the new emails I receive aren't being saved into the
> spam-stat dictionary. From what I gather, emails that I mark as spam
> are supposed to be "taught" to the dictionary as spam, and the rest of
> the email as ham. In practice, ~/.spam-stat.el hasn't changed since I
> first initialized it.
...>
> And spam-log-to-registry defaults to nil. Nothing ever gets pushed
> onto unregister-list, and spam-register-routine is never called!
> Surely this can't be the intended result?
I'll take a look at this. It does look suspicious :) Thanks!
Ted
next prev parent reply other threads:[~2005-10-13 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-08 1:39 Chong Yidong
2005-10-13 17:49 ` Ted Zlatanov [this message]
2006-04-20 18:42 ` 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=4noe5te28a.fsf@lifelogs.com \
--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).