Sorry for replying to my own post....
#######
ADDITIONAL NOTE:

I think it's because amavis is using /usr/lib/perl5/vendor_perl/5.8.3/ 
and everything else uses /usr/lib/perl5/site_perl/5.8.3/


#######

>>>And it sounds like you don't get SURBL detection even when you
>>send unmunged testpoints into the system.

>>>Jeff C.

>>It may have something to do with the way amavisd calls spamassassin,
maybe. 

>>I've tried to use cpan to re-install SpamCopURI, but it just says its upto
>>date, I installed it originally by downloading it... and following the
>>instructions in the install file.


>Make sure to run the 'spamassassin...' under the same user
>as amavisd is running (e.g. su vscan -c 'spamassassin -t ...')

[EMAIL PROTECTED] tester]# su amavis -c 'spamassassin -t'
Can't locate Mail/SpamAssassin/SpamCopURI.pm in @INC (@INC contains: lib
/usr/li
b/perl5/site_perl/5.8.3 /usr/lib/perl5/5.8.3/i386-linux-thread-multi
/usr/lib/pe
rl5/5.8.3 /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi
/usr/lib/perl5/
site_perl /usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi
/usr/lib/perl
5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl/5.8.1/i386-linux-thread-multi
/us
r/lib/perl5/vendor_perl/5.8.1 /usr/lib/perl5/vendor_perl) at
/usr/lib/perl5/vend
or_perl/5.8.3/Mail/SpamAssassin/PerMsgStatus.pm line 41.
BEGIN failed--compilation aborted at
/usr/lib/perl5/vendor_perl/5.8.3/Mail/SpamA
ssassin/PerMsgStatus.pm line 41.
Compilation failed in require at
/usr/lib/perl5/vendor_perl/5.8.3/Mail/SpamAssas
sin.pm line 62.
BEGIN failed--compilation aborted at
/usr/lib/perl5/vendor_perl/5.8.3/Mail/SpamA
ssassin.pm line 62.
Compilation failed in require at /usr/bin/spamassassin line 66.

I changed the permissions on SpamCopURI.pm (gave it read :-) ) but then i
got the 
errors below


>You may also try: amavisd debug-sa
>and verify that the SA paths are correct,
>and check any comments it may utter on DNS or SpamCopURI.

That all seems fine... in as much as there is not mention of SpamCopURI and
there
are no errors.

>If you haven't specified $daemon_chroot_dir, then it is not.

It isnt chrooted. 


There are 3 locations with Conf.pm, PerMsgStatus.pm and SpamCopyURI.pm, and
they are 
all the same versions as the ones that come with SpamCopURI. 

AmavisD doesnt pickup SpamCopURI at all.

Weirdness '[EMAIL PROTECTED] tester]spamassassin -tD <test2' works...!

spamassassin -V gives 2.64

If in cpan i do install Mail::SpamAssassin it says 'up to date'

 'su amavis -c 'spamassassin -tD <test1' reports......

configuration file "/usr/share/spamassassin/20_body_tests.cf" requires
version 2
.64 of SpamAssassin, but this is code version 2.63. Maybe you need to use
the -C
 switch, or remove the old config files? Skipping this file at
/usr/lib/perl5/ve
ndor_perl/5.8.3/Mail/SpamAssassin/Conf.pm line 362.

Conf.pm [line 362...]
   if (/^require_version\s+(.*)$/) {
      my $req_version = $1;
      $req_version =~ s/[EMAIL PROTECTED]@[EMAIL 
PROTECTED]@$/$Mail::SpamAssassin::VERSION/;
      if ($Mail::SpamAssassin::VERSION != $req_version) {
        warn "configuration file \"$self->{currentfile}\" requires version
".
                "$req_version of SpamAssassin, but this is code version ".
                "$Mail::SpamAssassin::VERSION. Maybe you need to use ".
                "the -C switch, or remove the old config files? ".
                "Skipping this file";
        $skipfile = 1;


I'm so close to getting it work... arrghh

Cheers,
Kristian


---------------------------------------------------------------------------
The information transmitted is intended only for the
person or entity to which it is addressed and may
contain confidential and/or privileged material. 
Any review, retransmission, dissemination or other
use of, or taking of any action in reliance upon, this
information by persons or entities other than the
intended recipient is prohibited.  If you received this
in error, please contact the sender and delete the
material from any computer.
---------------------------------------------------------------------------

Reply via email to