Mail-in-a-Box version v0.40 and moving to Ubuntu 18.04

slenk · January 15, 2019, 10:20pm

Is it easy to explain/list out the reasons for being at v0.30 regarding PHP? Is it simply an upgrade from PHP5 to 7 or much more than that?

alento · January 15, 2019, 10:29pm

I can only suggest to look at the change log … likely some of the other components of MiaB required PHP 7 vs PHP 5.

github.com

mail-in-a-box/mailinabox/blob/v0.40/CHANGELOG.md#changelog

CHANGELOG
=========

v0.40 (January 12, 2019)
------------------------

This is the first release for Ubuntu 18.04. This version and versions going forward can **only** be installed on Ubuntu 18.04; however, upgrades of existing Ubuntu 14.04 boxes to the latest version supporting Ubuntu 14.04 (v0.30) continue to work as normal.

When **upgrading**, you **must first upgrade your existing Ubuntu 14.04 Mail-in-a-Box box** to the latest release supporting Ubuntu 14.04 --- that's v0.30 --- before you migrate to Ubuntu 18.04. If you are running an older version of Mail-in-a-Box which has an old version of ownCloud or Nextcloud, you will *not* be able to upgrade your data because older versions of ownCloud and Nextcloud that are required to perform the upgrade *cannot* be run on Ubuntu 18.04. To upgrade from Ubuntu 14.04 to Ubuntu 18.04, you **must create a fresh Ubuntu 18.04 machine** before installing this version. In-place upgrades of servers are not supported. Since Ubuntu's support for Ubuntu 14.04 has almost ended, everyone is encouraged to create a new Ubuntu 18.04 machine and migrate to it.

For complete upgrade instructions, see:

https://discourse.mailinabox.email/t/mail-in-a-box-version-v0-40-and-moving-to-ubuntu-18-04/4289

The changelog for this release follows.

Setup:

* Mail-in-a-Box now targets Ubuntu 18.04 LTS, which will have support from Ubuntu through 2022.
* Some of the system packages updated in virtue of using Ubuntu 18.04 include postfix (2.11=>3.3) nsd (4.0=>4.1), nginx (1.4=>1.14), PHP (7.0=>7.2), Python (3.4=>3.6), fail2ban (0.8=>0.10), Duplicity (0.6=>0.7).

This file has been truncated. show original

The project’s GitHub page may also shed some light.

JvdBBBB · January 15, 2019, 10:34pm

Upgraded a Strato VPS:
First issue:
The same as @yonkoc

Second: I got the installer to:
Initializing system random number generator...
Creating SSH key for backup…
Firewall is active and enabled on system startup
When I got the error:
Failed to restart systemd-resolved.service: Unit systemd-resolved.service is masked.

I had to run systemctl unmask systemd-resolved.service

Now I have one rather important issue left:
✖ Incoming Mail (SMTP/postfix) is not running (port 25).

Anyone know what to do about this? I have rebooted and rerun the install script a couple of times but it does not solve the problem. I have run ufw status but the port shows as allowed anywhere.

alento · January 15, 2019, 10:41pm

The encoding issue? or one of the other issues?

JvdBBBB · January 15, 2019, 10:55pm

Yes, the encoding issue.
The first 2 issues are solved.
The third issue I do not have a solution for so far.

alento · January 15, 2019, 10:57pm

Did setting the locale not help?

JoshData · January 15, 2019, 11:02pm

As @alento suggested, I’m going to close this topic because it’ll be easier for everyone to help everyone if we move to separate topics for each issue. Please feel free to open a new topic if you have trouble with the uprade and the discussion can continue! (Also please check the forum for posts from others with the same problem first.)

Thanks to everyone who provided suggestions for improving the upgrade instructions. I made some updates, and I will go back over the replies to see if I missed anything. And thanks to @alento for the nudge to close this topic so things would be less confusing.