management IP address (mgmtip) must be different from your platform installation IP address. This suggests that while the Velocity MTA can be on the same server, it needs to be configured with a different IP address than the main platform.

Given that emaildelivery.com uses ports 80, 443, and 2525, and the Velocity MTA requires that ports 80, 81, and 25 are not in use, there is a conflict with port 80. Both systems require port 80 to be available.

This means that if you want to run both emaildelivery.com and Velocity MTA on the same server, you would encounter issues due to the overlapping use of port 80"

This means that if you want to run both emaildelivery.com and Velocity MTA on the same server, you would encounter issues due to the overlapping use of port 80.

To resolve this, you have a few options:

Different IP Addresses: If your server supports multiple IP addresses (IP aliasing), you can assign a different IP address to each system. This way, both systems can use port 80, but on different IP addresses.

Use a Reverse Proxy: Implement a reverse proxy (like Nginx or Apache) to listen on port 80 and then route traffic based on domain names or other criteria to the appropriate system on a different port. This can be complex and requires careful configuration.

Separate Servers: The simplest and most straightforward solution would be to use two separate servers – one for emaildelivery.com and another for Velocity MTA. This ensures that there are no port conflicts and both systems can operate optimally.

Given the port conflict and the potential complexities of resolving it, if you have the resources, using separate servers might be the most hassle-free approach.

Any thoughts on that, chaps?