Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Paul Johnson <baloo@ursine.ca>
Subject: Re: Automatic SpamAssassin processing
Date: Fri, 28 May 2004 10:41:55 -0700	[thread overview]
Message-ID: <87fz9k8n4s.fsf@ursine.ca> (raw)
In-Reply-To: <4nlljceep0.fsf@lifelogs.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Thu, 27 May 2004, baloo@ursine.ca wrote:
>
>> Is there any way to set up Gnus to automatically process groups as
>> ham or spam before it expires messages?
>
> Look at the spam.el documentation in the Gnus manual.
>
> The basic answer is yes, with some cautions.  If you explain how you
> want mail to flow from incoming to spam/ham groups to spam/ham
> training, that would be helpful.

I'm not interested in using gnus to split my mail, procmail already
does that for me.  Just want all messages that can be expired run
through SpamAssassin before they're expired.

- -- 
Paul Johnson
<baloo@ursine.ca>
Linux.  You can find a worse OS, but it costs more.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAt3nlUzgNqloQMwcRAjrDAJ4xJqn9f7r/iurZkoh6oAZwmfT5SQCcDf1Z
Ubb37fDWwJepJh29DN40/7E=
=EtsK
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2004-05-28 17:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3wu31ae64.fsf@eric.rossnet.com>
     [not found] ` <87y8nh7g8u.fsf@uhoreg.ca>
2004-05-28  3:13   ` Paul Johnson
     [not found]     ` <4nlljceep0.fsf@lifelogs.com>
2004-05-28 17:41       ` Paul Johnson [this message]
     [not found]         ` <4nlljbdi13.fsf@lifelogs.com>
     [not found]           ` <87pt8nx1jk.fsf@ursine.ca>
2004-05-30  8:07             ` Paul Johnson

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=87fz9k8n4s.fsf@ursine.ca \
    --to=baloo@ursine.ca \
    /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).