Discussion:
Required perl modules
Stef Morrell
2013-08-07 14:26:11 UTC
Permalink
Hello List,

It's been a while since I did a MailScanner install. In those days the "current" PERL was 5.8

Today, we're at 5.18!

I followed the familiar procedure, downloading the tarball for "other" unix and running install.sh, but it does appear that the changes made in the base PERL install have brought in a lot of problems with the modules shipped with MS.

Looking at http://www.mailscanner.info/perl.html I can see the same rather elderly set of perl module versions.

Can I simply install latest versions of all of these manually, or are there specific versions I need to be looking at?

I've included a zipped copy of the install log for your delectation. As you can see, most of the included modules do install quite happily, but there are some that don't, sometimes something (more) complicated (than I can work out), sometimes something as simple as a deprecated feature. The failures include HMTL-Parser, which is obviously crucial.

I am also slightly worried about other server roles which may depend on perl (even Nagios client needs some modules) needing more up to date versions and possible conflicts.

I suppose the same question should be applied in terms of the "install-clam-sa" tarball. The clam version is certainly out of date. Is that simply a collection of sa dependancies and in that case is it fine to just install the appropriate modules as indicated in the SA documentation. As for clam, I guess I can rip the configure command out of the script and build that manually with little trouble.
--
Stefan Morrell????????? | Operations Director
Tel: 0843 4532820?????? | Alpha Omega Computers Ltd
Fax: 0843 4532830?????? | Incorporating Level 5 Internet
stef at aoc-uk.com???????? | stef at l5net.net
?
Standard Disclaimer: http://www.aoc-uk.com/aoc_email_terms.html
?
Alpha Omega Computers Ltd, Batley Business Park, Grange Road, Batley, WF17 6ER.
Registered in England No. 3867142.? VAT No. GB734421454


-------------- next part --------------
A non-text attachment was scrubbed...
Name: install.log.zip
Type: application/x-zip-compressed
Size: 21072 bytes
Desc: install.log.zip
Url : http://lists.mailscanner.info/pipermail/mailscanner/attachments/20130807/b5869e84/attachment.bin
Christopher Meng
2013-08-07 15:30:21 UTC
Permalink
Upstream think older is more stable... ;)

I may try packaging it into modern systems like Fedora later.

Maybe more issues are still hidden...

Sent from Note I
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mailscanner.info/pipermail/mailscanner/attachments/20130807/842064ed/attachment.html
Stef Morrell
2013-08-07 15:40:30 UTC
Permalink
Upstream think older is more stable...? ;)
Older PERL version, or PERL modules?

I have experienced a massive performance drop off with 5.16.2 which I hope might be cured with 5.18.

I can't really go back to 5.8 as other applications (like that pesky nagios client) require modules which hate 5.8, so I'm stuck really.

Maybe I could try 5.10 or 5.12.
Barry Callahan
2013-08-07 16:50:36 UTC
Permalink
I did.
Post by Stef Morrell
Hello List,
Can I simply install latest versions of all of these manually, or are
there specific versions I need to be looking at?
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
M A Young
2013-08-08 09:34:58 UTC
Permalink
Post by Stef Morrell
It's been a while since I did a MailScanner install. In those days the
"current" PERL was 5.8
...
Can I simply install latest versions of all of these manually, or are
there specific versions I need to be looking at?
We don't use any of the RPMs in the install tarball except mailscanner on
our CentOS 6 servers, using instead ones shipped with CentOS, or from EPEL
or rpmforge. We also stopped running the install.sh script and just
install the RPMs directly.

Michael Young
Christopher Meng
2013-08-08 10:25:51 UTC
Permalink
? 2013-8-8 PM6:07?"M A Young" <m.a.young at durham.ac.uk>???
Post by M A Young
We don't use any of the RPMs in the install tarball except mailscanner on
our CentOS 6 servers, using instead ones shipped with CentOS, or from EPEL
or rpmforge. We also stopped running the install.sh script and just
install the RPMs directly.
Can it work correctly?

I'm preparing packages for Fedora 20+ and RHEL6,7.

Sent from Note I
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mailscanner.info/pipermail/mailscanner/attachments/20130808/40d5486d/attachment.html
Kai Schaetzl
2013-08-19 12:49:18 UTC
Permalink
Post by Christopher Meng
Can it work correctly?
Sure. I've been doing this for years. Just install the mailscanner*.rpm.
Anything else can be used from the system. Same for SA and clamav. Some
modules need to be updated versions than the base system, of course.



Kai
--
Get your web at Conactive Internet Services: http://www.conactive.com
Christopher Meng
2013-08-19 14:49:43 UTC
Permalink
? 2013-8-19 PM9:33?"Kai Schaetzl" <maillists at conactive.com>???
Post by Kai Schaetzl
Sure. I've been doing this for years. Just install the mailscanner*.rpm.
Anything else can be used from the system. Same for SA and clamav. Some
modules need to be updated versions than the base system, of course.
Thanks, I'll get ms into Fedora/EPEL soon.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mailscanner.info/pipermail/mailscanner/attachments/20130819/cbbd5cae/attachment.html
Peter Bonivart
2013-08-08 10:23:11 UTC
Permalink
Post by Stef Morrell
Can I simply install latest versions of all of these manually, or are there specific versions I need to be looking at?
For Solaris I just used the tarball and installed the latest available
version of the required modules. No problems at all.
Loading...