<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<META content="MSHTML 6.00.2900.5512" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt tahoma">
<DIV>Does this mean that the existing method of installing MailScanner (i.e. going to mailscanner.info / downloading the installer for MailScanner) is going away?</DIV>
<DIV> </DIV>
<DIV><BR><BR>>>> Julian Field <MailScanner@ecs.soton.ac.uk> 9/18/2008 9:02 AM >>><BR>* What is it?<BR><BR>This is a new Yum repository for CentOS 5 i386 and x86_64 only. It will <BR>always contain the latest MailScanner beta (4.72.2 at the time of <BR>writing) along with SpamAssassin (plus DCC, Razor, DKIM, SPF, IP-Country <BR>and Rule2XS plug-ins), ClamAV and all Perl module dependencies.<BR><BR>It should be used for beta testing new releases only and should not be <BR>used in production.<BR><BR>* Why is it different from other repositories?<BR><BR>Because it aims to completely eliminate the problem of package conflicts <BR>and to make installations and upgrades as simple as possible. These rpms <BR>provide an automatic configuration that contains the regular tuning tips <BR>that would be unfamiliar to those who do not have in-depth knowledge of <BR>MailScanner and it's configuration. This significantly reduces the <BR>amount of time it takes to do an installation. From start to finish, the <BR>installation and configuration of all packages takes less than five <BR>minutes on a reasonably fast network.<BR><BR>Package conflicts are avoided by creating a new RPM namespace for all <BR>the Perl modules required by MailScanner and SpamAssassin and by <BR>installing all Perl modules (except SpamAssassin) in <BR>/opt/fsl/lib/perl5. This allows the Perl system libraries to be totally <BR>independent so they can be updated by the operating system vendor <BR>without the possibility of breaking MailScanner or SpamAssassin.<BR><BR>Automatic configuration is achieved by using RPM 'triggers' which allow <BR>the installation, upgrade or un-installation of one package trigger to <BR>access an action specified by another package. For example - when <BR>'re2c' is installed, the fsl-spamassassin package runs a trigger that <BR>automatically runs 'sa-update' and 'sa-compile' to get the latest rules <BR>and compile them and then automatically enables the 'Rule2XSBody' <BR>plug-in in v320.pre, subsequently if 're2c' is uninstalled, then the <BR>plug-in is automatically disabled.<BR><BR>* Installation procedure<BR><BR>Ideally it should be installed onto a server with a fresh minimal <BR>installation of CentOS/RHEL 5. This will allow the operating system and <BR>all MailScanner related applications to be safely updated by simply <BR>running `yum -y update`.<BR><BR>If you want the MailScanner package to automatically mount the <BR>MailScanner incoming directory on tmpfs then run the following command <BR>before starting the installation:<BR> export MAILSCANNER_CREATE_TMPFS=1<BR><BR>Then simply run:<BR><BR> wget <A href="http://yum.fslupdate.com/fsl-beta/fsl-beta.repo">http://yum.fslupdate.com/fsl-beta/fsl-beta.repo</A> -O <BR>/etc/yum.repos.d/fsl-beta.repo<BR> yum -y groupinstall MailScannerGold<BR> export PERL5LIB=/opt/fsl/lib/perl5<BR><BR>Once all the packages are installed, the only configuration required is <BR>to MailScanner.conf, Sendmail (/etc/mail/access, /etc/mail/mailertable) <BR>and then enable and start them both by running:<BR><BR> chkconfig MailScanner on<BR> service MailScanner start<BR><BR>* Installing over an existing RPM based installation<BR><BR>This is no different to the procedure above - except you should back-up <BR>your MailScanner and SpamAssassin configuration first as a precaution. <BR>The 'stock' MailScanner package has no automatic upgrade procedure you <BR>will need to manually run upgrade_MailScanner_conf and/or <BR>upgrade_languages_conf if any rpmnew files are created by the new package.<BR><BR>* Support<BR><BR>Sign-up for the fsl-beta support list at <BR><A href="http://listserv.fsl.com/mailman/listinfo/fsl-mailscanner-beta.">http://listserv.fsl.com/mailman/listinfo/fsl-mailscanner-beta.</A><BR><BR>The use of the repository is entirely unsupported by FSL, so use is at <BR>your own risk - however we will be happy to answer and questions about <BR>the repository or packages on the fsl-beta list.<BR><BR>* MailScannerGold PRODUCTION<BR><BR>The MailScannerGold Production yum repository will be available in a few <BR>days. We'll post another announcement when it's available for <BR>subscription and downloading.<BR><BR>Initial pricing for the production version subscription is a monthly fee <BR>of $30 / month for the first gateway and $20 / per month for each <BR>additional gateway. This should help us to recover our costs for <BR>development and maintenance while at the same time costing sites less <BR>that the salaries required for administrators to fully maintain and <BR>update the MailScanner systems.<BR><BR>Support for MailScannerGold PRODUCTION will provided by a subscribers <BR>supported and FSL moderated email list. Subscribers to the service will <BR>also be able to obtain FSL support services at our standard hourly rates <BR>less a 25% discount.<BR><BR>These repositories should make installing, running and updating <BR>MailScanner a lot easier for both newbes and experienced mail <BR>administrators.<BR><BR>Jules<BR>-- <BR>Julian Field MEng CITP CEng<BR>Chief Technical Officer<BR>Fort Systems Ltd.<BR><BR><BR>-- <BR>This message has been scanned for viruses and<BR>dangerous content by MailScanner, and is<BR>believed to be clean.<BR><BR>-- <BR>MailScanner mailing list<BR>mailscanner@lists.mailscanner.info<BR><A href="http://lists.mailscanner.info/mailman/listinfo/mailscanner">http://lists.mailscanner.info/mailman/listinfo/mailscanner</A><BR><BR>Before posting, read <A href="http://wiki.mailscanner.info/posting">http://wiki.mailscanner.info/posting</A><BR><BR>Support MailScanner development - buy the book off the website! <BR></DIV></BODY></HTML>