From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: `S t' always returns nil
Date: Mon, 27 Jan 2003 12:50:52 -0500 [thread overview]
Message-ID: <4nd6micwhv.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <87d6mjsz41.fsf@splinter.inka.de> (Christopher Splinter's message of "Sun, 26 Jan 2003 16:35:26 +0100")
On Sun, 26 Jan 2003, chris@splinter.inka.de wrote:
> Hi,
>
> I think there is something wrong with `S t' as it always
> returns a spamicity of 0, even if the concerned mail is clearly
> spam and is recognized as such by bogofilter, too.
>
> I use the most recent version of bogofilter from CVS, which
> returns lines like this:
>
>| X-Bogosity: Spam, tests=bogofilter, spamicity=0.9056373309,
>| version=0.10.1.1.cvs.20030125
>
> The variables which are related to bogofilter are set properly.
Hmm, the version I used for testing had lines like this:
X-Bogosity: Yes, tests=bogofilter, spamicity=0.567040, version=0.9.1.2
so I wrote spam-check-bogofilter-headers to look for "X-Bogosity: Yes"
headers, see below.
(defun spam-check-bogofilter-headers (&optional score)
(let ((header (message-fetch-field spam-bogofilter-header)))
(when (and header
(string-match "^Yes" header))
(if score
(when (string-match "spamicity=\\([0-9.]+\\)" header)
(match-string 1 header))
spam-split-group))))
Fixing this is trivial, but should I match on something else, or
should I allow both ^Yes and ^Spam as valid spam indicators in the
header?
Thanks
Ted
next prev parent reply other threads:[~2003-01-27 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-26 15:35 Christopher Splinter
2003-01-27 17:50 ` Ted Zlatanov [this message]
2003-01-27 19:01 ` Christopher Splinter
2003-01-27 20:17 ` Ted Zlatanov
2003-01-28 15:13 ` Christopher Splinter
2003-01-28 16:46 ` 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=4nd6micwhv.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).