Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Spam quation : procmail v spam.el using spamassassin.
Date: Tue, 20 Jun 2006 11:51:24 -0400	[thread overview]
Message-ID: <g69sllz25c3.fsf@CN1374059D0130.kendall.corp.akamai.com> (raw)
In-Reply-To: <87r71lyz64.fsf@mail.europe.de>

On 19 Jun 2006, hadronquark@gmail.com wrote:

> It is a help : if only to calm me down and think more logically -
> sometimes it can all be a bit confusing :( Especially with this new
> default spam process which has replaced spamassassin - it wasnt
> immediately clear to me wither this spam.el was compatible with
> spamassassins x-headers etc etc.

It's meant to be general (with SA support among others), and the
manual tries to explain that.  Did you find the manual section about
spam.el hard to follow?  If so, it would be helpful if you pointed out
problems or gave us suggestions so we can improve it.

> Maybe one last answer (which may or may not be in manuals) : I use
> posting styles to maintain different email folders - is it trivial (before I
> start wasting time trying) to configure spam.el to move the "mark as NOT
> spam" to the correct procmail populated maildirs in gnus?

[ ham == NOT spam ]

You can move ham articles automatically out of spam groups.  You need
to classify that group as a spam group with `G c' and the rest is
automatic.

There can be multiple ham destinations per group.  When you exit the
group, ham messages will be copied or moved to the ham destinations
(moved to the last one and copied to all the others) and processed
with the ham processors you've defined (none by default).

You can also define a ham destination of nil (leave in place) or
'respool (send back to the split-fancy process).  All of this can be
customized with `G c'.

Ted

  reply	other threads:[~2006-06-20 15:51 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
2006-06-19 14:53   ` Hadron Quark
2006-06-20 15:51     ` Ted Zlatanov [this message]
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=g69sllz25c3.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).