[NTLUG:Discuss] Postfix
Dennis Rice
dennis at dearroz.com
Mon Aug 6 18:13:02 CDT 2007
In the continuing saga, the problem was solved....
------------------
> Hi Dennis,
> >
> > If there is no firewall, I have to think that Postfix isn't actually
> > running, since the port isn't open.
> > Does 'ps -ef |grep postfix' prove that it's running? Does the mail
> > log indicate that all's well?
> >
Or where is it bound?
sudo netstat -pln | grep postfix
see if it is bound to 127.0.0.1 or 0.0.0.0 or your IP.
sorry, coming in late and drinking tonigth.
220 is not imap. 143 is imap. 993 is imap/ssl. postfix is an MTA, so
25 only. As far as sending mail, you will need to configure the relays
hosts (not recommended), or use authentication credentials to allow
relay (recommended). I use sendmail and exim, so I am no real help with
the configs... so I guess I can shut up now.
I'm confused. If nmap says 25 is open, but you can't telnet there,
problem. nmap will do a connnect by default. Maybe add in a -sV and
see what the results are (assuming a recent version of nmap).
----------------
The solution was to add the local IP address to the inet_interfaces
address. For some reason, the Postfix does not pick up on the
interface address. Normal configuration (recommended)is:
inet_interfaces = $myhostname, localhost
I had to change this to:
inet_interfaces = $myhostname, localhost, 192.168.1.71
After adding the above, I was able to telnet to the server port 25.
If anyone has any comprehension to why, I am sure many would like to
understand, including the people back at Postfix. Does anyone know of
a variable that returns an interface's IP address?
Note that I am learning and experimenting so this system is only
working in my internal network at this time. Objective is to place
document a setup that will go onto the Internet and serve a business.
Dennis
More information about the Discuss
mailing list