After updating perl and running perl-cleaner --all, I get this error when trying to start MailScanner :
* Starting MailScanner ...
Can't load '/usr/lib/perl5/5.12.2/i686-linux/auto/Compress/Raw/Zlib/Zlib.so' for module Compress::Raw::Zlib: /usr/lib/perl5/5.12.2/i686-linux/auto/Compress/Raw/Zlib/Zlib.so: undefined symbol: deflateTune at /usr/lib/perl5/5.12.2/i686-linux/DynaLoader.pm line 200.
at /usr/lib/perl5/vendor_perl/5.12.2/Archive/Zip.pm line 12
Compilation failed in require at /usr/lib/perl5/vendor_perl/5.12.2/Archive/Zip.pm line 12.
BEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/5.12.2/Archive/Zip.pm line 12.
Compilation failed in require at /usr/lib/MailScanner/MailScanner/Message.pm line 48.
BEGIN failed--compilation aborted at /usr/lib/MailScanner/MailScanner/Message.pm line 48.
Compilation failed in require at /usr/sbin/MailScanner line 108.
BEGIN failed--compilation aborted at /usr/sbin/MailScanner line 108. [ !! ]
My gentoo kernel version is :
Linux t-rex 2.6.35-gentoo-r4 #4 PREEMPT Sun Aug 29 19:36:27 EEST 2010 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz GenuineIntel GNU/Linux
Steps to Reproduce:
1.Install MailScanner 220.127.116.11
2.Update to perl 5.12.2-r1
3./etc/init.d/MailScanner restart or reboot
Same thing happened with older version of MailScanner whick worked just before updating to the new perl version.
*** Bug 343321 has been marked as a duplicate of this bug. ***
MailScanner is not in Portage. Report it to upstream.
You did run 'perl-cleaner --all' after upgrading to perl-5.12.2 didn't you?
course, I did. I ran perl-cleaner -all. The problem is that indeed MailScanner is not in portage but a friend of mine runs it perfectly well on a gentoo linux server even after updating perl. And it used to work fine before the perl upgrade on gentoo box as well.
I might try contacting the developer of MailScanner, see if I get something out of it. For the time being I cannot access my mail, even though postfix is getting them.
Downgraded to 5.8.8-r8 and all seems to be working now. There seems to some issue with perl-5.12.2 here!!