You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by analyzer <an...@gmx.net> on 2005/12/26 13:37:38 UTC

Failed to parse

Hello everybody

I would like check that my spamassassin installation run fine. I use a 
debian server system with the newest spamassassin version and all debian 
updates.

spamassassin -D < test.text
The follow errors output:
debug: Failed to parse line in SpamAssassin configuration, skipping: 
report_safe             1
debug: Failed to parse line in SpamAssassin configuration, skipping: 
use_bayes               1
debug: Failed to parse line in SpamAssassin configuration, skipping: 
auto_learn              1
debug: Failed to parse line in SpamAssassin configuration, skipping: 
use_razor2              1
debug: Failed to parse line in SpamAssassin configuration, skipping: 
use_dcc                 1
debug: Failed to parse line in SpamAssassin configuration, skipping: 
use_pyzor               1
debug: Failed to parse line in SpamAssassin configuration, skipping: 
ok_languages            all
debug: Failed to parse line in SpamAssassin configuration, skipping: 
user_scores_sql_table           spampref

A part of my local.cf:

#
required_hits           5.0

# Whether to change the subject of suspected spam
rewrite_subject         1

# Text to prepend to subject if rewrite_subject is used
subject_tag             *****SPAM*****

# Encapsulate spam in an attachment
report_safe             1

# Use terse version of the spam report
use_terse_report        0

# Enable the Bayes system
use_bayes               1

# Enable Bayes auto-learning
auto_learn              1

# Enable or disable network checks
skip_rbl_checks         0
use_razor2              1
use_dcc                 1
use_pyzor               1

# Mail using languages used in these country codes will not be marked
# as being possibly spam in a foreign language.
ok_languages            all

# Mail using locales used in these country codes will not be marked
# as being possibly spam in a foreign language.
ok_locales              all

I can't find any mistakes. Where is the problem?

Thanks

Karsten

Re: Failed to parse

Posted by Matt Kettler <mk...@comcast.net>.
At 12:49 AM 12/27/2005, Matt Kettler wrote:

>>server:~# spamassassin -V
>>SpamAssassin version 2.20
>>
>>My provider have configured the system. Perhaps there is anything false.
>
>
>And spamassassin --lint works?? That's quite strange indeed.

Nevermind.. I re-read your original message. you never used --lint, you 
used -D.

In any event. SA 2.20 is a very ancient version of spamassassin, from May 
of 2002, over 3 and a half years ago. Many of the features you are trying 
to use were added until much later in the SA development.

Really, if SA 2.20 is all you have available, you're probably better off 
not even bothering. The efficacy of a three-year old version of SA against 
modern spam will be almost nil.

But if you must, I'd suggest consulting perldoc Mail::SpamAssassin::Conf on 
your machine. Most people here are using at least SA 2.63 with backported 
fixes from 2.64, or newer, so few will be able to help you with the setup 
and configuration. Heck, many people here, myself included, have never run 
a version that old. For example I started with SA 2.31.


 >debug: Failed to parse line in SpamAssassin configuration, skipping: 
report_safe             1

Message encapsulation, aka report_safe, was not added until SA 2.40 
(Released November 2002)

 >debug: Failed to parse line in SpamAssassin configuration, skipping: 
use_bayes               1
 >debug: Failed to parse line in SpamAssassin configuration, skipping: 
auto_learn              1

The Bayes system was not added till SA 2.50 (released Feb 2003)

 >debug: Failed to parse line in SpamAssassin configuration, skipping: 
use_razor2              1
 >debug: Failed to parse line in SpamAssassin configuration, skipping: 
use_pyzor               1

Pyzor and Razor2 support were not added until SA 2.40

 >debug: Failed to parse line in SpamAssassin configuration, skipping: 
use_dcc                 1
 >debug: Failed to parse line in SpamAssassin configuration, skipping: 
ok_languages            all
 >debug: Failed to parse line in SpamAssassin configuration, skipping: 
user_scores_sql_table          spampref

I don't know when DCC, ok_languages or SQL support were added, however 
apparently they are not supported by 2.20.






Re: Failed to parse

Posted by Matt Kettler <mk...@comcast.net>.
At 01:25 PM 12/26/2005, analyzer wrote:
>Matt Kettler schrieb:
>
>>At 10:18 AM 12/26/2005, analyzer wrote:
>>
>>>Sry, my mistake. I use version 2.20. I can't update to the newest 
>>>version, beacause the confixx compatibility.
>>
>>
>>You are not using SA 2.20.. SA didn't even support the --lint command 
>>until 2.40. The fact that you could run a --lint clearly indicates you're 
>>using something at least as new as 2.40.
>>
>>Check your version again. Preferably with spamassassin -V
>>
>>
>>
>
>server:~# spamassassin -V
>SpamAssassin version 2.20
>
>My provider have configured the system. Perhaps there is anything false.


And spamassassin --lint works?? That's quite strange indeed. 


Re: Failed to parse

Posted by analyzer <an...@gmx.net>.
Keith Dunnett schrieb:

