> On Mon, 11 Jan 2010, Warren Togami wrote:
>> Try wiping out /var/lib/spamassassin/*, does spamassassin work then?
On 11.01.10 08:28, Rich Shepard wrote:
> I don't have a spamassassin directory in /var/lib/.
FreeBSD uses /var/db/spamassassin. Or do:
# grep LOCAL_STATE_DIR `whichspamassassin s
How come that you messed this up with regards to that arbitrary rules
directory?
Kai
--
Get your web at Conactive Internet Services: http://www.conactive.com
On Mon, 11 Jan 2010, Rich Shepard wrote:
So I found and downloaded v320.pre into /etc/mail/spamassassin/rules and
still get the error. What have I missed in getting SA to see the new
.pre file is now present and calls for the check_main to be run?
Putting them into the rules subdirectory unde
On Mon, 11 Jan 2010, Benny Pedersen wrote:
mv /etc/mail/spamassassin/rules /etc/mail/spamassassin
no ?
Benny:
You and Larry gave me the solution. I found v320.pre and put it in
/etc/mail/spamassassin/rules. Then, based on your suggestion above, I copied
it up one directory level to /etc/mai
On Mon, 11 Jan 2010, Rosenbaum, Larry M. wrote:
It looks like you are missing the v320.pre file, which contains
Larry,
Yes, that's true. I have v310.pre and v312.pre.
loadplugin Mail::SpamAssassin::Plugin::Check
along with several other important loadplugin lines.
So I found and downl
On Mon 11 Jan 2010 08:45:40 PM CET, "Rosenbaum, Larry M." wrote
check: no loaded plugin implements 'check_main': cannot scan! at
/usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/PerMsgStatus.pm
line 164.
What plugin do I need to have loaded to resolve this error?
It looks like you are missing
> check: no loaded plugin implements 'check_main': cannot scan! at
> /usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/PerMsgStatus.pm
> line
> 164.
>
>What plugin do I need to have loaded to resolve this error?
It looks like you are missing the v320.pre file, which contains
loadplugin Mai
On Mon, 11 Jan 2010, Benny Pedersen wrote:
no do not copy, edit the files in there place where thay got installed
Benny,
OK.
where is your pre files located ?
if thay are in /etc/mail/spamassassin/rules ?
/etc/mail/spamassassin/rules
output from --lint tells where thay should be
On Mon 11 Jan 2010 08:07:12 PM CET, Rich Shepard wrote
Should I copy the .pre files to /usr/share/spamassassin?
no do not copy, edit the files in there place where thay got installed
spamassassin 2>&1 -D --lint | less
I can post the results, but the final error still is:
check: no loaded p
On Mon, 11 Jan 2010, Benny Pedersen wrote:
rules dir error
Benny,
Should I copy the .pre files to /usr/share/spamassassin?
spamassassin 2>&1 -D --lint | less
I can post the results, but the final error still is:
check: no loaded plugin implements 'check_main': cannot scan! at
/usr/li
On Mon 11 Jan 2010 07:01:04 PM CET, Rich Shepard wrote
In /etc/mail/spamassassin/rules/ I have init.pre, v310.pre, and
v312.pre files.
which would be a non-default location.
Almost all SA-related files are in /etc/mail/spamassassin/; that's where
the Slackware package installs everything. If th
On Mon, 11 Jan 2010, David Michaels wrote:
find / -name spamassassin -print
/etc/mail/spamassassin
/etc/mail/spamassassin/blib/script/spamassassin
/etc/mail/spamassassin/spamassassin
/opt/src/slackbuilds/spamassassin
/usr/bin/spamassassin
/usr/share/spamassassin
Rich
Quoting "Rich Shepard" :
On Mon, 11 Jan 2010, Kai Schaetzl wrote:
In /etc/mail/spamassassin/rules/ I have init.pre, v310.pre, and
v312.pre files.
which would be a non-default location.
Kai,
Almost all SA-related files are in /etc/mail/spamassassin/; that's where
the Slackware package in
On Mon, 11 Jan 2010, Kai Schaetzl wrote:
In /etc/mail/spamassassin/rules/ I have init.pre, v310.pre, and
v312.pre files.
which would be a non-default location.
Kai,
Almost all SA-related files are in /etc/mail/spamassassin/; that's where
the Slackware package installs everything. If this
Rich Shepard wrote on Mon, 11 Jan 2010 08:07:40 -0800 (PST):
> In /etc/mail/spamassassin/rules/ I have init.pre, v310.pre, and
> v312.pre files.
which would be a non-default location.
Kai
--
Get your web at Conactive Internet Services: http://www.conactive.com
Quoting "Rich Shepard" :
On Mon, 11 Jan 2010, Warren Togami wrote:
Try wiping out /var/lib/spamassassin/*, does spamassassin work then?
Warren,
I don't have a spamassassin directory in /var/lib/.
Rich
Sorry but I must insert a smiley...
:)
On Mon, 11 Jan 2010, Warren Togami wrote:
Try wiping out /var/lib/spamassassin/*, does spamassassin work then?
Warren,
I don't have a spamassassin directory in /var/lib/.
Rich
On 01/11/2010 11:07 AM, Rich Shepard wrote:
At the suggestion of a local user I ran 'sa-update -D' to bring my
Slackware-12.2 system running SA-3.2.5 up to date. Instead, I just dug
myself a hole and fell in by running the above. Sigh.
What I see as a result is:
[6753] error: check: no loaded
At the suggestion of a local user I ran 'sa-update -D' to bring my
Slackware-12.2 system running SA-3.2.5 up to date. Instead, I just dug
myself a hole and fell in by running the above. Sigh.
What I see as a result is:
[6753] error: check: no loaded plugin implements 'check_main': cannot sc
Hi Tica,
Tica wrote:
After a few tries (it was my mistake about the the patch error) I was able
to patch spamd, but after a few testing, I needed to fall back to unpatched
3.2.5
The patched version was with two problems:
1. Spam scanning was not working... I got the same error to a lot of
in
#x27;m
not kidding try it.
--
Martin Hepworth
Snr Systems Administrator
Solid State Logic
Tel: +44 (0)1865 842300
> > -Original Message-
> > From: Alex Woick [mailto:[EMAIL PROTECTED]
> > Sent: 26 June 2007 19:26
> > To: users@spamassassin.apache.org
> > Subject: d
On Tue, Jun 26, 2007 at 08:26:22PM +0200, Alex Woick wrote:
> Isn't SpamAssassin supposed to try the next nameserver from resolv.conf
> on such a hard error? I expected that it would transparently fail over
> to 10.10.10.12 and use that server. Nothing else in my network
> encountered a problem
I have two nameservers in my /etc/resolv.conf:
nameserver 10.10.10.11
nameserver 10.10.10.12
Now, the named daemon on 10.10.10.11 was stopped. The one on 10.10.10.12
was still up. SpamAssassin, which is also running on 10.10.10.11,
suddenly threw these errors upon every dns request:
Jun 26 1
23 matches
Mail list logo
