Update from v67 to v70 notes

Maintenance
1

This MIAB has been up for 2+ years with not many issues so far.

Here are some notes on the recent update

1) After a reboot, when running the script there is an error:

[...]
Executing: /lib/systemd/systemd-sysv-install enable fail2ban

FAILED: apt-get -y -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confnew install openssl
-----------------------------------------
E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 320420 (apt-get)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?

However, I do not have any other ‘dpkg’ going.

Running the script for the second time went without errors.

Edit: Found the info in the maintenace section:

If you see an error message similar to:

Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)

Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?

then be sure that you have closed any browser pages for your Mail-in-a-Box instance and run the above command again.

  1. Edit: Opened a new thread for this: Postfix error dsn=4.3.0
2

Looking through mail.log, I do not see anything suspicious (to me as a layman) in the vicinity of sending those delayed emails, except these two:

Nov 25 21:25:42 box opendkim[10205]: my_miab.com: key data is not secure: /home/user-data is writeable and owned by uid 1002 which is not the executing uid (122) or the superuser

Nov 25 21:25:43 box postfix/smtp[31946]: warning: smtp_tls_wrappermode requires "smtp_tls_security_level = encrypt" (or stronger)

But I am not sure if that is related?