> analyzer wrote:
>
>> server:~# spamassassin -V
>> SpamAssassin version 2.20
>>
>> My provider have configured the system. Perhaps there is anything false.
>
>
> Perhaps you have multiple copies of SpamAssassin on the system? Try 
> 'whereis spamassassin'.
>
> As Jonn said, these errors are likely to be the product of running SA 
> 3.1.0 without loading the
> necessary modules (by reason of using an old config file). That might 
> have been installed from
> CPAN, rather than via Debian. The current Debian stable version is 
> 3.0.3-2. You might try
> 'apt-cache showpkg spamassassin' to find out which version Debian 
> thinks it has installed.
>
> If you don't mind managing the SpamAssassin installation yourself, you 
> can usually obtain a
> newer version by installing via CPAN than using Debian packages. To 
> forcibly remove SA
> and install the newest version, you could do the following (all as root):
>
> 1. apt-get remove spamassassin
> 2. whereis spamassassin
> 3. Delete anything still listed by 'whereis spamassassin', including 
> /etc/spamassassin
> 4. perl -MCPAN -e shell
> 5. Accept the defaults to set up the CPAN shell
> 6. In CPAN, type 'install Mail::SpamAssassin'.
> 7. Exit CPAN and cd /etc/spamassassin
> 8. Edit the configuration files local.cf and v310.pre according to 
> taste/need.
> 9. Test spamassassin as before.
> 10. When happy, google for RulesDuJour and decide whether you want it. 
> Many
> of us find that it improves the effectiveness of SpamAssassin.
>
> This is a fairly drastic solution, but ensures that you benefit from 
> the latest version. Do note
> that this will no longer be upgraded for you by Debian's 'apt-get 
> upgrade', so you will have
> to keep an eye out for new releases and update via CPAN. It's worth 
> the effort, though.
>
> WARNING: Before doing this, make sure that you have perl 5.6.1 or 
> better, which is a
> requirement of spamassassin 3.x. Also, please read the upgrade notes 
> available at
> http://spamassassin.apache.org/full/3.1.x/dist/UPGRADE before 
> starting; you might
> wish to take advantage of some of the new features.
>
> And finally, as with any such advice, make sure that you understand 
> what I'm suggesting
> and that it is what you want to do before you start typing commands. 
> If not, read the docs
> or ask further questions.
>
> HTH,
>
> Keith
>
>
>
>
>
>>
>>
>>
>
>
>
Here are the errors from starting sapd:
[13505] error: udp_timeout: no such method at 
/usr/local/share/perl/5.6.1/Net/DN
S/Resolver.pm line 1136
[13505] error: 
_Net::DNS::Resolver::AUTOLOAD('Net::DNS::Resolver=HASH(0x8a381c0)
', 3) called at 
/usr/local/share/perl/5.6.1/Mail/SpamAssassin/DnsResolver.pm lin
e 97
[13505] error: _eval {...} called at 
/usr/local/share/perl/5.6.1/Mail/SpamAssass
in/DnsResolver.pm line 85
[13505] error: 
_Mail::SpamAssassin::DnsResolver::load_resolver('Mail::SpamAssass
in::DnsResolver=HASH(0x8a38034)') called at 
/usr/local/share/perl/5.6.1/Mail/Spa
mAssassin/DnsResolver.pm line 65
[13505] error: 
_Mail::SpamAssassin::DnsResolver::new('Mail::SpamAssassin::DnsRes
olver', 'Mail::SpamAssassin=HASH(0x80feeec)') called at 
/usr/local/share/perl/5.
6.1/Mail/SpamAssassin.pm line 299
[13505] error: _Mail::SpamAssassin::new('Mail::SpamAssassin', 
'Mail::SpamAssassi
n=HASH(0x80feeec)') called at /usr/local/bin/spamd line 686
[13505] warn: dns: Net::DNS version is 0.12, but need 0.34 at 
/usr/local/share/p
erl/5.6.1/Mail/SpamAssassin/Dns.pm line 589.
[13505] info: spamd: server started on port 783/tcp (running version 3.1.0)
[13505] info: spamd: server pid: 13505
[13505] info: spamd: server successfully spawned child process, pid 13763
[13505] info: spamd: server successfully spawned child process, pid 13796
[13505] info: prefork: child states: IS
[13505] info: prefork: child states: II

Re: Failed to parse

Posted by Gary V <mr...@hotmail.com>.
>From: "analyzer" <an...@gmx.net>
>
>>Matt Kettler schrieb:
>>
>>>At 06:51 AM 12/30/2005, analyzer wrote:
>>>
>>>>hanks four your help. My provider had updated the system. Now 
>>>>spamassassin 3.0.8 is install and it run fine.
>>>
>>>
>>>3.0.8?
>>>
>>Sry, my mistake 3.0.3.
>
>Provider screwed up again. 3.0.4 is the one that should have been
>installed. 3.0.3 has a potential DoS, Denial of Service, hole.
>
>{^_^}
>

If the Debian version is used, it is patched, no need to worry. It probably 
is the Debian version since I don't know why anyone would deliberately 
install 3.0.3 from source.

dpkg -l spamassassin

Gary V

_________________________________________________________________
Don’t just search. Find. Check out the new MSN Search! 
http://search.msn.click-url.com/go/onm00200636ave/direct/01/


Re: Failed to parse

Posted by jdow <jd...@earthlink.net>.
From: "analyzer" <an...@gmx.net>

> Matt Kettler schrieb:
> 
>> At 06:51 AM 12/30/2005, analyzer wrote:
>>
>>> hanks four your help. My provider had updated the system. Now 
>>> spamassassin 3.0.8 is install and it run fine.
>>
>>
>> 3.0.8?
>>
> Sry, my mistake 3.0.3.

Provider screwed up again. 3.0.4 is the one that should have been
installed. 3.0.3 has a potential DoS, Denial of Service, hole.

{^_^}


Re: Failed to parse

Posted by analyzer <an...@gmx.net>.
Matt Kettler schrieb:

> At 06:51 AM 12/30/2005, analyzer wrote:
>
>> hanks four your help. My provider had updated the system. Now 
>> spamassassin 3.0.8 is install and it run fine.
>
>
> 3.0.8?
>
Sry, my mistake 3.0.3.

Re: Failed to parse

Posted by Matt Kettler <mk...@comcast.net>.
At 06:51 AM 12/30/2005, analyzer wrote:
>hanks four your help. My provider had updated the system. Now spamassassin 
>3.0.8 is install and it run fine.

3.0.8? 


Re: Failed to parse

Posted by analyzer <an...@gmx.net>.
Gary V schrieb:

> You might try to manually install a little older version of Net::DNS
>
> cd /usr/local/src
> wget http://www.net-dns.org/download/Net-DNS-0.48.tar.gz
> tar xzvf Net-DNS-0.48.tar.gz
> cd Net-DNS-0.48
> perl Makefile.PL
>
> Do you want to enable these tests? [y] n
>
> make
> make test
> make install
>
>
Thanks four your help. My provider had updated the system. Now 
spamassassin 3.0.8 is install and it run fine.

Regards

Karsten


Re: Failed to parse

Posted by Gary V <mr...@hotmail.com>.
You might try to manually install a little older version of Net::DNS

cd /usr/local/src
wget http://www.net-dns.org/download/Net-DNS-0.48.tar.gz
tar xzvf Net-DNS-0.48.tar.gz
cd Net-DNS-0.48
perl Makefile.PL

Do you want to enable these tests? [y] n

make
make test
make install

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/


Re: Failed to parse

Posted by Gary V <mr...@hotmail.com>.
>It would be nice if someone actually could tell us what the deal is with 
>IPv6 on Debian Sarge.
>

Sorry I am getting off topic here, but:
Looks like if you do a fresh install with 'linux26' (to get the 2.6 kernel), 
IPv6 is enabled. I personally have had issues (segfaults) after I to 
upgraded from 2.4 to 2.6 on a test box, so I personally don't recommend 
going that route, YMMV. When I want to use the 2.6 kernel, I start out that 
way. I install 2.4 on production boxes and forget about IPv6 myself.

Gary V

_________________________________________________________________
On the road to retirement? Check out MSN Life Events for advice on how to 
get there! http://lifeevents.msn.com/category.aspx?cid=Retirement


Re: Failed to parse

Posted by Gary V <mr...@hotmail.com>.
>>>Thanks for your help. I can't install IO::Socket::INET6.
>>
>>The same thing happened on my (newer) Debian system. If you use IPv6, this 
>>may be serious
>>and we'll need to find out why. If, like me, you only use IPv4, just 
>>'force install IO::Socket::INET6'.
>>

I think the big problem is it looks like you are still running Woody. To get 
a fairly recent version of Net::DNS will necessitate a newer version of Perl 
and libc6 etc. etc... IPV6 may require a kernel upgrade also. I'm just not 
sure you will find any joy until you do a dist-upgrade. I could be wrong.

http://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html

I also could not install IO::Socket::INET6 from CPAN on my Sarge box, but 
this worked:
apt-get install libio-socket-inet6-perl
I don't actually know if the program works however. I have not understood 
exactly what the deal is with IPV6 on Sarge 3.1. I think it works if you 
install 3.1 from scratch, but when you come to it from an upgrade path I'm 
not certain whether it works or not. I think I remember it being a last 
minute thing just prior to Sarge going stable (or maybe they just fixed some 
programs that tried to use IPv6 so they wouldn't use it). One example would 
be on a fresh install you will have IPV6 related info in /etc/hosts that may 
be missing on earlier versions (but I don't know how significant this is). 
Here is an example:

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

Even then I'm not sure IPV6 is functioning. I use DCC and if I try to turn 
IPv6 on with:
cdcc 'IPv6 on'
it replies with:
IPv6 switch not changed.
and running 'cdcc info' confirms that IPv6 is still not in use.

In Postfix, if I set:
inet_protocols = ipv6
I get:
postfix: fatal: inet_protocols: IPv6 support is disabled: Address family not 
supported by protocol
It would be nice if someone actually could tell us what the deal is with 
IPv6 on Debian Sarge.

Just an unrelated note: my experience has shown that when installing 
packages from CPAN (same as installing from source), Perl finds those 
modules in the path before it will find the Debian version.

Gary V

_________________________________________________________________
On the road to retirement? Check out MSN Life Events for advice on how to 
get there! http://lifeevents.msn.com/category.aspx?cid=Retirement


Re: Failed to parse

Posted by analyzer <an...@gmx.net>.
Keith Dunnett schrieb:

> analyzer wrote:
>
>>>
>> Thanks for your help. I can't install IO::Socket::INET6.
>> Here the output:
>
>
>
> The same thing happened on my (newer) Debian system. If you use IPv6, 
> this may be serious
> and we'll need to find out why. If, like me, you only use IPv4, just 
> 'force install IO::Socket::INET6'.
>
> Regards,
>
> Keith
>
>
The Output ist from "force install IO::Socket::INET6".

Regards,

Karsten

Re: Failed to parse

Posted by Keith Dunnett <ke...@dunnett.org>.
analyzer wrote:

>>
> Thanks for your help. I can't install IO::Socket::INET6.
> Here the output:


The same thing happened on my (newer) Debian system. If you use IPv6, 
this may be serious
and we'll need to find out why. If, like me, you only use IPv4, just 
'force install IO::Socket::INET6'.

Regards,

Keith


Re: Failed to parse

Posted by analyzer <an...@gmx.net>.
Keith Dunnett schrieb:

> analyzer wrote:
>
>> Package: libnet-dns-perl
>> Versions:
>> 0.19-0.1(/var/lib/apt/lists/ftp.tiscali.de_pub_debian_debian_dists_woody_main_binary-i386_Packages)(/var/lib/dpkg/status) 
>>
>
>
> That isn't what we want, and it doesn't look like Debian woody offers 
> a suitable version, so we'll do
> everything via CPAN.
>
>> The Output from cpan> test Net::DNS
>> http://cpp.sourceforge.net/?show=11192
>
>
> So your CPAN is trying to test version 0.55 but is not able to install 
> it, due to problems with one resolver
> test and several online tests. See below for suggestions...
>
>>
>> Output from spamassassin -D:
>> [29218] dbg: logger: adding facilities: all
>> [29218] dbg: logger: logging level is DBG
>> [29218] dbg: generic: SpamAssassin version 3.1.0
>> [29218] dbg: config: score set 0 chosen.
>> [29218] dbg: util: running in taint mode? yes
>> [29218] dbg: util: taint mode: deleting unsafe environment variables, 
>> resetting PATH
>> [29218] dbg: util: PATH included '/usr/local/sbin', keeping
>> [29218] dbg: util: PATH included '/usr/local/bin', keeping
>> [29218] dbg: util: PATH included '/usr/sbin', keeping
>> [29218] dbg: util: PATH included '/usr/bin', keeping
>> [29218] dbg: util: PATH included '/sbin', keeping
>> [29218] dbg: util: PATH included '/bin', keeping
>> [29218] dbg: util: PATH included '/usr/bin/X11', which doesn't exist, 
>> dropping
>> [29218] dbg: util: final PATH set to: 
>> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
>> [29218] dbg: dns: is Net::DNS::Resolver available? yes
>> [29218] dbg: dns: Net::DNS version: 0.12
>> [29218] dbg: dns: name server: 66.28.0.45, family: 2, ipv6: 0
>> Here stopped the output. I dont' know why.
>
>
>
> Well, since it requires at least Net::DNS 0.34, and has either 0.12 or 
> 0.19 depending on where
> it's looking, I'm guessing it cannot use DNS.
>
>> *************************************************
>>
>> Output from spamassassin -D --lint:
>> http://cpp.sourceforge.net/?show=11197  
>
>
>
> The good news is that this looks very close to working. The only 
> problems I see are Net::DNS (which is serious),
> ident (which is not), pyzor, which is optional, razor likewise, and 
> bayes, which can wait until the rest is working.
>
> Let's start by installing the newest version of CPAN, so we're not 
> working with outdated code.
>
> # perl -MCPAN -e shell
> > install Bundle::CPAN
> > reload cpan
>
> Then try reinstalling Net::DNS, preceded by the relevant IPv6 support
>
> > install Socket6
> > install IO::Socket::INET6 (you may have to force this if you do not 
> use IPv6)
> > install Net::DNS
>
> If this does not succeed, stop. Review any errors and attempt to 
> correct them before proceeding.
> There is no point going on until Net::DNS is fixed. If CPAN still 
> thinks it has the current version
> then 'force install Net::DNS', but this should not be necessary and is 
> not particularly desirable.
>
> When Net::DNS 0.55 is installed, retest with 'spamassassin -D lint' 
> and let's see if we've solved
> the DNS issue. When and *only* when that works, we can look at 
> improving upon it, as follows:
>
> Ident - this is only relevant if you wish to run spamd with the 
> --auth-ident flag (unlikely, and depends
> on running identd, which most systems don't). Unless you need it, 
> forget about it.
>
> Razor - the perl module is supplied by the razor-agents package which 
> needs to be at least version
> 2.40 and preferably version 2.67 or newer. Check this with 
> 'razor-client -v'. If the version offered
> by apt-get is inadequate, then install Razor from source. 
> http://razor.sourceforge.net/
>
> Pyzor - this just needs to be installed. Again, if apt offers a very 
> outdated version, it may be better to
> do this from source. http://pyzor.sourceforge.net/
>
> DCC - same story as pyzor, there may be advantages to doing this from 
> source. Equally, apt *ought*
> to work, but your mileage may vary. 
> http://www.rhyolite.com/anti-spam/dcc/
>
> RulesDuJour - a matter of personal taste, but I recommend it.
> http://www.exit0.us/index.php?pagename=RulesDuJour
>
> By the time you have quite finished, you should have a fully updated 
> SpamAssassin installation with just
> about all the available trimmings. Sorry to see you're having so much 
> difficulty in getting it set up, but it is
> well worth the effort to use up-to-date software.
>
> Speaking of which, you should also try 'sa-update -D' to make sure 
> that the update script works correctly,
> On my system (debian sarge), which is not set up to use IPv6, I had to 
> 'force install IO::Socket::INET6' for
> this to work. After that, you can add both this command and 
> RulesDuJour to your crontab, to keep
> spamassassin up to date. Then it's ready for integration with your 
> mail system.
>
> Hope that helps,
>
> Keith
>
>
>
Thanks for your help. I can't install IO::Socket::INET6.
Here the output:
Running install for module IO::Socket::INET6
Running make for M/MO/MONDEJAR/IO-Socket-INET6-2.51.tar.gz
Checksum for 
/root/.cpan/sources/authors/id/M/MO/MONDEJAR/IO-Socket-INET6-2.51.tar.gz ok
IO-Socket-INET6-2.51/
IO-Socket-INET6-2.51/t/
IO-Socket-INET6-2.51/t/io_multihomed6.t
IO-Socket-INET6-2.51/t/io_udp6.t
IO-Socket-INET6-2.51/t/io_sock6.t
IO-Socket-INET6-2.51/README
IO-Socket-INET6-2.51/INET6.pm
IO-Socket-INET6-2.51/Makefile.PL
IO-Socket-INET6-2.51/ChangeLog
IO-Socket-INET6-2.51/MANIFEST
Removing previously used /root/.cpan/build/IO-Socket-INET6-2.51

  CPAN.pm: Going to build M/MO/MONDEJAR/IO-Socket-INET6-2.51.tar.gz

Checking if your kit is complete...
Looks good
Writing Makefile for IO::Socket::INET6
cp INET6.pm blib/lib/IO/Socket/INET6.pm
Manifying blib/man3/IO::Socket::INET6.3pm
  /usr/bin/make  -- OK
Running make test
PERL_DL_NONLAZY=1 /usr/bin/perl -Iblib/arch -Iblib/lib 
-I/usr/lib/perl/5.6.1 -I/usr/share/perl/5.6.1 -e 'use Test::Harness 
qw(&runtests $verbose); $verbose=0; runtests @ARGV;' t/*.t
t/io_multihomed6....IO::Socket::INET6: socket: Address family not 
supported by protocol at t/io_multihomed6.t line 57.

                                                                             

t/io_multihomed6....dubious
Test returned status 97 (wstat 24832, 0x6100)
DIED. FAILED tests 1-5
Failed 5/5 tests, 0.00% okay
t/io_sock6..........IO::Socket::INET6: socket: Address family not 
supported by protocol at t/io_sock6.t line 45.

                                                                             

t/io_sock6..........dubious
Test returned status 97 (wstat 24832, 0x6100)
DIED. FAILED tests 1-20
Failed 20/20 tests, 0.00% okay
t/io_udp6...........
                                                                             

t/io_udp6...........ok 1/7
                                                                             

t/io_udp6...........ok
Failed Test        Stat Wstat Total Fail  Failed  List of Failed
-------------------------------------------------------------------------------
t/io_multihomed6.t   97 24832     5   10 200.00%  1-5
t/io_sock6.t         97 24832    20   40 200.00%  1-20
Failed 2/3 test scripts, 33.33% okay. 25/32 subtests failed, 21.88% okay.
make: *** [test_dynamic] Error 11
  /usr/bin/make test -- NOT OK
Running make install
Installing /usr/local/share/perl/5.6.1/IO/Socket/INET6.pm
Installing /usr/local/man/man3/IO::Socket::INET6.3pm
Writing /usr/local/lib/perl/5.6.1/auto/IO/Socket/INET6/.packlist
Appending installation info to /usr/local/lib/perl/5.6.1/perllocal.pod
  /usr/bin/make install  -- OK


Karsten

Re: Failed to parse

Posted by Keith Dunnett <ke...@dunnett.org>.
analyzer wrote: 

> Package: libnet-dns-perl
> Versions:
> 0.19-0.1(/var/lib/apt/lists/ftp.tiscali.de_pub_debian_debian_dists_woody_main_binary-i386_Packages)(/var/lib/dpkg/status) 
>

That isn't what we want, and it doesn't look like Debian woody offers a 
suitable version, so we'll do
everything via CPAN.

> The Output from cpan> test Net::DNS
> http://cpp.sourceforge.net/?show=11192

So your CPAN is trying to test version 0.55 but is not able to install 
it, due to problems with one resolver
test and several online tests. See below for suggestions...

>
> Output from spamassassin -D:
> [29218] dbg: logger: adding facilities: all
> [29218] dbg: logger: logging level is DBG
> [29218] dbg: generic: SpamAssassin version 3.1.0
> [29218] dbg: config: score set 0 chosen.
> [29218] dbg: util: running in taint mode? yes
> [29218] dbg: util: taint mode: deleting unsafe environment variables, 
> resetting PATH
> [29218] dbg: util: PATH included '/usr/local/sbin', keeping
> [29218] dbg: util: PATH included '/usr/local/bin', keeping
> [29218] dbg: util: PATH included '/usr/sbin', keeping
> [29218] dbg: util: PATH included '/usr/bin', keeping
> [29218] dbg: util: PATH included '/sbin', keeping
> [29218] dbg: util: PATH included '/bin', keeping
> [29218] dbg: util: PATH included '/usr/bin/X11', which doesn't exist, 
> dropping
> [29218] dbg: util: final PATH set to: 
> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
> [29218] dbg: dns: is Net::DNS::Resolver available? yes
> [29218] dbg: dns: Net::DNS version: 0.12
> [29218] dbg: dns: name server: 66.28.0.45, family: 2, ipv6: 0
> Here stopped the output. I dont' know why.


Well, since it requires at least Net::DNS 0.34, and has either 0.12 or 
0.19 depending on where
it's looking, I'm guessing it cannot use DNS.

> *************************************************
>
> Output from spamassassin -D --lint:
> http://cpp.sourceforge.net/?show=11197  


The good news is that this looks very close to working. The only 
problems I see are Net::DNS (which is serious),
ident (which is not), pyzor, which is optional, razor likewise, and 
bayes, which can wait until the rest is working.

Let's start by installing the newest version of CPAN, so we're not 
working with outdated code.

# perl -MCPAN -e shell
 > install Bundle::CPAN
 > reload cpan

Then try reinstalling Net::DNS, preceded by the relevant IPv6 support

 > install Socket6
 > install IO::Socket::INET6 (you may have to force this if you do not 
use IPv6)
 > install Net::DNS

If this does not succeed, stop. Review any errors and attempt to correct 
them before proceeding.
There is no point going on until Net::DNS is fixed. If CPAN still thinks 
it has the current version
then 'force install Net::DNS', but this should not be necessary and is 
not particularly desirable.

When Net::DNS 0.55 is installed, retest with 'spamassassin -D lint' and 
let's see if we've solved
the DNS issue. When and *only* when that works, we can look at improving 
upon it, as follows:

Ident - this is only relevant if you wish to run spamd with the 
--auth-ident flag (unlikely, and depends
on running identd, which most systems don't). Unless you need it, forget 
about it.

Razor - the perl module is supplied by the razor-agents package which 
needs to be at least version
2.40 and preferably version 2.67 or newer. Check this with 'razor-client 
-v'. If the version offered
by apt-get is inadequate, then install Razor from source. 
http://razor.sourceforge.net/

Pyzor - this just needs to be installed. Again, if apt offers a very 
outdated version, it may be better to
do this from source. http://pyzor.sourceforge.net/

DCC - same story as pyzor, there may be advantages to doing this from 
source. Equally, apt *ought*
to work, but your mileage may vary. http://www.rhyolite.com/anti-spam/dcc/

RulesDuJour - a matter of personal taste, but I recommend it.
http://www.exit0.us/index.php?pagename=RulesDuJour

By the time you have quite finished, you should have a fully updated 
SpamAssassin installation with just
about all the available trimmings. Sorry to see you're having so much 
difficulty in getting it set up, but it is
well worth the effort to use up-to-date software.

Speaking of which, you should also try 'sa-update -D' to make sure that 
the update script works correctly,
On my system (debian sarge), which is not set up to use IPv6, I had to 
'force install IO::Socket::INET6' for
this to work. After that, you can add both this command and RulesDuJour 
to your crontab, to keep
spamassassin up to date. Then it's ready for integration with your mail 
system.

Hope that helps,

Keith



Re: Failed to parse

Posted by analyzer <an...@gmx.net>.
Keith Dunnett schrieb:

> analyzer wrote
>
>> Yes, i had updated the libnet-dns-perl. apt-get and cpan say its up 
>> to date.
>
>
> Spamassassin doesn't - so you haven't *successfully* updated it. Paste 
> the full output of
>
>    apt-cache showpkg libnet-dns-perl
>
> then go into CPAN and run:
>
>    test Net::DNS
>
> Again, paste the full output. If the spamassassin installation failed 
> owing to lack of Net::DNS,
> then you won't even have the current version of SpamAssassin 
> installed. I have a nasty feeling
> that you're still testing with the old version.
>
> 1) Update Net::DNS properly and show evidence of success or failure..
> 2) Reinstall SpamAssassin and show that you are testing version 3.1
>
> If you still get failures with 3.1.0 installed, then paste the 
> *complete* output of
>    spamassassin -D < some.message
> which should be some 400 lines and will tell us most of what we need 
> to know.
>
> I do not intend to address any other errors yet; if they persist when 
> we have debug output
> from version 3.1 then we'll look into it. Neither Razor2 nor ident is 
> mandatory for using
> SpamAssassin, but razor is certainly useful.
>
> Regards,
>
> Keith
>
>
>
>
>
>
Output from apt-cache showpkg libnet-dns-perl:
 Package: libnet-dns-perl
Versions:
0.19-0.1(/var/lib/apt/lists/ftp.tiscali.de_pub_debian_debian_dists_woody_main_binary-i386_Packages)(/var/lib/dpkg/status)

Reverse Depends:
  spong-client,libnet-dns-perl
  spamassassin,libnet-dns-perl
  razor,libnet-dns-perl
  ptknettools,libnet-dns-perl
  mon,libnet-dns-perl
  libpoe-component-client-dns-perl,libnet-dns-perl
  libemail-valid-perl,libnet-dns-perl
  jdresolve,libnet-dns-perl
  dnswalk,libnet-dns-perl
Dependencies:
0.19-0.1 - perl (2 5.6.0-16) libdigest-md5-perl (0 (null)) 
libdigest-sha1-perl (0 (null)) libdigest-hmac-perl (0 (null)) 
libmime-base64-perl (0 (null))
Provides:
0.19-0.1 -
Reverse Provides:
*************************************************
Output form apt-cache showpkg libdigest-md5-perl:
Package: libdigest-md5-perl
Versions:
2.13-2(/var/lib/apt/lists/ftp.tiscali.de_pub_debian_debian_dists_woody_main_binary-i386_Packages)(/var/lib/dpkg/status)

Reverse Depends:
  theme-converters,libdigest-md5-perl
  syncbbdb,libdigest-md5-perl
  sporum,libdigest-md5-perl
  snap,libdigest-md5-perl
  smokeping,libdigest-md5-perl 2.13-2
  sanitizer,libdigest-md5-perl
  request-tracker1,libdigest-md5-perl
  pilot-manager,libdigest-md5-perl
  pilot-link-perl,libdigest-md5-perl
  pgi,libdigest-md5-perl
  note,libdigest-md5-perl
  mhonarc,libdigest-md5-perl
  libwww-perl,libdigest-md5-perl
  libwww-perl,libdigest-md5-perl
  libnet-ldap-perl,libdigest-md5-perl
  libnet-ftpserver-perl,libdigest-md5-perl
  libnet-dns-perl,libdigest-md5-perl
  libmd5-perl,libdigest-md5-perl 2.13
  libinline-perl,libdigest-md5-perl
  libfile-cache-perl,libdigest-md5-perl
  libdigest-sha1-perl,libdigest-md5-perl 2.13
  libdigest-perl,libdigest-md5-perl
  libdigest-md2-perl,libdigest-md5-perl 2.13
  libdigest-hmac-perl,libdigest-md5-perl
  libcrypt-passwdmd5-perl,libdigest-md5-perl
  libcache-cache-perl,libdigest-md5-perl
  libauthen-radius-perl,libdigest-md5-perl
  libapache-session-perl,libdigest-md5-perl
  libapache-asp-perl,libdigest-md5-perl
  interchange,libdigest-md5-perl
  dnscvsutil,libdigest-md5-perl
  devscripts,libdigest-md5-perl
  debsums,libdigest-md5-perl 2.12-2
  debian-cd,libdigest-md5-perl
  cricket,libdigest-md5-perl
  cons,libdigest-md5-perl
  bioperl,libdigest-md5-perl
  axkit,libdigest-md5-perl
  alamin-server,libdigest-md5-perl
  alamin-client,libdigest-md5-perl
Dependencies:
2.13-2 - perl (2 5.6.0-21) perlapi-5.6.0 (0 (null)) libc6 (2 2.2.1-2) 
libmd5-perl (3 2.02)
Provides:
2.13-2 -
Reverse Provides:
*************************************************

Output from apt-cache showpkg libdigest-sha1-perl:
Package: libdigest-sha1-perl
Versions:
2.00-1(/var/lib/apt/lists/ftp.tiscali.de_pub_debian_debian_dists_woody_main_binary-i386_Packages)(/var/lib/dpkg/status)

Reverse Depends:
  razor,libdigest-sha1-perl
  libnet-jabber-perl,libdigest-sha1-perl 1.02
  libnet-dns-perl,libdigest-sha1-perl
  libdigest-hmac-perl,libdigest-sha1-perl
Dependencies:
2.00-1 - perl (2 5.6.0-21) perlapi-5.6.0 (0 (null)) libc6 (2 2.2.1-2) 
libdigest-md5-perl (3 2.13)
Provides:
2.00-1 -
Reverse Provides:

Output from apt-cache showpkg libdigest-hmac-perl:
Package: libdigest-hmac-perl
Versions:
1.01-1(/var/lib/apt/lists/ftp.tiscali.de_pub_debian_debian_dists_woody_main_binary-i386_Packages)(/var/lib/dpkg/status)

Reverse Depends:
  libnet-dns-perl,libdigest-hmac-perl
Dependencies:
1.01-1 - perl (0 (null)) libdigest-md5-perl (0 (null)) 
libdigest-sha1-perl (0 (null))
Provides:
1.01-1 -
Reverse Provides:
*************************************************

Output from apt-cache showpkg libmime-base64-perl:
Package: libmime-base64-perl
Versions:
2.12-4(/var/lib/apt/lists/ftp.tiscali.de_pub_debian_debian_dists_woody_main_binary-i386_Packages)(/var/lib/dpkg/status)

Reverse Depends:
  liburi-perl,libmime-base64-perl
  libcrypt-ssleay-perl,libmime-base64-perl
  whisker,libmime-base64-perl
  w3mir,libmime-base64-perl
  sympa,libmime-base64-perl 1.0
  smb2www,libmime-base64-perl
  sanitizer,libmime-base64-perl
  mime-construct,libmime-base64-perl
  mailscanner,libmime-base64-perl
  libwww-perl,libmime-base64-perl 2.1
  liburi-perl,libmime-base64-perl
  libunicode-string-perl,libmime-base64-perl
  libnet-ssleay-perl,libmime-base64-perl
  libnet-ldap-perl,libmime-base64-perl
  libnet-dns-perl,libmime-base64-perl
  libmime-perl,libmime-base64-perl 2.04
  libapache-mod-perl,libmime-base64-perl
  interchange,libmime-base64-perl
  gnatsweb,libmime-base64-perl
  catalog,libmime-base64-perl 2.11
  bioperl,libmime-base64-perl
Dependencies:
2.12-4 - perl (2 5.6.0-21) perlapi-5.6.0 (0 (null)) libc6 (2 2.2.2-2) 
libwww (0 (null)) libwww-perl (0 (null))
Provides:
2.12-4 -
Reverse Provides:
*************************************************

The Output from cpan> test Net::DNS
http://cpp.sourceforge.net/?show=11192
*************************************************


cpan> install Net::DNS //how can I reinstall a package?
Net::DNS is up to date.
*************************************************


cpan> install Mail::SpamAssassin
Mail::SpamAssassin is up to date.
*************************************************

Output from spamassassin -D:
[29218] dbg: logger: adding facilities: all
[29218] dbg: logger: logging level is DBG
[29218] dbg: generic: SpamAssassin version 3.1.0
[29218] dbg: config: score set 0 chosen.
[29218] dbg: util: running in taint mode? yes
[29218] dbg: util: taint mode: deleting unsafe environment variables, 
resetting PATH
[29218] dbg: util: PATH included '/usr/local/sbin', keeping
[29218] dbg: util: PATH included '/usr/local/bin', keeping
[29218] dbg: util: PATH included '/usr/sbin', keeping
[29218] dbg: util: PATH included '/usr/bin', keeping
[29218] dbg: util: PATH included '/sbin', keeping
[29218] dbg: util: PATH included '/bin', keeping
[29218] dbg: util: PATH included '/usr/bin/X11', which doesn't exist, 
dropping
[29218] dbg: util: final PATH set to: 
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
[29218] dbg: dns: is Net::DNS::Resolver available? yes
[29218] dbg: dns: Net::DNS version: 0.12
[29218] dbg: dns: name server: 66.28.0.45, family: 2, ipv6: 0
Here stopped the output. I dont' know why.
*************************************************

Output from spamassassin -D --lint:
http://cpp.sourceforge.net/?show=11197
*************************************************

Karsten



Re: Failed to parse

Posted by Keith Dunnett <ke...@dunnett.org>.
analyzer wrote

> Yes, i had updated the libnet-dns-perl. apt-get and cpan say its up to 
> date.

Spamassassin doesn't - so you haven't *successfully* updated it. Paste 
the full output of

    apt-cache showpkg libnet-dns-perl

then go into CPAN and run:

    test Net::DNS

Again, paste the full output. If the spamassassin installation failed 
owing to lack of Net::DNS,
then you won't even have the current version of SpamAssassin installed. 
I have a nasty feeling
that you're still testing with the old version.

1) Update Net::DNS properly and show evidence of success or failure..
2) Reinstall SpamAssassin and show that you are testing version 3.1

If you still get failures with 3.1.0 installed, then paste the 
*complete* output of
    spamassassin -D < some.message
which should be some 400 lines and will tell us most of what we need to 
know.

I do not intend to address any other errors yet; if they persist when we 
have debug output
from version 3.1 then we'll look into it. Neither Razor2 nor ident is 
mandatory for using
SpamAssassin, but razor is certainly useful.

Regards,

Keith






Re: Failed to parse

Posted by analyzer <an...@gmx.net>.
Keith Dunnett schrieb:

>
>>>
>> Net::DNS ist up to date.
>> Spamassassin say:
>> [7841] warn: dns: Net::DNS version is 0.12, but need 0.34 at 
>> /usr/local/share/perl/5.6.1/Mail/SpamAssassin/Dns.pm line 589.
>
>
> Did you update it as described in previous e-mail?
>
> apt-get update
> apt-get install libnet-dns-perl
>
>>
>> There are more errors:
>> [32544] dbg: diag: module not installed: Razor2::Client::Agent 
>> ('require' failed)
>> Warning: Cannot install Razor2::Client::Agent, don't know what it is.
>
>
> apt-get install razor
>
>>
>>
>> [32544] dbg: diag: module not installed: Net::Ident ('require' failed)
>> runtests @ARGV;' t/*.t
>> t/0use......Net::Ident::_export_hooks() called too early to check 
>> prototype at blib/lib/Net/Ident.pm line 29.
>> t/0use......ok
>> t/Ident.....Net::Ident::_export_hooks() called too early to check 
>> prototype at blib/lib/Net/Ident.pm line 29.
>> Here stopped the installation.
>
>
> apt-get install libnet-ident-perl
>
>>
>>
>> [32544] dbg: diag: module not installed: IO::Socket::INET6 ('require' 
>> failed)
>
>
> apt-get install libsocket6-perl
>
> Then go back to CPAN, and see if spamassassin installs without incident.
>
> HTH,
>
> Keith
>
>
>
>
>
Yes, i had updated the libnet-dns-perl. apt-get and cpan say its up to date.
I had installed all pachages, but spamassassin says:
[21985] dbg: diag: module not installed: Razor2::Client::Agent 
('require' failed)
[21985] dbg: diag: module not installed: IO::Socket::INET6 ('require' 
failed)

and


[5408] warn: Prototype mismatch: sub Net::Ident::_export_hooks vs () at 
/usr/share/perl5/Net/Ident.pm line 516. <<-- this error is new
[5408] warn: dns: Net::DNS version is 0.12, but need 0.34 at 
/usr/local/share/perl/5.6.1/Mail/SpamAssassin/Dns.pm line 589.

Karsten



Re: Failed to parse

Posted by Keith Dunnett <ke...@dunnett.org>.
>>
> Net::DNS ist up to date.
> Spamassassin say:
> [7841] warn: dns: Net::DNS version is 0.12, but need 0.34 at 
> /usr/local/share/perl/5.6.1/Mail/SpamAssassin/Dns.pm line 589.

Did you update it as described in previous e-mail?

apt-get update
apt-get install libnet-dns-perl

>
> There are more errors:
> [32544] dbg: diag: module not installed: Razor2::Client::Agent 
> ('require' failed)
> Warning: Cannot install Razor2::Client::Agent, don't know what it is.

apt-get install razor

>
>
> [32544] dbg: diag: module not installed: Net::Ident ('require' failed)
> runtests @ARGV;' t/*.t
> t/0use......Net::Ident::_export_hooks() called too early to check 
> prototype at blib/lib/Net/Ident.pm line 29.
> t/0use......ok
> t/Ident.....Net::Ident::_export_hooks() called too early to check 
> prototype at blib/lib/Net/Ident.pm line 29.
> Here stopped the installation.

apt-get install libnet-ident-perl

>
>
> [32544] dbg: diag: module not installed: IO::Socket::INET6 ('require' 
> failed)

apt-get install libsocket6-perl

Then go back to CPAN, and see if spamassassin installs without incident.

HTH,

Keith





Re: Failed to parse

Posted by analyzer <an...@gmx.net>.
Keith Dunnett schrieb:

>
>>>
>> There is a problem with Net::DNS. How can I update this pachages to 
>> the newest version.
>>
>> spamassassin --lint
>> [15694] warn: dns: Net::DNS version is 0.12, but need 0.34 at 
>> /usr/local/share/perl/5.6.1/Mail/SpamAssassin/Dns.pm line 589.
>
>
> First try:
>
> # apt-get update
> # apt-get install libnet-dns-perl
>
> This is the Debian way, should get you v0.48. For future reference, to 
> find unknown Debian
> packages, you can use 'apt-cache search <what>', followed by 'apt-get 
> install <packagename>'.
> Always run 'apt-get update' first, to be sure you have the latest 
> package information.
>
> If it doesn't work, here is the CPAN way:
>
> # perl -MCPAN -e shell
> # install Net::DNS
>
> Use one or the other, not both. Debian packages are preferred.
>
>>
>> Spamassassin is now installed on an other directory than befor.
>> Old: /etc/spamassassin
>> New: /etc/mail/spamassassin
>> Is that right?
>
>
> Yes. By default, spamassassin will use this directory for 
> configuration files, as described in
> 'man spamassassin'.
>
>> How can I check that spamassassin works fine?
>
>
> Feed it a bunch of spam on the commandline. e.g. save a message as 
> spam.txt and then invoke
> spamassassin as appropriate. This depends also on how you intend to 
> call it for incoming mail,
> as *that* is what needs to work.
>
> Be aware that the config options are important; the use of network 
> tests doubles the efficiency
> of SpamAssassin, so go through your config files carefully. The 
> defaults may work, but they will
> not work as well as is possible with complete configuration.
>
> Hope that helps, and wishing you the best of luck.
>
> Regards,
>
> Keith
>
> PS. If your system is that out of date, it is quite old. You might 
> like to run 'apt-get -s upgrade' to
> find out which packages the system thinks you should update.
>
>
Net::DNS ist up to date.
Spamassassin say:
[7841] warn: dns: Net::DNS version is 0.12, but need 0.34 at 
/usr/local/share/perl/5.6.1/Mail/SpamAssassin/Dns.pm line 589.

There are more errors:
[32544] dbg: diag: module not installed: Razor2::Client::Agent 
('require' failed)
Warning: Cannot install Razor2::Client::Agent, don't know what it is.
Try the command

[32544] dbg: diag: module not installed: Net::Ident ('require' failed)
runtests @ARGV;' t/*.t
t/0use......Net::Ident::_export_hooks() called too early to check 
prototype at blib/lib/Net/Ident.pm line 29.
t/0use......ok
t/Ident.....Net::Ident::_export_hooks() called too early to check 
prototype at blib/lib/Net/Ident.pm line 29.
Here stopped the installation.

[32544] dbg: diag: module not installed: IO::Socket::INET6 ('require' 
failed)

Failed 2/3 test scripts, 33.33% okay. 25/32 subtests failed, 21.88% okay.
make: *** [test_dynamic] Error 11
  /usr/bin/make test -- NOT OK
Running make install
  make test had returned bad status, won't install without force

Karsten

Re: Failed to parse

Posted by Keith Dunnett <ke...@dunnett.org>.
analyzer wrote:

> server:~# spamassassin -V
> SpamAssassin version 2.20
>
> My provider have configured the system. Perhaps there is anything false.

Perhaps you have multiple copies of SpamAssassin on the system? Try 
'whereis spamassassin'.

As Jonn said, these errors are likely to be the product of running SA 
3.1.0 without loading the
necessary modules (by reason of using an old config file). That might 
have been installed from
CPAN, rather than via Debian. The current Debian stable version is 
3.0.3-2. You might try
'apt-cache showpkg spamassassin' to find out which version Debian thinks 
it has installed.

If you don't mind managing the SpamAssassin installation yourself, you 
can usually obtain a
newer version by installing via CPAN than using Debian packages. To 
forcibly remove SA
and install the newest version, you could do the following (all as root):

1. apt-get remove spamassassin
2. whereis spamassassin
3. Delete anything still listed by 'whereis spamassassin', including 
/etc/spamassassin
4. perl -MCPAN -e shell
5. Accept the defaults to set up the CPAN shell
6. In CPAN, type 'install Mail::SpamAssassin'.
7. Exit CPAN and cd /etc/spamassassin
8. Edit the configuration files local.cf and v310.pre according to 
taste/need.
9. Test spamassassin as before.
10. When happy, google for RulesDuJour and decide whether you want it. Many
of us find that it improves the effectiveness of SpamAssassin.

This is a fairly drastic solution, but ensures that you benefit from the 
latest version. Do note
that this will no longer be upgraded for you by Debian's 'apt-get 
upgrade', so you will have
to keep an eye out for new releases and update via CPAN. It's worth the 
effort, though.

WARNING: Before doing this, make sure that you have perl 5.6.1 or 
better, which is a
requirement of spamassassin 3.x. Also, please read the upgrade notes 
available at
http://spamassassin.apache.org/full/3.1.x/dist/UPGRADE before starting; 
you might
wish to take advantage of some of the new features.

And finally, as with any such advice, make sure that you understand what 
I'm suggesting
and that it is what you want to do before you start typing commands. If 
not, read the docs
or ask further questions.

HTH,

Keith





>
>
>



Re: Failed to parse

Posted by analyzer <an...@gmx.net>.
Matt Kettler schrieb:

> At 10:18 AM 12/26/2005, analyzer wrote:
>
>> Sry, my mistake. I use version 2.20. I can't update to the newest 
>> version, beacause the confixx compatibility.
>
>
> You are not using SA 2.20.. SA didn't even support the --lint command 
> until 2.40. The fact that you could run a --lint clearly indicates 
> you're using something at least as new as 2.40.
>
> Check your version again. Preferably with spamassassin -V
>
>
>
>

server:~# spamassassin -V
SpamAssassin version 2.20

My provider have configured the system. Perhaps there is anything false.




Re: Failed to parse

Posted by Matt Kettler <mk...@comcast.net>.
At 10:18 AM 12/26/2005, analyzer wrote:
>Sry, my mistake. I use version 2.20. I can't update to the newest version, 
>beacause the confixx compatibility.

You are not using SA 2.20.. SA didn't even support the --lint command until 
2.40. The fact that you could run a --lint clearly indicates you're using 
something at least as new as 2.40.

Check your version again. Preferably with spamassassin -V




Re: Failed to parse

Posted by analyzer <an...@gmx.net>.
Sry, my mistake. I use version 2.20. I can't update to the newest 
version, beacause the confixx compatibility.

Karsten

Jonn R Taylor schrieb:

> SA 3.1.0 uses differand config option. If you look at the docs you 
> will see this. I found this when I upgraded from 2.x version.
>
> Jonn
>
>
> On Mon, 26 Dec 2005 13:37:38 +0100
>  analyzer <an...@gmx.net> wrote:
>
>> Hello everybody
>>
>> I would like check that my spamassassin installation run fine. I use 
>> a debian server system with the newest spamassassin version and all 
>> debian updates.
>>
>> spamassassin -D < test.text
>> The follow errors output:
>> debug: Failed to parse line in SpamAssassin configuration, skipping: 
>> report_safe             1
>> debug: Failed to parse line in SpamAssassin configuration, skipping: 
>> use_bayes               1
>> debug: Failed to parse line in SpamAssassin configuration, skipping: 
>> auto_learn              1
>> debug: Failed to parse line in SpamAssassin configuration, skipping: 
>> use_razor2              1
>> debug: Failed to parse line in SpamAssassin configuration, skipping: 
>> use_dcc                 1
>> debug: Failed to parse line in SpamAssassin configuration, skipping: 
>> use_pyzor               1
>> debug: Failed to parse line in SpamAssassin configuration, skipping: 
>> ok_languages            all
>> debug: Failed to parse line in SpamAssassin configuration, skipping: 
>> user_scores_sql_table          spampref
>>
>> A part of my local.cf:
>>
>> #
>> required_hits           5.0
>>
>> # Whether to change the subject of suspected spam
>> rewrite_subject         1
>>
>> # Text to prepend to subject if rewrite_subject is used
>> subject_tag             *****SPAM*****
>>
>> # Encapsulate spam in an attachment
>> report_safe             1
>>
>> # Use terse version of the spam report
>> use_terse_report        0
>>
>> # Enable the Bayes system
>> use_bayes               1
>>
>> # Enable Bayes auto-learning
>> auto_learn              1
>>
>> # Enable or disable network checks
>> skip_rbl_checks         0
>> use_razor2              1
>> use_dcc                 1
>> use_pyzor               1
>>
>> # Mail using languages used in these country codes will not be marked
>> # as being possibly spam in a foreign language.
>> ok_languages            all
>>
>> # Mail using locales used in these country codes will not be marked
>> # as being possibly spam in a foreign language.
>> ok_locales              all
>>
>> I can't find any mistakes. Where is the problem?
>>
>> Thanks
>>
>> Karsten
>
>
>