On Wed, 6 Apr 2011, Benny Pedersen wrote:
disable this v320.pre:loadplugin
Mail::SpamAssassin::Plugin::Rule2XSBody
and restart spamd. your errors will go away.
you did not listen, but try:
spamassassin 2>&1 -D --lint | less
any unwanted plugins failing ?, or do you like to use more plugin
On Wed, 6 Apr 2011 19:18:39 +0200 (CEST), Marco Beishuizen
wrote:
>> disable this v320.pre:loadplugin
Mail::SpamAssassin::Plugin::Rule2XSBody
>> and restart spamd. your errors will go away.
you did not listen, but try:
spamassassin 2>&1 -D --lint | less
any unwanted plugins failing ?, or do
On Tue, 5 Apr 2011, Michael Scheidell wrote:
you should disable the compile plugin, not bother compiling. with a
borked perl install, the best thing to do is start from scratch. its
almost impossible to fix.
disable this v320.pre:loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody
and restar
On Tue, 5 Apr 2011, Michael Scheidell wrote:
did you reload spamd, restart spamd?
when you recompile the rules, you need to tell spamd to reload.
did this used to work before you upgraded to perl 5.12?
When spamd restarts I also get:
...
Stopping spamd.
Waiting for PIDS: 9064.
Starting spamd.
On 4/5/11 3:28 PM, Marco Beishuizen wrote:
On Tue, 5 Apr 2011, Michael Scheidell wrote:
did you reload spamd, restart spamd?
when you recompile the rules, you need to tell spamd to reload.
did this used to work before you upgraded to perl 5.12?
Yes I recompiled and restarted spamd. I think
On Tue, 5 Apr 2011, Michael Scheidell wrote:
did you reload spamd, restart spamd?
when you recompile the rules, you need to tell spamd to reload.
did this used to work before you upgraded to perl 5.12?
Yes I recompiled and restarted spamd. I think I have this error for a long
time, also with
On 4/5/11 3:17 PM, Marco Beishuizen wrote:
On Tue, 5 Apr 2011, Michael Scheidell wrote:
just 'sa-compile'
make sure it completes.
do a 'spamassassin --lint' to make sure you don't have any rules that
won't compile.
also, AFTER you compile the rules, you have to restart spamd.
I already
On Tue, 5 Apr 2011, Michael Scheidell wrote:
just 'sa-compile'
make sure it completes.
do a 'spamassassin --lint' to make sure you don't have any rules that
won't compile.
also, AFTER you compile the rules, you have to restart spamd.
I already ran sa-compile twice, and didn't get any error
On 4/5/11 3:01 PM, Marco Beishuizen wrote:
On Tue, 5 Apr 2011, Michael Scheidell wrote:
spamd[1353]: Can't locate
Mail/SpamAssassin/CompiledRegexps/body_0.pm in @INC (@INC contains:
/var/db/spamassassin/compiled/5.012/3.003001
/var/db/spamassassin/compiled/5.012/3.003001/auto
/usr/
On Tue, 5 Apr 2011, Michael Scheidell wrote:
spamd[1353]: Can't locate Mail/SpamAssassin/CompiledRegexps/body_0.pm in
@INC (@INC contains:
/var/db/spamassassin/compiled/5.012/3.003001
/var/db/spamassassin/compiled/5.012/3.003001/auto
/usr/local/lib/perl5/site_perl/5.12.3
you need to co
On 4/5/11 2:52 PM, Marco Beishuizen wrote:
After some googling, I reinstalled SA, and ran sa-compile again but
the message stays. I'm running SA on FreeBSD 8.2-STABLE and sendmail.
if you are NOT running the ports version, then SA might put the files in
the wrong place.
I am the ports mainta
On 4/5/11 2:52 PM, Marco Beishuizen wrote:
...
spamd[1353]: Can't locate Mail/SpamAssassin/CompiledRegexps/body_0.pm
in @INC (@INC contains:
/var/db/spamassassin/compiled/5.012/3.003001
/var/db/spamassassin/compiled/5.012/3.003001/auto
/usr/local/lib/perl5/site_perl/5.12.3
you ne
Hi,
For a long time I'm getting the above message when spamd is started. All
seems to work fine so I never tried to repair it, but since it is an error
message I was wondering what the problem is. The full message is:
...
spamd[1353]: Can't locate Mail/SpamAssassin/CompiledRegexps
On Fri, June 6, 2008 02:21, Chris wrote:
> Since I posted this early this morning CDT, I've seen no responses, am I the
> only one who saw this or caught it?
remember to load re2c plugin when sa-compiler is used
spamassassin 2>&1 -D --lint
sa-compile -D --list
i am sure it shows something :-)
On Thursday 05 June 2008 8:15 pm, D Hill wrote:
> > It has never been there before. SA-Update was run at 6:11am and was
> > restarted at Jun 5 06:14:20 localhost spamassassin: spamd startup
> > succeeded
>
> Perhaps you do not have something set up right or haven't run sa-compile
> yet. Looking
On Thu, 5 Jun 2008 at 06:24 -0500, [EMAIL PROTECTED] confabulated:
After this mornings sa-update run I noticed this in my syslog:
Jun 5 06:14:24 localhost spamd[26853]: Can't locate
Mail/SpamAssassin/CompiledRegexps/body_0.pm in @INC (@INC
contains: /var/lib/spamassassin/compiled/3.0
On Thursday 05 June 2008 7:36 pm, Jim Knuth wrote:
> >
> > [26462] dbg: zoom: loading compiled ruleset
> > from /var/lib/spamassassin/compiled/3.002004
> >
> > [26462] dbg: zoom: loading compiled ruleset
> > from /var/lib/spamassassin/compiled/3.002004
> > [26462] dbg: zoom: no compiled ruleset fo
Am 06.06.2008 2:21 Uhr, schrieb Chris:
> To continue on with the post I made early this morning right after sa-update
> ran I see this after stopping and starting SA:
>
> Jun 5 06:14:24 localhost spamd[26853]: Can't locate
> Mail/SpamAssassin/CompiledRegexps/body_0.pm in @I
To continue on with the post I made early this morning right after sa-update
ran I see this after stopping and starting SA:
Jun 5 06:14:24 localhost spamd[26853]: Can't locate
Mail/SpamAssassin/CompiledRegexps/body_0.pm in @INC (@INC
contains: /var/lib/spamassassin/compiled/3.002004
/va
After this mornings sa-update run I noticed this in my syslog:
Jun 5 06:14:24 localhost spamd[26853]: Can't locate
Mail/SpamAssassin/CompiledRegexps/body_0.pm in @INC (@INC
contains: /var/lib/spamassassin/compiled/3.002004
/var/lib/spamassassin/compiled/3.002004/auto
lib /usr/lib/
20 matches
Mail list logo
