The 3.0.2.5 update is now available.

We would also like to thank everyone for their support and contributions to this project.

The following issues have been fixed (hopefully) in 3.0.2.5:

Issue #324 Enhancement – Import external backup to new EFA device
Issue #361 Enhancement – Display EFA version in the CLI via EFA-Configure
Issue #385 Bug – Changed from reload to restart for Postfix
Issue #386 Bug – Admin cannot modify domain admin accounts
Issue #387 Enhancement – Updated MariaDB recovery script

Enhancement – Let’s Encrypt
Enhancement – Add EFA sponsored DCC servers
Enhancement – Hypervisor detection during init
Enhancement – MailScanner update to 5.0.6-5
Enhancement – MailWatch updated to latest develop
Enhancement – clamav-unofficial-sigs updated to 5.6.2
Security – Regenerate self signed certs for Postfix/Apache/Webmin
Security – Enabled strong cipher preference in Postfix
Security – Enabled strong cipher preference in Apache
Bug – Left the disabling of modsecuirty fix enabled, as new builds of 3.0.2.4 still have it enabled by default
Bug – Updated menu options for “Apache Settings” menu
Bug – Quarantine report to flip from HTTP to HTTPS
Bug – Update quarantine FROM_ADDR to use POSTMASTER address in /etc/EFA-Config

###################### How To Update ##################################

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, collect relevant logs or screen
outputs/screenshots and revert to your snapshot
4) Report failure at https://forum.efa-project.org

Launch EFA-Configure from console or secure shell

(sudo /usr/local/sbin/EFA-Configure)

Choose option 14) Update Now

The first time you run this update, the kernel may update. If this
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.2.5.

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.