Upgrade path from mailinabox to power-mailinabox

[mrvanes]

Is there an upgrade/sidegrade path from mailinabox to power-mailinabox? Has anyone tried? Is it safe?

[MasterTailer]

Id love to know this too :D Can I just run the curl update command over the top of a vanilla Mailinabox?

[MasterTailer]

Ah thats very interesting - thanks for your reply..

[ddavness]

So far, I haven't actually bothered to check for a side-ways migration path, or even make sure that mailinabox backups are forward-compatible with power-mailinabox. After all, mailinabox and power-mailinabox target different distros.

Here's the main issue - if you have important data on Nextcloud then you're already off to a bad start. This is because mailinabox runs on NC20. power-mailinabox ships with NC23. There are also some files that power-mailinabox expands on but still mostly backwards compatible.

But both mailinabox and power-mailinabox are going to support Ubuntu 22.04: A pretty good opportunity to investigate a sideways update (even possibly doing this in-place!). But it'll depend on how the folks at mailinabox handle their side of the update - there are talks about replacing NextCloud with something else (see mail-in-a-box/mailinabox#2083) or doing some crazy migration steps. It's a watch and see.

@mrvanes Given that you've already plunged into it, what kind of issues have you encountered during the migration?

[mrvanes]

I played around a bit to fix things but didn't keep track of my efforts. I do still have my history so I'll try to reproduce and write down what needed attention when I find the time.

[signal-9]

Well, I was trying to make the switch and have been hitting roadblocks.
I'm currently on mailinabox v57a. I get power-mailinabox installed, start the duplicity recovery, and it goes smooth, but then when I try to reconfigure with sudo mailinabox, I get issues about Nextcloud and SSL. I believe Nextcloud issues are due to #67. Once I get that to complete though, I'm not able to manage from the admin panel, keep getting message that "something went wrong".
All of the mail and accounts and aliases seem to recover just fine, though. Just can't manage SSL, view the Status page / do much from the admin panel, and can't access roundcube or nextcloud.
Could it have something to do with power-mailinabox being a few commits behind mailinabox? Trying to recover basically to a downgraded version? I'm not sure that would work even on mailinabox.

[ddavness]

There's also the fact that they're several versions behind on Nextcloud. If you were hoping to keep NC data, you're in for a ride 😬

[ddavness]

Here's an update: Now both MIAB and this fork are somewhat at OS parity - more specifically, they're both supporting Ubuntu 22.04. They're on NC 23 while we moved to NC 24 - but that shouldn't be the biggest issue ever.

I wonder whether there's a safe window now to do the switch, or whether it's still pretty hard to do so.

[mannp]

I don't actually use NC or nginx configs on my miab and so would not mind if they were reset moving to p-miab

Mainly have email and email aliases setup, but not a huge mailbox to transfer.

Did anyone manage to get their emails and aliases transferred at all?

Thanks in advance.

Distributor ID:	Debian
Description:	Debian GNU/Linux 11 (bullseye)
Release:	11
Codename:	bullseye

[ddavness]

Emails and aliases are likely a non-issue to transfer, since the schema is exactly the same. Same for the mailbox format.

[ddavness]

If you don't have existing data in the new box to "merge", just copy over from the old one. All files required are there.

Otherwise you can use an external tool (e.g. imapsync) to synchronize messages between inboxes, and re-create missing users/aliases manually.

[mannp]

p-miab has the important data, so a copy over won't be good.

I will look into imapsync thanks, although not entirely clear how it will work, when I am transferring from essentially the same account with the same domain on a different server.

[ddavness]

I think that's the point, transfer over mail between two inboxes (may be the same account in different servers).
Apparently you need to pay for it, but if you want to dwell on compiling it from source, it is freely available (https://github.com/imapsync/imapsync)

[mannp]

I think that's the point, transfer over mail between two inboxes (may be the same account in different servers). Apparently you need to pay for it, but if you want to dwell on compiling it from source, it is freely available (https://github.com/imapsync/imapsync)

What I mean is currently domain.com points to miab, but I will need to change it to point to p-miab and then not clear how I can login to the original miab as it will be pointing to p-miab.....maybe it needs a 3rd account to transfer between.

Current imapsync is on Nix, just installed and seems fine.

[ddavness]

probably create a subdomain temp.example.com and assign it to the old server? That way you can probably do the transfer-over fine

[blok82]

Hi,

What would happen if i just install pmiab over an existing miab system? (miab 60.1 --> pmiab 60.4)
I use it for e-mail and dns only (for 3 domains), dont use contacts/calendar/active sync

I have 1 vps with miab now, but would like to move to pmiab beause of the added features (like TTL and quota. i guess miab is not interested in those), but i dont want to destroy my mailserver....... scary stuff for someone who is not an expert in mail servers :-)
I'm afraid that a second vps to migrate to is not really an option for me...

If its not possible to do then i guess i could start from scratch, but that's.... hmm.... not really a fun idea.

Thanks for any light you can shed in my darkness

[mannp]

Hey @blok82 did you make any progress on this?

Holding off on my miab upgrade as there seem to be a few support requests for failed upgrades :-/ but i know it must be done :)