[csw-users] Problems with MailScanner

[Peter Bonivart]

The first problem is only for those of you running Solaris 8, the
pre/post-scripts have a feature in them that is only supported in
Solaris 9 and 10. You should upgrade to 4.65,REV=2008.01.04. It's on
its way to unstable but can be found in testing for manual upgrade:

http://www.blastwave.org/testing/mailscanner-4.65.3.1,REV=2008.01.04-SunOS5.8-all-CSW.pkg.gz

The second problem is much more serious. Upgrades of the perl modules
mailtools and mimetools broke MailScanner 4.65 and it hit a lot of
Linux users quick to upgrade their systems. We still had version 1.71
of mailtools and 5.420 of mimetools so we were OK but for MailScanner
4.66 to work OK we needed version 2.02 and 5.425 of those modules and
they were built quickly by their maintainers. That in combination with
problems with a third perl module (IO) made both MailScanner 4.65 and
4.66 problematic for us.

What this means is that if you upgrade mailtools and mimetools, either
separately or by doing a full upgrade, you will end up with a broken
MailScanner 4.65 that will not start. I have prepared a temporary
package for MailScanner 4.66 in testing that has workarounds for the
third problem with the IO module.

http://www.blastwave.org/testing/mailscanner-4.66.5.2-SunOS5.8-all-CSW.pkg.gz
http://www.blastwave.org/testing/pm_io-1.2301-SunOS5.8-sparc-CSW.pkg.gz
http://www.blastwave.org/testing/pm_io-1.2301-SunOS5.8-i386-CSW.pkg.gz

We will soon have a new Perl package that will include IO 1.2301 which
is needed by MailScanner 4.66. Then I will release a new package to
unstable that will not need the separate IO package.

You have two choices:

1. Do not upgrade anything on your systems related to MailScanner.
Wait for MailScanner 4.66 to get into unstable.
2. Use the temporary MailScanner 4.66 and IO package from testing.

I only recommend 2 if you already have a broken system or you
absolutely must have version 4.66.

-- 
/peter