Chris,
You're right, it was late and I was having a poke (hence the emoticon
in the original posting).
Back to the problem,
Jeff,
The server (203.219.50.38) is accessible to the outside world for port
110 but not 25. Until this is fixed there is no hope of getting mail
inbound to it.
However a reverse lookup of that server returns
38.50.219.203.in-addr.arpa name = free-tpg-038.tpgi.com.au.
And a subsequent MX search of the domain tpgi.com.au returns three
servers each with 3 addresses overlapping each other but none of
which are the above server. All three respond on port 25 listing
sendmail as the SMTP agent.
So......you have two issues.
1. If tpgi.com.au is the mail domain in question then, your DNS is
pointing in-bound mail to other IP addresses,
2. the IP address that you wish to receive inbound mail on is
not accessible from the internet on port 25.
The lack of access on port 25 to the outside world could either be
a blocking at your adsl firewall, or possibly that port is blocked
by iptables on the server itself. Yes I know local traffic can get
through but imagine that you have a rule which says allow inbound
to all ports if source address = 192.168.0.0 then a following rule
which denys access to all. This would let your local users sendmail
but make the server inaccesible to the outside world. I suspect that
this is the case because the telnet to port 25 is being denied not
dropped.
BTW, I know that posting ip's to this list feels like a bad thing to
do from a security point of view, but if you have a mail server then
you advertise that ip in the DNS, so once you make the decision to
host e-mail you are already asking for it. So you haven't really
compromised security by letting the ip out of the bag.
HTH
P.
--
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
