Synchronization failure of IMAP Port has been changed

[Boldie]

Contribution guidelines

• I've read the contribution guidelines and wholeheartedly agree

I've found a bug and checked that ...

• ... I understand that not following the below instructions will result in immediate closure and/or deletion of my issue.
• ... I have understood that this bug report is dedicated for bugs, and not for support-related inquiries.
• ... I have understood that answers are voluntary and community-driven, and not commercial support.
• ... I have verified that my issue has not been already answered in the past. I also checked previous issues.

Description

After doing a fresh install, I want to transfer my old mail data using synchronize. For this to succeed I have changed the ports for the new mailcow installation to be prefixed with a 9 for eg. IMAP is now on 9143.
After starting the sync I found out the port change is not respected by synchronization mechanism which will lead to an aborted sync. The port for the new server seems not to be recognized while calling the external tool.

Inspecting the command line form the logs shows the --port2 option is missing.

Logs:

Host1: Socket successfully converted to SSL
Host1: success login on [imap.xxxx.de] with user [usernameA] auth [LOGIN] or [LOGIN]
Host2: connecting and login on host2 [localhost] port [143] with user [[email protected]*[email protected]]
Host2 failure: can not open imap connection on host2 [localhost] with user [[email protected]*[email protected]]: Unable to connect to localhost:  Connection refused

Steps to reproduce:

1. Install Mailcow
2. Change IMAP Port to something different then 143
3. Add a Mailbox and Domain
4. Configure a synchronization from a different server
5. -> The sync breaks because he can not connect to Port 143 in the new mailcow installation.

Which branch are you using?

master

Which architecture are you using?

x86

Operating System:

Uneccesary

Server/VM specifications:

Uneccesary

Is Apparmor, SELinux or similar active?

Uneccesary

Virtualization technology:

Uneccesary

Docker version:

Uneccesary

docker-compose version or docker compose version:

Uneccesary

mailcow version:

Uneccesary

Reverse proxy:

Uneccesary

Logs of git diff:

Uneccesary

Logs of iptables -L -vn:

Uneccesary

Logs of ip6tables -L -vn:

Uneccesary

Logs of iptables -L -vn -t nat:

Uneccesary

Logs of ip6tables -L -vn -t nat:

Uneccesary

DNS check:

Uneccesary

[Boldie]

The log message was completely missleading in this context. Yes, it works now, but the problem was the server was not reliable working and thus sometimes down. Now it works because the problem with the server being down is away. Hopefully it will work as expected now.