From: Marcelo Toledo <marcelo@marcelotoledo.org>
Subject: ham always being treated as spam (not true)
Date: Wed, 30 Jun 2004 16:17:59 -0300 [thread overview]
Message-ID: <87r7rwkg7s.fsf@kali.intranet> (raw)
I recieved a few ham and for some reason it was treated as spam and went
to spam group, I entered the group marked as read and it goes to
reclassify group, and here are the messages:
marcelo@kali:~/Mail/reclassify$ for i in *; do bogofilter -t < $i; done
N 0.000000
N 0.000000
N 0.000000
N 0.000000
N 0.000000
N 0.000000
N 0.000000
N 0.000000
N 0.000000
N 0.000000
N 0.000000
N 0.000000
N 0.000000
N 0.000000
N 0.000000
N 0.000000
N 0.000000
N 0.000000
N 0.000000
N 0.000000
N 0.000000
N 0.000000
bogofilter says none of the messages are spam, then I enter the
reclassify group and in the summary buffer I hit C-u 22 B r to respool
everything, some times when a new ham appears it goes alright, but
normaly it goes back to spam again. What else besides bogofilter might
be interfering the decision to *be* a spam when bogofilter says it's
not?
thanks,
--
Marcelo Toledo
marcelo@marcelotoledo.org
http://www.marcelotoledo.org
Mobile: 55 71 9141-7181
next reply other threads:[~2004-06-30 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 19:17 Marcelo Toledo [this message]
2004-07-01 8:30 ` Jonas Steverud
2004-07-01 16:15 ` Ted Zlatanov
2004-07-05 13:25 ` Marcelo Toledo
2004-07-08 10:55 ` Marcelo Toledo
2004-07-16 16:57 ` 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=87r7rwkg7s.fsf@kali.intranet \
--to=marcelo@marcelotoledo.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).