Re: spamc invocation: move from procmail to Gnus

[deskpot@despammed.com (Vasily Korytov)]

On Sun, 25 Apr 2004 13:32:58 +0200, Jonas Steverud wrote:

>> I.e. it's fetched by fetchmail and other means and put in maildir by
>> procmail, preprocessed by spamassassin. I'm moving my home directory to
>> NFS and the host machine (k6-266/128m/ata) won't be able to easily
>> handle spamassassin. So I want to run spamc on client machines.
>
> I don't quite follow what you try to archive. I'm with you all the way
> up to "run spamc on client machines." Will the client machines run
> fetchmail and procmail?

No, they won't. Mail is put into the maildir by the same machine, that
is an NFS server with limited resources. Client machines are using that
maildir with NFS.

>> I've also looked into spam.el, but found the way, it offers, too
>> complicated, but uneffective. I simply want to have spamassassin scores
>> in message header before it gets delivered to a folder.
>
> It might be so that you are looking at Gnus from the procmail/SA
> angle but need to look at procmail/SA from the Gnus angle.

Maybe. =))

> What does you do with the spam that SA detects? I.e. what does you do
> with mails that has the "X-SPAM: yes" header? Do you score on it or do
> you split such emails to a specific group? Does you use SA's training
> capabilities or just the static rule check?

I use static rule check and splitting on X-Spam headers. But I really
need spamassassin reports in messages (I.e. why is it considered spam
or non-spam.)

> It is nontrivial to use spamassassin from inside Gnus, one way of
> solving this is to decide if you have to use spamassassin or can
> change to some other filter - or wait until SA is integrated.
>
> Can you describe the thoughts behind your decisions why you arrived at
> this solution?

Well... I don't know, it just works for me. =)) So I'd like to adapt
this scheme to changing environment. If this is not trivial, when I
have time, I'll take a closer look and see, what I can do here.

-- 
       I accept RFC3156 and RFC2440-compatible encrypted mail.
PGP key fingerprint: 3273 7F6F 7B87 5DD5 9848 05FB E442 86BC 2E6B 6831