From: Paul Johnson <baloo@ursine.ca>
Subject: Re: Automatic SpamAssassin processing
Date: Sun, 30 May 2004 01:07:06 -0700 [thread overview]
Message-ID: <87brk65oet.fsf@ursine.ca> (raw)
In-Reply-To: <87pt8nx1jk.fsf@ursine.ca>
[-- Attachment #1: Type: text/plain, Size: 892 bytes --]
Paul Johnson <baloo@ursine.ca> writes:
> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> On Fri, 28 May 2004, baloo@ursine.ca wrote:
>>
>>> Just want all messages that can be expired run through SpamAssassin
>>> before they're expired.
>>
>> There is no pre-defined functionality in spam.el to handle expiry
>> specifically. If you use the default functionality, you can process
>> spam/ham messages BEFORE they are marked expired with a group spam/ham
>> processor. As to how messages become spam/ham messages - you can both
>> mark them manually and let spam.el handle it for you.
>
> That works well enough. Is there a fairly straightforward tutorial on
> how to do this someplace and I just missed it?
Hmm, I guess I should have said that it sounds good. Could I get an
example on how to do this?
--
Paul Johnson
<baloo@ursine.ca>
Linux. You can find a worse OS, but it costs more.
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2004-05-30 8:07 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
[not found] ` <4nlljbdi13.fsf@lifelogs.com>
[not found] ` <87pt8nx1jk.fsf@ursine.ca>
2004-05-30 8:07 ` Paul Johnson [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=87brk65oet.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).