Sorry, you have to change the hostname/domainname to have at least two dots now, but it shouldn’t be a problem. You seem to use your providers mailserver so to avoid naming conflicts you should name your Nethserver like LocalMail.internal.cox.net. This way you avoid pinging the own server on imap.cox.net. There’s some discussion about naming as one shouldn’t use “invented” tlds like .local.
I’ll fire up a Nethserver 6.9 VM and reproduce your scenario to find an easy way to migrate your mails.
In my case
Nethesis,1234 as passphrase worked. I could also open the backup files with 7-zip under Windows. I couldn’t extract the files with command line`, this is what I tried, I got only folders:
for t in duplicity-full.20180215T115508Z.*.difftar.gz; do tar xvf $t; done
What I did to upgrade from old NS6.9 backup files to a new installed NS7.4:
- Install backup from software center
- Upload and restore from the backup config file - you’ll find the backup-config.tar.xz in the extracted backup under
- Now you see some warning todos, we solve them step by step:
- Set network role and ip of new interface, in my case I gave an IP to
- Release role of old interface and delete it, in my case
restore-data on root shell
- I recognized pop3connector was set to POP3 after restore but on NS6 it was set to IMAP with SSL checked so you may change this to fit your needs (I recommend IMAP with SSL)
- In my case POP3 without SSL worked too because ISP still supports it.
- I found my mails restored in /email@example.com and in roundcube webmail.