Nicklas, > However it seems to play nice now after I renamed some perl folders > (/usr/local/share/perl/5.8.4 > /usr/local/share/perl/5.8.8 and > /usr/local/share/perl/5.8.4 > /usr/local/share/perl/5.8.8
That is not a good practice. Perl modules should be reinstalled after an upgrade of Perl. Keeping an old module may or may not work. Modules which are pure-perl are probably fine, but those that bring along C code and libraries are likely to cause trouble. > and also forced a rebuild of perl BerkeleyDB from CPAN. Always rebuild a Perl interface module when upgrading an undelying library, e.g. libdb->BerkeleyDB, mysql->DBD::mysql, PostgreSQL->DBD::Pg, zlib->Compress::Zlib, ldap->Net::LDAP, etc. Mark ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ AMaViS-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
