(Please see the following post before upgrading if you are using multiple AV scanners)
viewtopic.php?f=13&p=6953
This minor update includes a few fixes since the 3.0.1.2 release.
VMware Image:
https://dl.efa-project.org/build/3.0.1. ... VMware.zip
Size: 769.24 MiB
MD5: 8c4fba9d6bc671bdcf8098b7a69ec380
SHA1: 45bbc7826d45ddf1a675ff525f823c0186e7ce39
(Hyper-V build is pending...)
Updates is available from prior versions now.
The following issues have been fixed in 3.0.1.3:
Issue #308 Bug - ClamAV Status Page blank
Issue #309 Bug - Anacron daily notifications from mailscanner
Issue #311 Bug - Quarantine Permissions Issue in 3.0.1.2
Issue #312 Bug - MailScanner access to EFA-Config denied
Updated clamav, clamd, mysql, and mysql-server
The following issues have been fixed in 3.0.1.2:
Issue #92 Bug/Enhancement - Mailwatch Single Recipient Release
Issue #165 Enhancement - Upgrade MailScanner
Issue #206 Enhancement - Default Max Archive Depth to Non Zero
Issue #210 Enhancement - Add EFA Version to GUI
Issue #228 Bug - Greylist toggle overwrites custom smtpd_recipient_restrictions
Issue #232 Enhancement - Use CLAMAV-UNOFFICIAL-SIGS maintained by eXtremeSHOK.com
Issue #239 Enhancement - Add TxRep Config for SA 3.4.1
Issue #265 Enhancement - Add per user mode for MailWatch
Issue #267 Bug - SPAM bounce loop
Issue #275 Bug - MailWatch updater adds duplicate SHOW_GREYLIST definitions
Issue #284 Enhancement - Lower ImageCerberus Scores by default
Issue #276 Bug - EFA-Configure Option 11 logic error
Issue #286 Bug - Postmaster set to empty interferes with postfix
Issue #287 Regression - Rules without Descriptions (removed from beta)
Issue #294 Bug - Attachment Release Issues in MailWatch
Issue #297 Bug - KAM.cf URL needs updated
Issue #306 Enhancement - EFA-Monitor alert enhancement
Please review the RELEASENOTES prior to updating for important information:
https://raw.githubusercontent.com/E-F-A ... LEASENOTES
It is recommended that you suspend your mail flow and snapshot prior
to updating or to back up the entire appliance.
1) Stop mail flow temporarily (at firewalls/mailservers)
2) Snapshot your VM and its memory using your hypervisor tools
3) If the update fails for any reason, immediately roll back to snapshot
4) Report failure at https://forum.efa-project.org
Log into a console or shell section and use EFA-Configure.
Choose option 14) Upgrade
To manually launch from shell:
Code: Select all
sudo /usr/local/sbin/EFA-Configure
happens, the script will halt to give you an opportunity to restart.
After restarting and booting to the new kernel, rerun EFA-Update to
continue the update process to 3.0.1.3.
EFA-Update will not proceed until you are running on the latest
kernel. This is to ensure that open-vm-tools updates appropriately
if present.