On 7/31/2014 7:29 PM, Karsten Bräckelmann wrote:
Moreover, it is important to note that this debug warning was
introduced in 3.4. In particular, since the OP is running 3.3.x. ;)
And you didn't beat him up for running an outdated version? For shame!
Regards,
KAM
We are running spam assassin 3.3.1 with Postfix. So I have added some rules to
mark as spam yolasite, wix, etc…. as we have been getting besieged by them.
My thing is these rules seem not to be loading. When I do a spamassassin —lint
I don’t get any errors. When I do spamassassin —lint -D
On 7/31/2014 3:59 PM, Chris Brandstetter wrote:
We are running spam assassin 3.3.1 with Postfix. So I have added some
rules to mark as spam yolasite, wix, etc…. as we have been getting
besieged by them. My thing is these rules seem not to be loading.
When I do a spamassassin —lint I don’t
If showed it being loaded Jul 31 15:43:07.794 [20903] dbg: config: read file
/etc/mail/spamassassin/local.cf” Is there any way to list what rules are being
loaded? Like a list all available rules type of thing?
Chris Brandstetter
System Administrator
Nebraska Wesleyan University
Office
On Thu, 2014-07-31 at 21:08 +, Chris Brandstetter wrote:
If showed it being loaded Jul 31 15:43:07.794 [20903] dbg: config:
read file /etc/mail/spamassassin/local.cf” Is there any way to list
what rules are being loaded? Like a list all available rules type of
thing?
No, but you can
On 7/31/2014 5:08 PM, Chris Brandstetter wrote:
If showed it being loaded Jul 31 15:43:07.794 [20903] dbg: config:
read file /etc/mail/spamassassin/local.cf” Is there any way to list
what rules are being loaded? Like a list all available rules type of
thing?
Not that I'm aware of, no. Put
On Thu, 2014-07-31 at 19:59 +, Chris Brandstetter wrote:
body NWU_YOLASITE /yolasite\.com/i
This (and the other similar ones) really should better be a uri rule.
And this particular one be merged with the almost duplicating uri rule
just 20 lines below.
# Yolasite URI rule
uri
On Thu, 2014-07-31 at 17:34 -0400, Kevin A. McGrail wrote:
Put it in a different CF and comment out a description and look for an
error that a description is missing.
A missing description is not an error, not even a lint warning.
--
char
On 7/31/2014 5:41 PM, Karsten Bräckelmann wrote:
On Thu, 2014-07-31 at 17:34 -0400, Kevin A. McGrail wrote:
Put it in a different CF and comment out a description and look for an
error that a description is missing.
A missing description is not an error, not even a lint warning.
Yes, it is
On Thu, 2014-07-31 at 19:02 -0400, Kevin A. McGrail wrote:
On 7/31/2014 5:41 PM, Karsten Bräckelmann wrote:
A missing description is not an error, not even a lint warning.
Yes, it is a warning (though in my defense I was using error
generically.
Hah, that's actually news to me!
However,
On Fri, 2008-10-03 at 20:36 +0200, [EMAIL PROTECTED] wrote:
Hello,
I have done an upgrade with perl -MCPAN -e shell and then i recognized, that
spamassassin will not run.
He said:
spam_scan FAILED: Can't locate object method get_tag via package
Mail::SpamAssassin::PerMsgStatus at
Hello,
I have done an upgrade with perl -MCPAN -e shell and then i recognized, that
spamassassin will not run.
He said:
spam_scan FAILED: Can't locate object method get_tag via package
Mail::SpamAssassin::PerMsgStatus at (eval 87) line 335, GEN53 line 64.
I got the annouce, that i should
Hey folks. I'm seeing a fair bit of spam getting through with embedded
GIF images, a slightly redacted version being pasted into the bottom of
this email. I'm trying to write a rule to catch embedded GIFs, but it
just doesn't seem to work. I've tried the following:
full
13 matches
Mail list logo
