Many thanks for that, Bowie.
--
Dave Stiles
On 28/09/16 15:31, Axb wrote:
You are awake that it's not really polite to hijack a thread with
something totally unrelated?
It was relevant. I was trying to compare my system to the OP's.
--
Dave Stiles
On 09/28/2016 04:26 PM, SA wrote:
I've tried to run "spamassassin -D --lint" several times over the past
few years but never successfully. It always over-spills Terminal and all
attempts to pipe it to file or to more / less fail. Is there ANY way to
get a sensible listing fr
On 9/28/2016 10:26 AM, SA wrote:
I've tried to run "spamassassin -D --lint" several times over the past
few years but never successfully. It always over-spills Terminal and
all attempts to pipe it to file or to more / less fail. Is there ANY
way to get a sensible listing fr
I've tried to run "spamassassin -D --lint" several times over the past
few years but never successfully. It always over-spills Terminal and all
attempts to pipe it to file or to more / less fail. Is there ANY way to
get a sensible listing from this command, please? I'
On 28 Sep 2016, at 1:58, Luciano Rinetti wrote:
When i run the "spamassassin -D --lint" i get the message:
Sep 28 07:45:57.329 [13116] dbg: config: warning: score set for
non-existent rule "rulenames"
where rulenames are:
RCVD_IN_MSPIKE_H4
RCVD_IN_MSPIKE_WL
FREEMA
On Wed, 28 Sep 2016, Luciano Rinetti wrote:
When i run the "spamassassin -D --lint" i get the message:
Sep 28 07:45:57.329 [13116] dbg: config: warning: score set for non-existent rule
"rulenames"
where rulenames are:
RCVD_IN_MSPIKE_H4
RCVD_IN_MSPIKE_WL
FREEMA
When i run the "spamassassin -D --lint" i get
the message:
Sep 28 07:45:57.329 [13116] dbg: config: warning: score set for
non-existent rule "rulenames"
where rulenames are:
RCVD_IN_MSPIKE_H4
RCVD_IN_MSPIKE_WL
FREEMA
On Tue, Jan 23, 2007 at 05:00:35PM +0100, Florent Gilain wrote:
> If i have good understood all the manual/wiki i actually read, the
> "spamassassin -D --lint" command is used to test SA configuration before
> reloading it ?
--lint is, yes. People often run with -D so the
If i have good understood all the manual/wiki i actually read, the
"spamassassin -D --lint" command is used to test SA configuration before
reloading it ?
My problem is that it seems to give me errors...but i'm unable to resolve
it.
Yesterday, i upgraded my SA 3.0.4 to 3.1.7 an
On Mon, 9 Oct 2006, Email Lists wrote:
>
> When running
>
> spamassassin -D --lint > spamconfdebug.txt 2>&1
>
> what obvious things will jump out at someone if there is a problem?
>
> There is quite a bit of output stuff to go through regardless and im
> wond
When running
spamassassin -D --lint > spamconfdebug.txt 2>&1
what obvious things will jump out at someone if there is a problem?
There is quite a bit of output stuff to go through regardless and im
wondering if there are any standard texts we should grep for in the
outputfile
Tha
Leonard SA wrote:
> Hello,
>
> Thats the funny thing.. i dont have any spaces.. but since i went into
> v310.pre .. i dont get the errors anymore and the test is now error free ..
>
> Thanks..
>
> BTW .. how can i check to see if DCC and razor are working?
You can run a spamassassin --lint -D..
OTECTED]>
To: "Leonard SA" <[EMAIL PROTECTED]>
Cc:
Sent: Tuesday, November 29, 2005 4:05 PM
Subject: Re: spamassassin --D lint failing?
Leonard SA wrote:
Hello List ..
For some odd reason everytime I restart spamd or run spamassassin --D
lint ; I get some odd parse errors.
Leonard SA wrote:
> Hello List ..
>
> For some odd reason everytime I restart spamd or run spamassassin --D
> lint ; I get some odd parse errors.
>
> ###
> [25084] warn: config: failed to parse, now a plugin, skipping:
> ok_languages_all
> [25084] wa
Hello List ..
For some odd reason everytime I restart spamd or run spamassassin --D lint
; I get some odd parse errors.
###
[25084] warn: config: failed to parse, now a plugin, skipping:
ok_languages_all
[25084] warn: config: failed to parse line, skipping: use_dcc_1
[25084
--lint question
> One of the things I have found says to run
> spamassassin -D --lint when adding new rule sets.
Unless it is the first time for the installation or things have gone
very wacky, simply --lint is sufficient when adding a new rule set most
all the time. If you have put it
> One of the things I have found says to run
> spamassassin -D --lint when adding new rule sets.
Unless it is the first time for the installation or things have gone very
wacky, simply --lint is sufficient when adding a new rule set most all the
time. If you have put it in the right plac
the things I have found says to run
spamassassin -D --lint when adding new rule sets.
Really, I'd run spamassassin --lint. It should run and exit quitely. I'd
only bother with -D --lint when things get strange.
That said, all looks fine in that output..
You might consider setting
I have just reinstalled SA on a new server with more processor and more
memory that the "test" system I started out with that ended up in
production. I am looking at adding some additional rules as I get more
experience with this. One of the things I have found says to run
spamassassin
At 03:57 PM 9/27/2004, scohen wrote:
When I run spamassassin -D --lint I am noticing this message:
"config: SpamAssassin failed to parse line, skipping: rewrite_subject 0
Argument "" isn't numeric in addition (+) at
/usr/lib/perl5/site_perl/5.6.1/Mail/SpamAssassin/Con
Quoting scohen <[EMAIL PROTECTED]>:
When I run spamassassin -D --lint I am noticing this message:
"config: SpamAssassin failed to parse line, skipping: rewrite_subject 0
Argument "" isn't numeric in addition (+) at
/usr/lib/perl5/site_perl/5.6.1/Mail/SpamAssass
When I run spamassassin -D --lint I am noticing this message:
"config: SpamAssassin failed to parse line, skipping: rewrite_subject 0
Argument "" isn't numeric in addition (+) at
/usr/lib/perl5/site_perl/5.6.1/Mail/SpamAssassin/Conf/Parser.pm line 572."
Spamassasin stil
23 matches
Mail list logo
