Sure,
That's the trick. But I don't like my customers have a lot of verbose
code of it. The already get an subject change with "*SPAM*".
So we have to stop it for a moment.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of
Capt.Stern
Sent: zat
That did the trick! =) Thanks!
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of
Capt.Stern
Sent: Friday, September 06, 2002 3:21 PM
To: [EMAIL PROTECTED]
Subject: Re: [Qmail-scanner-general]Problem after upgrading SpamAssassin
to 2.41
> X-Spam-Status: No
Yup!
Me too. Before Spam Assassin version 2.41. With an early 2.40 CVS
release.
Nobody wants to look at the bug.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of
Paul Fries
Sent: vrijdag 6 september 2002 23:44
To: [EMAIL PROTECTED]
Subject: [Qmail-sca
> X-Spam-Status: No, hits=6.6 required=6.0
>
> Weird. Was working fine with SpamAssassin 2.31.
>
> Has anyone else run into this?
Yeah. I think it's a problem with "spamc -c" in SA 2.40 and above.
Qmail-scanner uses "spamc -c -f" by default. Try removing -c from your
spamc options in qmail-scan
X-Spam-Status: No, hits=6.6 required=6.0
Weird. Was working fine with SpamAssassin 2.31.
Has anyone else run into this?
Regards,
Paul Fries
[EMAIL PROTECTED]
---
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?
I'm in a very strange situation: this is my configuration...
- qmail 1.03 patched with qmailqueue patch, it works alone perfectly;
- spamassasin 2.41 in daemon mode (-d -L -x -u spamc):
=> /etc/mail/spamassassin/local.cf is
--
# Add yo
How about using the site wide procmail settings?
http://us.spamassassin.org/dist/procmailrc.example
We allow users to check for SPAM individually with this in there .qmail:
|condredirect teststaf-spam /usr/bin/grep "^X-Spam-Status: Yes"
Then create a .qmail-spam for the user that either puts i
