Frank Niedermann schrieb:
Hi,
on a fresh Debian 4.0 installation with Spamassassin 3.1.7 I get to
following message:
Oct 2 06:01:20 zoidberg spamd[17975]: spamd: connection from localhost
[127.0.0.1] at port 58519
Oct 2 06:01:21 zoidberg spamd[17975]: spamd: processing message
<[EMAIL PROTECTED]> for
[EMAIL PROTECTED]:2000
Oct 2 06:01:25 zoidberg spamd[17975]: pyzor: check failed: Can't fork at
/usr/share/perl5/Mail/SpamAssassin/Util.pm line 1308.
[1]
Oct 2 06:01:27 zoidberg spamd[17975]: spamd: identified spam (1001.9/6.5)
for [EMAIL PROTECTED]:2000 in 6.3 seconds, 1959 bytes.
Spam mail is getting recognized, I've tried with the GTUBE test. But
something seems to be wrong with starting the pyzor checks, does anybody
know why?
How do you call pyzor?
Perhaps you find hints with:
spamassassin -D
spamassassin -d [ < mailmessage | path ... ]
as described in "man 3 spamassassin"
btw:
Debian Etch too here:
ii perl 5.8.8-7
ii perl-base 5.8.8-7 The Pathologically Eclectic Rubbish Lister
ii perl-modules 5.8.8-7 Core Perl modules
ii spamassassin 3.1.7-2 Perl-based spam filter using text analysis
But i call SA from:
ii amavisd-new 2.4.2-6.1
dunno if it makes a difference in this case ...
[1] Perhaps someone could help:
How could i show/jump to line 1308 of Util.pm and more important are the
"comments "##"" counted as lines or not?
(I tried "less" with the command "g" but not sure if it jumped to the
exact position)
Regards,
Frank
--
Grüsse/Greetings
MH
Dont send mail to: [EMAIL PROTECTED]
--
