[Podman] Re: Making progress running MTA container - Q re ports

People, Starting my MTA with: podman run --rm -d -h pricom.com.au \     -v /home:/home \     -p 127.0.0.1:25:25 \     -p 127.0.0.1:143:143 \     -p 127.0.0.1:587:587 \     -p 127.0.0.1:993:993 \     -p 127.0.0.1:995:995 \     --name indimail \     `podman images | grep indimail | awk '{ print $3 }'` \     indimail - works happily and while mail delivery is working fine within the container, the ports are not accessible from other computers ie: I have opened ports on the host using iptables and when using nmap on localhost get: Starting Nmap 7.80 ( https://nmap.org ) at 2020-03-27 13:47 AEDT Nmap scan report for localhost (127.0.0.1) Host is up (0.0000050s latency). rDNS record for 127.0.0.1: localhost.localdomain Not shown: 993 closed ports PORT    STATE    SERVICE 22/tcp  open     ssh 25/tcp  filtered smtp 143/tcp filtered imap 587/tcp filtered submission 631/tcp open     ipp 993/tcp filtered imaps 995/tcp filtered pop3s - which doesn't look promising and from another machine on the LAN I get: Starting Nmap 7.80 ( https://nmap.org ) at 2020-03-27 13:44 AEDT Nmap scan report for phil (192.168.1.20) Host is up (0.00019s latency). rDNS record for 192.168.1.20: phil.pricom.com.au Not shown: 994 filtered ports PORT    STATE  SERVICE 22/tcp  open   ssh 25/tcp  closed smtp 143/tcp closed imap 587/tcp closed submission 993/tcp closed imaps 995/tcp closed pop3s - so I must still missing something about linking container ports to the same host ports . . Suggestions? Thanks, Phil.