x27;t.
Still ongoing as of a few minutes ago. If you want full output, let
me know.
If there's a way to force sa-compile to use gcc or something, that
would also be useful to know.
Not sure if this is a purely historical point, but for a long while it
was necessary to compile any compiled
On Fri, 10 Feb 2023, Kevin A. McGrail wrote:
Does this still occur after a change I made yesterday? I had a regex that
some versions of perl handle and others didn't.
Still ongoing as of a few minutes ago. If you want full output, let me
know.
If there's a way to force sa-comp
ation and credential theft.
Hey there all.
We're only using two real rulesets: core and kam.cf
Our nightly sa-update/sa-compile run is throwing warnings like the
following. So, these are only warnings, and the compile continues,
but they're making my cron jobs noisy.
The questions
Dan Mahoney (Gushi) skrev den 2023-02-10 06:10:
2) Is it worth filing a bug?
in spamassassin terms its more likely just that it miss to depricate
5.32 perl version, in gentoo we have perl 5.36 now without any issues
please if its just that filling a bug in spamassassassin and on freebsd
po
On 10 Feb 2023, at 13:28, Matt Anton via users wrote:
According to a thread on FreeBSD’s forums[1] and perl GitHub’s own
tracker[2], perl is currently not friendly with clang-11 and above
which was introduced on ≥12.2 and ≥13.1.
Err, I meant "not friendly with clang-13"...
--
matt [at] lv223
On 10 Feb 2023, at 6:10, Dan Mahoney (Gushi) wrote:
> Hey there all.
Hello Dan,
> We're only using two real rulesets: core and kam.cf
>
> Our nightly sa-update/sa-compile run is throwing warnings like the following.
> So, these are only warnings, and the compile continues
On 2/10/23 06:10, Dan Mahoney (Gushi) wrote:
Hey there all.
Hello.
1) Are these known issues.
Not sure, but I have the same problem.
2) Is it worth filing a bug?
I guess so, but I'm not sure if this is something worth reporting here;
maybe to FreeBSD.
I've been wanting to look into th
Hey there all.
We're only using two real rulesets: core and kam.cf
Our nightly sa-update/sa-compile run is throwing warnings like the
following. So, these are only warnings, and the compile continues, but
they're making my cron jobs noisy.
The questions:
1) Are these known issu
Hi everybody...
i have noticed a huge difference in compiling time between SA 3.4.2 and 3.4.4
(3.4.4 is much much faster)but i have not seen anything in the "what_is_new
docs" about it...
make it sense??
Thanks...
---Pedreter
On 2020-05-28 15:32, Bert Van de Poel wrote:
Almost all of the email we process are forwarders. It doesn't really
make sense for us to do a non-global bayes db. The large majority of
email we process is also for a uniform group: student organizations at
our local university.
On 28.05.20 21:05,
amavis user's .spamassassin folder and removed the path from
local.cf and it seems to work just fine and indeed solves our issue with
sa-compile. Thank you very much for the suggestion. This is a much
cleaner solution than what I had initially in mind!
On 28/05/2020 17:03, Matus UHLAR - fan
On 2020-05-28 15:32, Bert Van de Poel wrote:
Almost all of the email we process are forwarders. It doesn't really
make sense for us to do a non-global bayes db. The large majority of
email we process is also for a uniform group: student organizations at
our local university.
does not matter if
On 2020-05-28 15:22, Matus UHLAR - fantomas wrote:
On 28.05.20 13:38, Bert Van de Poel wrote:
We're using a global bayes_path defined in local.cf:
This is your problem imho.
if you use amavis, you need no bayes database, but amavis users',
i guess in /var/lib/amavis/.spamassassin/
if amavis
On 2020-05-28 10:18, Matus UHLAR - fantomas wrote:
I wonder where did these files come from.
did you sety bayes_path in /etc/spamassassin/ ?
setup userprefs file for amavisd, in this file make sure bayes data keep
in amavisd user, not the spamassasin user where there is no write access
hop
we noticed our daily
cronjob running sa-update and sa-compile was giving us an
error concerning permissions:
May 25 00:31:25.488 [8381] warn: bayes: cannot write to
/var/lib/spamassassin/bayes_db/bayes_journal, bayes db update
ignored: Permission denied
bayes: cannot write to
/var/lib/spamassassin
t confusing is that we noticed our daily cronjob
running sa-update and sa-compile was giving us an error concerning
permissions:
May 25 00:31:25.488 [8381] warn: bayes: cannot write to
/var/lib/spamassassin/bayes_db/bayes_journal, bayes db update
ignored: Permission denied
bayes: cannot write to
omewhat confusing is that we noticed our daily cronjob
running sa-update and sa-compile was giving us an error concerning
permissions:
May 25 00:31:25.488 [8381] warn: bayes: cannot write to
/var/lib/spamassassin/bayes_db/bayes_journal, bayes db update
ignored: Permission denied
bayes:
evaluating the amount of false positives (and
contacting users who seem to have broken cronjobs that confuse bayes)
before taking away the artificial scores. We wanted to clear up our
sa-compile cronjob error.
On 28/05/2020 10:18, Matus UHLAR - fantomas wrote:
On 25.05.20 23:34, Bert Van de
at was somewhat confusing is that we noticed our daily cronjob
running sa-update and sa-compile was giving us an error concerning
permissions:
May 25 00:31:25.488 [8381] warn: bayes: cannot write to
/var/lib/spamassassin/bayes_db/bayes_journal, bayes db update ignored:
Permission denied
bayes: cannot wr
this?
On 26/05/2020 00:45, RW wrote:
On Mon, 25 May 2020 23:34:27 +0200
Bert Van de Poel wrote:
My question therefore specifically is: what exactly does sa-compile
do to the bayes database files?
I don't know for sure, but it's probably just a side-effect of
initializing plugins
On Mon, 25 May 2020 23:34:27 +0200
Bert Van de Poel wrote:
> My question therefore specifically is: what exactly does sa-compile
> do to the bayes database files?
I don't know for sure, but it's probably just a side-effect of
initializing plugins. Possibly it's
ewhat confusing is that we noticed our daily cronjob running
sa-update and sa-compile was giving us an error concerning permissions:
May 25 00:31:25.488 [8381] warn: bayes: cannot write to
/var/lib/spamassassin/bayes_db/bayes_journal, bayes db update ignored:
Permission denied
bayes: cannot wr
An RH bug was opened and closed on this in 2014:
https://bugzilla.redhat.com/show_bug.cgi?id=1151565
I attached a patch to the bug for the latest sa-update.cron script from
the 3.4.2 RPM to invoke sa-compile if the plugin is enabled and re2c is
installed.
I'm experimenting with the Rule2XSBody plugin and I've figured out that I
have to run sa-compile after sa-update to create the compiled versions of
local rules. I don't see anything in either sa-update or the Red
Hat-supplied sa-update.cronscript invoked from cron (or a syste
An: users@spamassassin.apache.org
Betreff: Re: sa-compile Error invalid pointer
Hi,
it may be worth to run a memtest on your system.
Daniele
On 28/09/2018 12:25, Ronny Wagner wrote:
> Hello Community,
>
> since few days i have a problem with spamassassin.
> I can't start the
a-compile.cache/rules.body_0 and rules.body_neg100.
Then i tested again and there a no fail, i don´t now why.
Best regards
Ronny
-Ursprüngliche Nachricht-
Von: Kevin A. McGrail
Gesendet: Freitag, 28. September 2018 13:44
An: Ronny Wagner ; users@spamassassin.apache.org
Betreff: Re: sa-compil
04001" the service come up.
I download a test channel (/usr/bin/sa-update --nogpg --channel
spamassassin.heinlein-support.de) and use /usr/bin/sa-compile, i see a fail
message.
Do anyone know why?
Thank you for your help.
spamassassin:
Installed: 3.4.1-6+deb9u1
perl:
Installed:
download a test channel (/usr/bin/sa-update --nogpg --channel
> spamassassin.heinlein-support.de) and use /usr/bin/sa-compile, i see a fail
> message.
>
> Do anyone know why?
>
Does the channel you downloaded pass lint? spamassassin --lint ?
sassin.heinlein-support.de) and use /usr/bin/sa-compile, i see a fail
message.
Do anyone know why?
Thank you for your help.
spamassassin:
Installed: 3.4.1-6+deb9u1
perl:
Installed: 5.24.1-3+deb9u4
libc6:
Installed: 2.24-11+deb9u3
Debian 4.9.0-5-686-pae
Fail Message:
Sep 28 12:18:13.6
> PERL_MM_OPT="INSTALL_BASE=/root/perl5";
> export PERL5LIB="/root/perl5/lib/perl5:$PERL5LIB";
> export PATH="/root/perl5/bin:$PATH";
>
> Workaround:
>
> PERL_MM_OPT='' sa-compile
>
> Cheers,
>
> Phil
>
work perfect , thank
--
rickygm
http://gnuforever.homelinux.com
IB="/root/perl5/lib/perl5:$PERL5LIB";
export PATH="/root/perl5/bin:$PATH";
Workaround:
PERL_MM_OPT='' sa-compile
Cheers,
Phil
-Original Message-
From: Ricky Gutierrez [mailto:xserverli...@gmail.com]
Sent: 24 August 2017 23:47
To: users@spamassassin.apache.org
S
2017-08-24 17:55 GMT-06:00 John Hardin :
> On Thu, 24 Aug 2017, Ricky Gutierrez wrote:
>
>> spamassassin-3.4.1-14.el7.centos.x86_64
>
>
> Where did you get that?
>
> The official Centos 7 version (as far as I can tell) is 3.4.0-2 and the
> latest available via FC is 3.4.1-12 from FC26.
>
> I don't
On Thu, 24 Aug 2017, Ricky Gutierrez wrote:
spamassassin-3.4.1-14.el7.centos.x86_64
Where did you get that?
The official Centos 7 version (as far as I can tell) is 3.4.0-2 and the
latest available via FC is 3.4.1-12 from FC26.
I don't have a RedHat account, but I expect Centos would pretty
hi list , I have some problems compiling spamassassin 3.4.1
[root@scm ~]# sa-compile
Aug 24 22:30:40.694 [4709] info: generic: base extraction starting.
this can take a while...
Aug 24 22:30:40.695 [4709] info: generic: extracting from rules of type body_0
100
t need to remove anything.
> >
> > The stock rules aren't stored there anyway, it's just local rules.
>
> Ahh, I think perhaps I'm misunderstanding this (from the man page):
>
> "sa-compile uses re2c to compile the site-wide parts of the
> SpamAssass
ay, it's just local rules.
Ahh, I think perhaps I'm misunderstanding this (from the man page):
"sa-compile uses re2c to compile the site-wide parts of the SpamAssassin
ruleset. No part of user_prefs or any files included from user_prefs can
be built into the compiled set"
I
On Sat, 17 Jun 2017 13:48:32 +0100
Peter Smith wrote:
> Hello list,
>
> I'm playing around with sa-compile in an attempt to improve
> performance, but I have a couple of questions that I can't find
> answered in the online docs.
>
> 1) After compiling, my compi
Hello list,
I'm playing around with sa-compile in an attempt to improve performance,
but I have a couple of questions that I can't find answered in the online
docs.
1) After compiling, my compiled ruleset is stored in
/var/lib/spamassassin/compiled/5.014/3.004001. Do I now need to
On 20.04.17 17:07, Bill Cole wrote:
ls -ld /usr/bin/X11
lrwxrwxrwx 1 root root 1 Mar 11 2007 /usr/bin/X11 -> .
That's a weird Ubuntu (or Debian?) quirk. It shouldn't be necessary
but it probably shouldn't be fiddled with either, except maybe to
'chmod -h o-w /usr/bin/X11' (to remove the worl
No I don't. I have not used Gentoo and am not on that mailing list.. I
hope my questions do not appear too newbie, since I've been running Unix
systems for a long time, although this particular one had me stumped.
Thelma is the name of one of my servers, another is Louise. That
location has ser
On 2017-04-20 17:31, Robert Steinmetz AIA wrote:
> >>> thelma@thelma:~$ echo $PATH
BTW, do you have any connection to the Thelma who's asking a constant
stream of close-to-newbie questions in the Gentoo user mailing list?
It's not that common a name, so forgive me for the short-circuit in my
bra
Thank you Bill,
I checked all of the permissions at every level, they were all 755
except for as noted, which I changed. to 755
It works now.
I'll re-check this in the morning and run security scans to make sure
everything is tied down..
I appreciate your help.
Bill Cole wrote:
On 20 Apr
On Thu, 2017-04-20 at 17:07 -0400, Bill Cole wrote:
If your distro has an rkhunter package available, then I'd recommend
that you install it. Once you're happy that your system clean, do its
initial update "rkhunter --propupt" and thereafter make sure its run as
a daily cronjob. This way you shoul
On 20 Apr 2017, at 16:16, Robert Steinmetz AIA wrote:
Thank you Bill,
That has given me a clue. I ran the commands below:
thelma@thelma:~$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games:/usr/local/games:/snap/bin
thelma@thelma:~$ ls -ld /usr/l
issue, but as Bill Cole helpfully
wrote:
The sa-compile script DOES use a SA utility
function to untaint the whole %ENV hash, but there's a special
catch for $ENV{'PATH'}: if any directories included are not
absolute (e.g. commonly '.' and '~/
th
"PATH" is "$ENV{'PATH'}". The %ENV hash is considered "tainted" as
untrustworthy input by perl, so if the interpreter is run with the
"-T" option, any subprocess launched by perl won't get any environment
variables unless the script ha
he
system doesn't use the mode of a symlink itself.
What I expect is happening is that there's a problematic directory in
the $PATH that perl gets when executed, so the blind untainting of
$ENV{'PATH'} that sa-compile does won't work. The best fix is to find
the insecure member of $PATH and remove it before trying to run
sa-compile.
Title: Signature
Robert Steinmetz wrote:
Responding to my own post with new information.
I think I've confirmed that the problem is the $PATH, or the perl
equivalent.
I added the full path name where the specific commands were called
and that removed
Ian Zimmerman wrote:
On 2017-04-18 10:17, Robert Steinmetz wrote:
tty is in /usr/bin
But it is stty, not tty, which fails to be found. And stty is
(normally) in /bin. So it looks a lot like /bin (and probably /sbin) is
missing from the PATH.
Yes thanks stty is in /bin
This could be re
On 2017-04-18 10:17, Robert Steinmetz wrote:
> tty is in /usr/bin
But it is stty, not tty, which fails to be found. And stty is
(normally) in /bin. So it looks a lot like /bin (and probably /sbin) is
missing from the PATH.
This could be related to the long-advertised switch to a unified /u
Title: Signature
RW wrote:
On Mon, 17 Apr 2017 16:37:35 -0400
Robert Steinmetz wrote:
I upgrades my working Ubuntu 14.04 LTS to 16.04 LTS SpamAssassin
version 3.4.1.
Something happened during the upgrade and I ma now unable to get
sa-compile to
On Mon, 17 Apr 2017 16:37:35 -0400
Robert Steinmetz wrote:
> I upgrades my working Ubuntu 14.04 LTS to 16.04 LTS SpamAssassin
> version 3.4.1.
> Something happened during the upgrade and I ma now unable to get
> sa-compile to configure properly.
>
> Here is the message
I upgrades my working Ubuntu 14.04 LTS to 16.04 LTS SpamAssassin version
3.4.1.
Something happened during the upgrade and I ma now unable to get
sa-compile to configure properly.
Here is the message
root@thelma:~# dpkg --configure sa-compile
Setting up sa-compile (3.4.1-3) ...
Running sa
> On Feb 12, 2015, at 14.09, Kevin A. McGrail wrote:
>
> On 2/11/2015 7:25 PM, listsb-spamassas...@bitrate.net wrote:
>> i hope another solicitation for this help request is ok.
>
> It's ok.
>
> Overall, I agree. I tested on a devel box and running sa-compile
On Thu, 12 Feb 2015 14:09:00 -0500
Kevin A. McGrail wrote:
> On 2/11/2015 7:25 PM, listsb-spamassas...@bitrate.net wrote:
> > i hope another solicitation for this help request is ok.
>
> It's ok.
>
> Overall, I agree. I tested on a devel box and running sa-compile
On 2/11/2015 7:25 PM, listsb-spamassas...@bitrate.net wrote:
i hope another solicitation for this help request is ok.
It's ok.
Overall, I agree. I tested on a devel box and running sa-compile does
have an rm line but did leave these files listed below.
Because /tmp is a considered
i hope another solicitation for this help request is ok.
> On Feb 04, 2015, at 09.19, btb wrote:
>
> hi-
>
> i happened to notice a bunch of old files in /tmp/, related to spamassassin.
> after a bit of testing, it looks like sa-compile isn't cleaning up after
>
hi-
i happened to notice a bunch of old files in /tmp/, related to
spamassassin. after a bit of testing, it looks like sa-compile isn't
cleaning up after itself?
>ls -alH /tmp/
total 44
drwxrwxrwt 2 root root 36864 Feb 3 17:18 .
drwxr-xr-x 22 root root 4096 Dec 25 00:34 ..
>
On Sat, 3 May 2014, RW wrote:
On Fri, 02 May 2014 21:51:02 +0200
Axb wrote:
2) The non-amenable rules are processed, but may be slower than if
they weren't compiled?
yep
It means they get processed as normal in perl, so they don't get
speeded-up, but they aren't slowed-down.
One thing,
On 05/03/2014 01:18 PM, RW wrote:
On Fri, 02 May 2014 21:51:02 +0200
Axb wrote:
2) The non-amenable rules are processed, but may be slower than if
they weren't compiled?
yep
It means they get processed as normal in perl, so they don't get
speeded-up, but they aren't slowed-down.
correct
On Fri, 02 May 2014 21:51:02 +0200
Axb wrote:
> > 2) The non-amenable rules are processed, but may be slower than if
> > they weren't compiled?
>
> yep
It means they get processed as normal in perl, so they don't get
speeded-up, but they aren't slowed-down.
On 05/02/2014 09:28 PM, Quanah Gibson-Mount wrote:
I'm looking at compiling the SA rules to get a measurement of the
difference in SA timing to reduce delivery times for our email. I had a
couple of questions first though:
a) I assume that there's no issue uncommenting loadplugin
Mail::SpamAssa
--On May 2, 2014 at 3:47:22 PM -0400 "Kevin A. McGrail"
wrote:
Does this mean that:
1) The non-amenable rules are never processed?
It more means they won't be compiled and you might not be able to compile
them is more my understanding. I remember seeing the issue with sought
rules where w
On 5/2/2014 3:28 PM, Quanah Gibson-Mount wrote:
I'm looking at compiling the SA rules to get a measurement of the
difference in SA timing to reduce delivery times for our email. I had
a couple of questions first though:
a) I assume that there's no issue uncommenting loadplugin
Mail::SpamAssa
I'm looking at compiling the SA rules to get a measurement of the
difference in SA timing to reduce delivery times for our email. I had a
couple of questions first though:
a) I assume that there's no issue uncommenting loadplugin
Mail::SpamAssassin::Plugin::Rule2XSBody even if I'm not using c
On Sun, 21 Apr 2013 19:47:49 +0100
John Horne wrote:
> > That's the received wisdom, but I've never seen a definitive reason
> > why. Compiled rules are intended to co-exit with non-compiled rules,
> > and from my limited testing, rules behave correctly when they are
> > added, removed or modifie
On Thu, 2013-04-18 at 14:08 +0100, RW wrote:
> On Wed, 17 Apr 2013 21:40:33 +0100
> John Horne wrote:
>
> > Hello,
> >
> > We are running SpamAssassin 3.3.2 on a CentOS 5.9 server. sa-update
> > runs via a daily cron job, and we have modified that to run
>
On Wed, 17 Apr 2013 21:40:33 +0100
John Horne wrote:
> Hello,
>
> We are running SpamAssassin 3.3.2 on a CentOS 5.9 server. sa-update
> runs via a daily cron job, and we have modified that to run
> sa-compile as well. However, there are some questions:
>
> sa-compile is ru
Hello,
We are running SpamAssassin 3.3.2 on a CentOS 5.9 server. sa-update runs
via a daily cron job, and we have modified that to run sa-compile as
well. However, there are some questions:
sa-compile is run without any options. So what I am unsure of is whether
our local rules (in /etc/mail
21.10.2012 03:10, Kevin A. McGrail kirjoitti:
> On 10/20/2012 5:01 PM, Jari Fredriksson wrote:
>> Sa-compile says:
>>
>> # /usr/bin/sa-compile
>> Oct 20 23:59:32.992 [6734] info: generic: base extraction starting. this
>> can take a while...
>> Oct 20 23:59:
On 10/20/2012 5:01 PM, Jari Fredriksson wrote:
Sa-compile says:
# /usr/bin/sa-compile
Oct 20 23:59:32.992 [6734] info: generic: base extraction starting. this
can take a while...
Oct 20 23:59:32.992 [6734] info: generic: extracting from rules of type
body_0
100
Sa-compile says:
# /usr/bin/sa-compile
Oct 20 23:59:32.992 [6734] info: generic: base extraction starting. this
can take a while...
Oct 20 23:59:32.992 [6734] info: generic: extracting from rules of type
body_0
100
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6649
--
"Will I ever learn? I hope not, I'm having too much fun."
- Brent "Minime" Avis, motorcycle.com
http://www.ChaosReigns.com
just noted
--
Benny Pedersen
Replying to ones self is not good... or maybe I ought to have had that
cupa tea break earlier...
sa-compile assumes qx(re2c
this does not consider alternative locations, such as those who install
re2c from source to default location, being /usr/local/bin
put the path in there and it runs
Hi,
Does anyone have a list of the error codes?
running normally for years called from cron bash script, I am moving it
to cron perl script (for lots of reasons and other things), run from
console it works, but run from cron it fails, exits with 256 (assumed
exit code 1 ), tried backticks and syste
On Mon, 2011-08-15 at 16:34 -0400, Michael Scheidell wrote:
> > I just did an sa-update and the problem didn't go away.
> >
> > I'm running trunk (3.4.0) updated a couple days ago.
> >
> not fixed yet.
>
> re2c: error: line 154, column 2: unterminated string constant (missing ")
> command failed
On 8/15/11 12:08 PM, dar...@chaosreigns.com wrote:
On 08/15, Daniel McDonald wrote:
re2c: error: line 194, column 2: unterminated string constant (missing ")
Yup, it's a sought rule. Opened a bug:
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6649
Thanks for posting this so I kne
On 08/15, Daniel McDonald wrote:
>re2c: error: line 194, column 2: unterminated string constant (missing ")
Yup, it's a sought rule. Opened a bug:
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6649
Thanks for posting this so I knew it wasn't a local problem.
The problematic rule is
On 8/15/11 10:27 AM, Bowie Bailey wrote:
But that server is still running SA 3.3.1, so this may be caused by
something that changed from 3.3.1 to 3.3.2.
might be 3.3.2.. we have 3.3.2 also.
I do have OLD sought rules on systems. I started to see this fail at
3:00am yesterday, CEST time (9pm
ting, spamassassin --lint didn't pick anything up.
>>
>> also note, 'scanner2.c' is a blank file, 0 bytes\
>>
>
> didn't help: (tz is CEST)
>
> you also use sought_rules?
Yes, I download the sought.rules.yerp.org channel.
>
> s
t pick anything up.
>>
>> also note, 'scanner2.c' is a blank file, 0 bytes\
>
> didn't help: (tz is CEST)
>
> you also use sought_rules?
>
> sa-compile
> Aug 15 16:11:10.524 [56726] info: generic: base extraction starting.
> this can take a while.
r2.c' is a blank file, 0 bytes\
didn't help: (tz is CEST)
you also use sought_rules?
remove sought_rules:
rm -rf sought_rules_yerp_org*
rm z-INCLUDE-LATE.cf
sa-compile
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
>*| *SECNAP Network Security Corporation
t help: (tz is CEST)
you also use sought_rules?
sa-compile
Aug 15 16:11:10.524 [56726] info: generic: base extraction starting.
this can take a while...
Aug 15 16:11:10.525 [56726] info: generic: extracting from rules
On 8/15/11 10:07 AM, Daniel McDonald wrote:
I just noticed that my cron-job for sa-update/sa-compile has crashed
over the weekend.
Spamassassin lints fine, but sa-compile fails:
Aug 15 08:59:42.970 [469] info: generic: base extraction starting.
this can take a while...
Aug 15 08:59:42.970
I just noticed that my cron-job for sa-update/sa-compile has crashed over
the weekend.
Spamassassin lints fine, but sa-compile fails:
Aug 15 08:59:42.970 [469] info: generic: base extraction starting. this can
take a while...
Aug 15 08:59:42.970 [469] info: generic: extracting from rules of type
On Tue, 2011-02-15 at 14:37 +0100, J4K wrote:
> Also, I thought that one only had to run spamassassin --lint once. I
> did a month ago. Afterwards, I thought that only sa-compile had to be
> run.
It's a syntax check, reporting errors with your configuration and rules.
The lin
with debug enabled for more information
The lint check failed because there is an invalid option in your config
file. A successful lint check produces no output at all.
> # sa-compile
> Feb 15 14:34:33.485 [15149] info: config: failed to parse line,
> skipping, in "/etc/spamassassin/
t; /usr/local/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Plugin/DCC.pm
> /var/amavis/etc/DCC.pm
> mx1# grep dcc_add
> /usr/local/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Plugin/DCC.pm
>
> no dcc_add_header in the plugin.
Removed. It took a while for this part to sink in. sa-compile ru
On 2/15/11 8:46 AM, J4K wrote:
use_dcc 1
dcc_path /usr/local/bin/dccproc
dcc_home /var/dcc
dcc_add_header 1
just like lint says, dcc_add_header is NOT valid.
locate DCC.pm
/usr/local/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Plugin/DCC.pm
/var/amavis/etc/DCC.pm
mx1# grep dcc_add
/usr/local
On 02/15/2011 02:43 PM, Lawrence @ Rogers wrote:
> On 15/02/2011 10:07 AM, J4K wrote:
>>
>> Its pretty moot any way, because now after running spamassassin
>> -lint, sa-compile still fails with the same error.
> Hi,
>
> Just because DCC is running doesn't mean
On 15/02/2011 10:07 AM, J4K wrote:
Its pretty moot any way, because now after running spamassassin -lint,
sa-compile still fails with the same error.
Hi,
Just because DCC is running doesn't mean SA is configured to use it.
Can you post the following:
- Output of spamassassin -
On 02/15/2011 02:19 PM, Lawrence @ Rogers wrote:
> On 15/02/2011 9:27 AM, J4K wrote:
>> spamassassin --lint
> This may seem obvious, but did you run "spamassassin --lint" like
> sa-compile suggested?
>
> I assume DCC is probably not loaded, or disabled in your setup
On 15/02/2011 9:27 AM, J4K wrote:
spamassassin --lint
This may seem obvious, but did you run "spamassassin --lint" like
sa-compile suggested?
I assume DCC is probably not loaded, or disabled in your setup.
Open up /etc/spamassassin/local.cf, find this line
dcc_add_header 1
Comm
Hi chaps,
I added the FuzzyOCR (via Debian repos) into sa a few days ago, and
finally got around to running sa-compile which looks like it fails. I
tried with the -D option, but the verbosity was too great for me to make
head nor tail of it. I don't know if this is FuzzyOCR or
Where
What I've read in the past suggests that sa-compile needs to be rerun
each time sa-update modifies the rules. What happens if it isn't?
I get the impression from Rule2XSBody.pm that new, modified and
difficult rules are left for evaluation in perl, and the unmodified
compiled rules c
On 11/12/2010 6:05 PM, fchan wrote:
2) re2c 0.12.3
I can't say I even recall using re2c 0.12.x, but I do remember several
bugs in 0.13.x prior to the current 0.13.5. Is upgrading an option?
0.13.5 has been stable for over 2 years and works great here.
--
/Jason
On 11/12/10 5:38 PM, fchan wrote:
I was trying to do sa-compile -D on my system and I got this error
message: \
first, tell us:
1) version of SA
2) version of re2c
3) what rules, other than stock SA rules do you have
4) what local rules, changes, edits do you have?
5) what operating system
On 11/12/10 5:38 PM, fchan wrote:
I was trying to do sa-compile -D on my system and I got this error
message: \
first, tell us:
1) version of SA
2) version of re2c
3) what rules, other than stock SA rules do you have
4) what local rules, changes, edits do you have?
5) what operating system
I was trying to do sa-compile -D on my system and I got this error message:
cd /tmp/.spamassassin28731HM9DTNtmp
cd Mail-SpamAssassin-CompiledRegexps-body_0
re2c -i -b -o scanner1.c scanner1.re
re2c -i -b -o scanner2.c scanner2.re
re2c: error: line 85, column 12: unexpected character: 0x1E
What
1 - 100 of 319 matches
Mail list logo
