Hey list,

I could not find too much info about the following issue on the list. 
Hopefully someone can help me out:

I've just pushed an upgrade of my SA 2.64 setup to 3.0.1. I wanted to benefit 
from the new features, uridnsbl in particular.

I've done this kind of setup on a Gentoo box, and it worked without any 
hurdles. The mail server I'm trying to set this up onto is a sparc solaris 9 
system running Perl 5.8.0. Both of these installs are being performed on 
Postfix / amavisd-new setup. I'm no beginner to SA: I've done a few setups as 
a sideline.

The uridnsbl.pm module is indeed located in the right place. A quick test with 
one of the blacklisted domains on surbl.org triggers Razor2 tests, suggesting 
that the network tests are operational, but not uridnsbl.

Where the Gentoo system outputs the following (when starting amavis in debug 
mode):

##########
debug: config: read file /etc/mail/spamassassin/local.cf
debug: using "/var/run/amavis/.spamassassin/user_prefs" for user prefs file
debug: plugin: loading Mail::SpamAssassin::Plugin::URIDNSBL from @INC
debug: plugin: registered Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x9459d78)
debug: plugin: loading Mail::SpamAssassin::Plugin::Hashcash from @INC
debug: plugin: registered Mail::SpamAssassin::Plugin::Hashcash=HASH(0x945508c)
debug: plugin: loading Mail::SpamAssassin::Plugin::SPF from @INC
debug: plugin: registered Mail::SpamAssassin::Plugin::SPF=HASH(0x85a1c90)
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x9459d78) implements 
'parse_config'
debug: plugin: Mail::SpamAssassin::Plugin::Hashcash=HASH(0x945508c) implements 
'parse_config'
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x9459d78) inhibited 
further callbacks
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x9459d78) inhibited 
further callbacks
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x9459d78) inhibited 
further callbacks
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x9459d78) inhibited 
further callbacks
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x9459d78) inhibited 
further callbacks
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x9459d78) inhibited 
further callbacks
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x9459d78) inhibited 
further callbacks
debug: bayes: 9039 tie-ing to DB file 
R/O /var/run/amavis/.spamassassin/bayes_toks
debug: bayes: 9039 tie-ing to DB file 
R/O /var/run/amavis/.spamassassin/bayes_seen
##########

... the Solaris system skips from the "user_prefs" line to the bayes lines.

I'm at a lost here. Is it possible that this @INC search path doesn't include 
the folder where uridnsbl, hashcash and SPF are located? I'm not a perl 
expert, and I have no clue on how/if I can change amavisd's @INC to reflect 
the proper path for these modules.

Can anyone help me out? I'm sorry, perhaps this should have been posted on the 
amavis mailing list. However, I know that there are loads of amavis experts 
here.

Thanks!!

-- 
Mathieu Nantel, RHCE - Systems Manager
Ecopia BioSciences Inc.
(514) 336-2724 x434

Reply via email to