Trimming the fat from MailScanner
kevin.miller at juneau.org
Mon Feb 8 17:48:27 UTC 2016
What is the expected behavior for an upgrade? As the new version won't have the update programs any more will it remove the older copies and revert the update process back to "factory specs" for the respective packages, i.e. antivirus and spamassassin?
I think that would be fine, but if not it may be helpful to include some verbiage in the script describing what should be done to manually roll back the update processes.
Network/email Administrator, CBJ MIS Dept.
155 South Seward Street
Juneau, Alaska 99801
Phone: (907) 586-0242, Fax: (907) 586-4500 Registered Linux User No: 307357
From: MailScanner [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Jerry Benton
Sent: Saturday, February 06, 2016 12:58 AM
To: MailScanner Discussion
Subject: Trimming the fat from MailScanner
Here I sit creating the RPM build and I am thinking that there are some items that just are not needed anymore. For example, we donât update_virus_scanners nor do we need update_spamassassin. I donât know of any virus scanner package that does not have its own update platform. The same is true Spamassassin. sa-compile will automatically do what is needed as long as you have re2c installed and the Rule2XSBody module installed and loaded.
So in addition to standardizing the directory structure across all platforms, I am also removing these scripts. They are far beyond their expiration date.
I am also removing processing_messages_alert from being in any cron by default.
MailScanner mailing list
mailscanner at lists.mailscanner.info
More information about the MailScanner