From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: spam-split with bogofilter
Date: Fri, 21 Mar 2003 13:44:59 -0500 [thread overview]
Message-ID: <4n7kastv84.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <ubs059lxh.fsf@riic.at> (Stefan =?iso-8859-1?q?Reich=F6r's?= message of "Fri, 21 Mar 2003 09:13:46 +0100")
On Fri, 21 Mar 2003, xsteve@riic.at wrote:
> On Fri, 21 Mar 2003, Karl Eichwalder stated:
>
>> Ted Zlatanov <tzz@lifelogs.com> writes:
>>
>> Thanks for your help! This morning, with a sudden, it starts
>> working. Strange. But now it's to overzealous ;) All mail did end
>> in the spam box.
>>
>> There is/was also an additional problem: "~/Mail/nnml:spambox"
>> (Gnus name: "nnml:nnml:spambox") was used instead of
>> "~/Mail/spambox".
>>
>> But this was a good message -- obviously, bogofilter needs more
>> training...
>>
>> I must reread the docs.
>
> I had the same problem when I started using spam-stat. I solved it
> the following way: I entered the spam group I displayed the whole
> ham article with: C-u g I switched to the article buffer and typed:
> M-: (spam-stat-buffer-is-non-spam) At last I respooled the article
> (B r)
>
> Is there already an automated way for doing this?
It should be automatic when you quit a group summary with
gnus-group-ham-exit-processor-bogofilter enabled for that group. That
processes the ham with bogofilter. You can also set the
ham-process-destination parameter if you want the processed ham to go
to another group after registration.
Ted
prev parent reply other threads:[~2003-03-21 18:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 19:02 Karl Eichwalder
2003-03-20 21:28 ` Ted Zlatanov
2003-03-21 6:23 ` Karl Eichwalder
2003-03-21 8:13 ` Stefan Reichör
2003-03-21 17:25 ` Karl Eichwalder
2003-03-21 18:49 ` Ted Zlatanov
2003-03-21 19:28 ` Karl Eichwalder
2003-03-21 20:35 ` Ted Zlatanov
2003-03-22 18:40 ` Karl Eichwalder
2003-03-23 23:08 ` Ted Zlatanov
2003-03-21 18:44 ` 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=4n7kastv84.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).