efa-project.org

I am looking at making a backup of the complete appliance,
then updating the underlying centos system,
then going to the EFA console an selecting option: 14) Update Now

to update my EFA 3.0.1.1 to 3.0.1.3

If the update goes smooth I need to check if my customizations are all still in place.
Is there a list of which files get overwritten by an EFA update?
I'm talking about config files and template files, etc.
After all, I do have the backup to restore them from, I just need to know what gets overwritten.

You don't use EFA as a VM appliance? -> Snapshot and everything is fine.

@DaN: did you read my first sentence?

I am looking at making a backup of the complete appliance

Is the appliance virtual or physical?

ovizii wrote:Is there a list of which files get overwritten by an EFA update?
I'm talking about config files and template files, etc.
After all, I do have the backup to restore them from, I just need to know what gets overwritten.

Here you go:

3.0.1.2 Update (https://github.com/E-F-A/v3/blob/3.0.1. ... de-3.0.1.2)

Old clamav-unofficial-sigs backed up to /var/EFA/backup/3.0.1.2 and removed.
Old MailScanner backed up to /var/EFA/backup/3.0.1.2
EFA-Configure backed up using EFA-Backup and updated
MailWatch backed up and updated (configs preserved and updated)
MailScanner updated (configs preserved and updated)
/etc/MailScanner/filename.rules created
/etc/MailScanner/filetype.rules created
/etc/MailScanner/rules/content.scanning.rules created
/etc/MailScanner/filetype.rules.allowall.conf created
Miscellaneious config updates as needed for MailScanner/Spamassassin

3.0.13 Update (https://github.com/E-F-A/v3/blob/3.0.1. ... de-3.0.1.3)

Permissions changes to /var/spool/MailScanner/incoming and quarantine
Add apache to mtagroup
Config updates to /etc/MailScanner/MailScanner.conf to support above changes
/etc/cron.daily/mailscanner modified to suppress cron output

Hi there,

it is a virtual appliance. I had found the changelog on my own, so looking at what shawn posted I understand that I do not need to worry about any Mailwatch configs and customizations:

MailWatch backed up and updated (configs preserved and updated)
MailScanner updated (configs preserved and updated)

Slightly unclear if I will lose any configs in this step:

Miscellaneious config updates as needed for MailScanner/Spamassassin

Can I safely assume the following?
- my stuff inside /etc/mail/spamassassin is safe
- everything I customized inside /etc/MailScanner/ will be safe

ovizii wrote:Hi there,

Can I safely assume the following?
- my stuff inside /etc/mail/spamassassin is safe
- everything I customized inside /etc/MailScanner/ will be safe

Yes, it should

For example, /etc/MailScanner/MailScanner.conf is updated to the new MailScanner version number, and the permissions for mtagroup are added, because it is required for MailScanner v5.

If by chance something changes that you don't think should, post back here and let us know , and remember, everything updated is backed up to /var/EFA/backup as a precaution.

I just snapshotted the vm, and ran the upgrade from 3.0.1.1 to 3.0.1.4.

so far, there appears to be no problems and everything is running fine after the reboot.



edit: oh, and my mailwatch fixes are in. happy day!

edit2: almost all. the spamassassin rule hits report is still broken and needs patching until mailwatch includes the fix