From: Jeremy Maitin-Shepard <jbms@attbi.com>
Subject: Re: spam/ham autolearn (spamassassin) markings in summary
Date: Thu, 18 Dec 2003 11:55:56 -0500 [thread overview]
Message-ID: <87fzfirroj.fsf@jbms.ath.cx> (raw)
In-Reply-To: <sdsmjjs4gf.fsf@wanderer.hardakers.net> (Wes Hardaker's message of "Wed, 17 Dec 2003 10:07:44 -0800")
Wes Hardaker <wes@hardakers.net> writes:
> So, I just wanted to get spamassain working properly and to ensure
> that all the articles it "autolearned" as spam/ham truly were.
[snip]
My approach is to filter (using procmail) spam into a separate (Gnus)
group. Then I ensure that mail is sorted into the correct group by
moving it as appropriate from within Gnus. Finally, I have a cron job
run every other day, which invokes sa-learn on my various spam and ham
nnml group directories. The effect is that mail is properly learned.
--
Jeremy Maitin-Shepard
prev parent reply other threads:[~2003-12-18 16:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 18:07 spam/ham autolearn (spamassassin) markings in summary example Wes Hardaker
2003-12-18 6:57 ` spam/ham autolearn (spamassassin) markings in summary Xavier Maillard
2003-12-23 18:13 ` Ted Zlatanov
2003-12-18 16:41 ` Ted Zlatanov
2003-12-19 18:04 ` Wes Hardaker
2003-12-23 18:17 ` Ted Zlatanov
2003-12-18 16:55 ` Jeremy Maitin-Shepard [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=87fzfirroj.fsf@jbms.ath.cx \
--to=jbms@attbi.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).