Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: spamc invocation: move from procmail to Gnus
Date: Wed, 12 May 2004 12:48:10 -0400	[thread overview]
Message-ID: <4nn04dd22d.fsf@lifelogs.com> (raw)
In-Reply-To: <m2smesmgwl.fsf@c-a75372d5.036-4-67626721.cust.bredbandsbolaget.se> (Jonas Steverud's message of "Sun, 25 Apr 2004 13:32:58 +0200")

On Sun, 25 Apr 2004, tvrud@bredband.net wrote:

> I'm not convinced spam.el can be used to use spamassassin as is but
> need to be extended. This should be possible and definitely
> something some here might help out with - since it is a feature that
> is needed.
> 
> I had one long look at spam filtering in Gnus before selecting which
> backend I should use and I found like you did that spamassassin is
> not perfectly integrated into Gnus (yet) so I decided I should use
> bogofilter instead and I'm quite happy with that result.

I did not write the SA support in spam.el, but I'm wondering what is
missing from it.  Can you or someone else interested in better SA
support explain?

Note there are two ways of using SA, server-based (user just sees
X-Spam-Status) and user-based.  The two are very different, so please
explain what is needed for each one.

Ted



  parent reply	other threads:[~2004-05-12 16:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-24 19:33 Vasily Korytov
2004-04-25 11:32 ` Jonas Steverud
2004-04-25 19:38   ` Vasily Korytov
2004-04-26  7:24     ` Jonas Steverud
2004-04-26 11:15       ` Vasily Korytov
2004-05-12 16:48   ` Ted Zlatanov [this message]
2004-05-13  8:26     ` Jonas Steverud
2004-04-30  0:18 ` Kevin Ryde

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=4nn04dd22d.fsf@lifelogs.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).