Just in case I installed from source the Net::DNS module, and it still
does the same thing. But it was a long shot since this whole server
was setup this morning from yum installs. I also change the name
servers in resolve.conf and I got the same result. Arg this is so
annoying, this is like the last thing before this is done.
On 11/4/06, Dan McCullough <[EMAIL PROTECTED]> wrote:
So possibly if I point it to another set of DNS server it might be
okay? If not are there any other suggestions?
On 11/4/06, jdow <[EMAIL PROTECTED]> wrote:
>
> ----- Original Message -----
> From: "Dan McCullough" <[EMAIL PROTECTED]>
> To: "jdow" <[EMAIL PROTECTED]>
> Sent: Saturday, November 04, 2006 14:27
> Subject: Re: spamassassin --lint fails - undefined symbol
>
>
> > As far as I know DNS module is installed.
> >
> > Here is the complete output.
> >
> > ############################################################
> >
> > su amavis -c 'spamassassin --lint -D'
> file /usr/share/spamassassin/60_whitelist_subject.cf
> ...
> > [3901] dbg: bayes: tie-ing to DB file R/O
/var/amavis/.spamassassin/bayes_toks
> > [3901] dbg: bayes: tie-ing to DB file R/O
/var/amavis/.spamassassin/bayes_seen
> > [3901] dbg: bayes: found bayes db version 3
> > [3901] dbg: bayes: DB journal sync: last sync: 0
> > [3901] dbg: config: using "/var/amavis/.spamassassin" for user state dir
> > [3901] dbg: bayes: not available for scanning, only 0 spam(s) in bayes DB <
200
> > [3901] dbg: bayes: untie-ing
> > [3901] dbg: bayes: untie-ing db_toks
> > [3901] dbg: bayes: untie-ing db_seen
>
> Your Bayes is completely untrained for what that is worth.
>
> > [3901] dbg: dns: name server: 64.80.203.201, family: 2, ipv6: 0
> > [3901] dbg: dns: testing resolver nameservers: 64.80.203.201,
> > 64.80.203.194, 64.80.255.240
> > [3901] dbg: dns: trying (3) google.com...
> > [3901] dbg: dns: looking up NS for 'google.com'
> > /usr/bin/perl: symbol lookup error:
> >
/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/auto/Net/DNS/DNS.so:
> > undefined symbol: Perl_sv_2uv_flags
>
>
> Not being an expert I'd initially guess you are running a version of
> Net:DNS that is too old for SpamAssassin. Second guess would be a DNS
> server that is incompatible with SpamAssassin. There are several that
> return intentionally doctored data and as such are incompatible with
> SpamAssassin. Due to Earthlink's extreme misbehavior I run a caching
> server off the root servers here. And I use plain old bind, none of
> the holier than thou newer stuff.
>
> {^_^}
>
