From: deskpot@despammed.com (Vasily Korytov)
Subject: Re: spamc invocation: move from procmail to Gnus
Date: Mon, 26 Apr 2004 15:15:35 +0400 [thread overview]
Message-ID: <87fzardm7c.fsf@unix.home.local> (raw)
In-Reply-To: <m2u0z7kxqp.fsf@c-a75372d5.036-4-67626721.cust.bredbandsbolaget.se>
On Mon, 26 Apr 2004 09:24:30 +0200, Jonas Steverud wrote:
> I'm sorry, but I don't think I can help with this setup. I found
> during my investigations that is was nontrivial - even very hard IMHO
> - to get Gnus to call Spamassassin and gave up. If you can consider
> switching to bogofilter it becomes trivial to use. The downside is
> that you won't know what triggered the spam level (although I think
> that bogofilter could tell you that if you feed it a false positive
> manually, but I haven't checked the docs).
Using spamassassin from spam.el gives this results too. I consider this
nothing but awkward. =(( Maybe, it's really not from the Gnus angle (not
procmail and SA's), but I don't understand that yet.
Another solution is to write `spamc -c` output to some other file, and
retrieve it as needed. But also a hack to SA is needed: current output
it too trimmed down. I'll think of it.
> One solution that you probably already have thought of is to have
> spamd run on a more resourceful server and have the mail server run
> spamc, if spamc can work across a network and the mail server is not
> that limited, which I guess it is.
I've already thought of it. Unfortunately, there're no other full-time
on machines in this subnet. =((
Thanks.
--
I accept RFC3156 and RFC2440-compatible encrypted mail.
PGP key fingerprint: 3273 7F6F 7B87 5DD5 9848 05FB E442 86BC 2E6B 6831
next prev parent reply other threads:[~2004-04-26 11:15 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 [this message]
2004-05-12 16:48 ` Ted Zlatanov
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=87fzardm7c.fsf@unix.home.local \
--to=deskpot@despammed.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).