Thank you sir, here are my bindings settings
as you can see I am binding the mailcow services to my local lan IP and then I am using nginx proxy manager to reverse proxy to the correct WAN Interface - so I am thinking this may be a proxy/docker issue rather than an an mailcow config issue…
Then again maybe I need to amend the below to include the WAN IP I wish to use?
Do you think this may help?
Just to recap my server has a lan IP of 192.168.1.19 and I am running mailcow-dockerized on the lan IP and reverse proxing the front-end services to one of my WAN IPs (O have 2 but I want to restrict all the services for my hosted domain to run on 1 of the WAN IPs and have set this up correctly with my DNS provider)
I am confused and thinking that as mailcow-dockerized is bound to the plan IP although I am reverse proxing the front-end services to the correct WAN IP - my server may be selecting one of the WAN IPs (in this case the wrong WAN IP) as the default gateway that docker/mailcow is using to send emails…
Does this make sense - or do you have any ideas?
Many thanks for your reply and any help on this!