From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: spam-check-BBDB bug?/bbdb whitelist split function
Date: Wed, 05 Feb 2003 12:51:45 -0500 [thread overview]
Message-ID: <4nr8amfwem.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <ulm0u3gvn.fsf@axis.com> (Niklas Morberg's message of "Wed, 05 Feb 2003 16:07:56 +0100")
On Wed, 05 Feb 2003, niklas.morberg@axis.com wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> Currently, spam-split will fall through to the next
>> spam/ham check on a whitelist match.
>>
>> I thought of having whitelists return t for a positive ham
>> match, and then spam-split wouldn't examine the rest of the
>> spam/ham checks but simply return nil altogether. Does that
>> makes sense?
>
> Given that I understand you correctly: yes! I get some false
> positives on mail from people who are in my BBDB when I use
> spam-stat.el. If what you are writing means: turn on BBDB
> whitelisting and all mail from everybody in your BBDB will
> be considered ham, then I am all for it.
Well, here's the embarassing thing: this was how things were supposed
to work when Francois Pinard wrote the code, but I didn't pay
attention and made whitelist/BBDB checks fall through to the next
spam-split rule (they returned nil instead of t). So it's all my fault.
> False positives are really really bad because it means I have to
> sift through my spam group looking for valid emails. But you knew
> this already.
I think the new code will fix that, try it (just committed to CVS).
I also added spam-use-{whitelist,BBDB}-exclusive for those who want to
consider all mail from people NOT in the BBDB/whitelist spam.
Ted
next prev parent reply other threads:[~2003-02-05 17:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 4:15 Bill White
2003-02-05 14:47 ` Ted Zlatanov
2003-02-05 14:59 ` Bill White
2003-02-05 17:57 ` Ted Zlatanov
2003-02-05 15:07 ` Niklas Morberg
2003-02-05 17:51 ` Ted Zlatanov [this message]
2003-02-10 8:13 ` spam-stat broken? (was: spam-check-BBDB bug?/bbdb whitelist split function) Niklas Morberg
2003-02-11 8:15 ` spam-stat broken? Niklas Morberg
2003-02-11 17:56 ` Ted Zlatanov
2003-02-11 20:28 ` Ted Zlatanov
2003-02-12 9:49 ` Niklas Morberg
2003-02-12 11:16 ` Ted Zlatanov
2003-02-12 13:44 ` Ted Zlatanov
2003-02-12 13:46 ` Ted Zlatanov
2003-02-12 15:00 ` The agent shows ghost messages (was: spam-stat broken?) Niklas Morberg
2003-02-12 15:48 ` The agent shows ghost messages Ted Zlatanov
2003-02-12 16:29 ` The agent shows ghost messages (was: spam-stat broken?) Kevin Greiner
2003-02-13 7:53 ` The agent shows ghost messages Niklas Morberg
2003-02-13 8:44 ` The agent shows ghost messages (was: spam-stat broken?) Niklas Morberg
2003-02-13 13:50 ` The agent shows ghost messages Kevin Greiner
2003-02-13 14:50 ` Niklas Morberg
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=4nr8amfwem.fsf@lockgroove.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).