From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Spam quation : procmail v spam.el using spamassassin.
Date: Mon, 19 Jun 2006 10:47:33 -0400 [thread overview]
Message-ID: <g697j3d6w3e.fsf@CN1374059D0130.kendall.corp.akamai.com> (raw)
In-Reply-To: <874pyhftqu.fsf@gmail.com>
On 19 Jun 2006, hadronquark@gmail.com wrote:
> Since procmail settings are causing my mail to be "split" into spam
> folders (nnmaildir) after processing by spamassassin, would the split
> functons in spam.el have any purpose?
Sure. You could apply additional filters to the SA run.
> I'm really going around in circles trying to figure out the best way of
> configuring spamassassin with procmail and then gnus. Any help greatly
> appreciated.
The delivery for that setup should be:
incoming mail
to
procmail
to
SA
to
nnmaildir
to
spam.el (if you want) for extra splitting
Then the read cycle would be
1)
enter SPAM group
(all unread messages are spam by default)
mark any messages as ham
exit SPAM group
(spam and ham processing and destinations are applied here)
2)
enter non-SPAM group
(same as above, except unread messages are not spam by default, so you
mark messages as spam manually)
So the setup consists of:
a) set up SPAM and non-SPAM groups (this is done with `G c' or `G p'
or gnus-parameters)
b) set up spam and ham processing (these are functions to be run on
spam and ham, e.g. sa-learn for SA), if wanted
c) set up spam and ham destinations (for spam/ham messages on group
exit), if wanted
I personally prefer destinations to processing, because I have a slow
IMAP server so it's faster to move messages and then batch-process
them, but it's up to you.
I hope that helps. More introductory information can be found at
http://lifelogs.com/spam and in the Gnus manual.
Ted
next prev parent reply other threads:[~2006-06-19 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 8:13 Hadron Quark
2006-06-19 14:47 ` Ted Zlatanov [this message]
2006-06-19 14:53 ` Hadron Quark
2006-06-20 15:51 ` Ted Zlatanov
2006-06-21 13:16 ` Hadron Quark
2006-06-21 19:43 ` Ted Zlatanov
2006-06-21 20:33 ` Hadron Quark
2006-06-22 15:27 ` Ted Zlatanov
2006-07-01 12:17 ` Leandro su janni
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=g697j3d6w3e.fsf@CN1374059D0130.kendall.corp.akamai.com \
--to=tzz@lifelogs.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).