LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (http://www.linuxquestions.org/questions/linux-networking-3/)
-   -   Postfix Problem - No incoming mail (http://www.linuxquestions.org/questions/linux-networking-3/postfix-problem-no-incoming-mail-44700/)

Gareman 02-09-2003 01:15 PM

Postfix Problem - No incoming mail
 
I've recently installed RedHat 8 along with BIND and Postfix. My Postfix server (runlevel6.com) can send mail just fine, but it can't receive it.

Clients attempting to connect to my mail server report that the operation timed out waiting for a response from the sending (SMTP) server.

Also, I've tried running dnsreport.com against my domain and it says it can find my MX records but that it (also) can't connect to my mail server.

Nothing appears in the Postfix logs.

Iptables is turned off on the mail server.

SMTP is allowed on my firewall.

I can connect to SMTP via telnetting to the port or to SMTP, on the local machine, on other machines in the domain. Machines outside of the domain connect to SMTP put then report "500 Error: bad syntax."

Any ideas or next step in troubleshooting would be greatly appreciated!

Thanks!

--gary

DaveG 02-09-2003 04:02 PM

First rule out any problems with the network firewall.
Check the logs (if possible) for Internet -> Postfix server:SMTP to look for problems. Attempt, if possible, to connect to the server using telnet from an external machine for an accurate simulation.
If you can rule out the network firewall then you should be able to test further witha local telnet to the SMTP port on the Postfix server. Make sure you are connecting over the network and not over the software loopback (127.0.0.1).
Things to check should include /etc/hosts.allow/deny, (x)inetd settings etc. that do local IP-based connection screening.
Check that the Postfix listener daemons are running properly and are listening on the right port (lsof -i).
For the MX records, check with your DNS Registrar. Things can take a few days to filter through.

Gareman 02-09-2003 10:24 PM

Good advice
 
I dialed into my ISP (not directly connected) and used telnet to the mail server. I used some commands I found online for troubleshooting smtp problems and here's what I was able to get:

220 ns1.runlevel6.com ESMTP Postfix
ehlo me
250-ns1.runlevel6.com
250-PIPELINING
250-SIZE 10240000
250-VRFY
250-ETRN
250-XVERP
250 8BITMIME
mail from: gray@runlevel6.com
250 Ok
rcpt to: gray@runlevel6.com
250 Ok
data
354 End data with <CR><LF>.<CR><LF>
test 123
.
250 Ok: queued as 2D28A1BE80
quit
221 Bye


Connection to host lost.

C:\>

So, I was able to send an email message and receive it without errors, while telnetted in from another network. Yet I still can't send email via a mail client. Any ideas for the next troubleshooting step? Meanwhile, I'll try those other suggestions.

Thanks!

--gary

Gareman 02-09-2003 10:32 PM

Answers to more questions
 
My hosts.allow and hosts.deny have no entries.

lsof -i produces the following information:

[root@ns1 sbin]# ./lsof -i
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
portmap 491 rpc 3u IPv4 920 UDP *:sunrpc
portmap 491 rpc 4u IPv4 926 TCP *:sunrpc (LISTEN)
rpc.statd 510 rpcuser 4u IPv4 1002 UDP *:32768
rpc.statd 510 rpcuser 6u IPv4 1005 TCP *:32768 (LISTEN)
named 613 named 8u IPv4 1712 UDP *:32769
named 613 named 9u IPv4 1705 UDP ns1.runlevel6.com:domain
named 613 named 10u IPv4 1706 TCP ns1.runlevel6.com:domain (LISTEN)
named 613 named 11u IPv4 1710 UDP 192.168.0.202:domain
named 613 named 12u IPv4 1711 TCP 192.168.0.202:domain (LISTEN)
named 613 named 13u IPv4 1713 TCP ns1.runlevel6.com:rndc (LISTEN)
named 615 named 8u IPv4 1712 UDP *:32769
named 615 named 9u IPv4 1705 UDP ns1.runlevel6.com:domain
named 615 named 10u IPv4 1706 TCP ns1.runlevel6.com:domain (LISTEN)
named 615 named 11u IPv4 1710 UDP 192.168.0.202:domain
named 615 named 12u IPv4 1711 TCP 192.168.0.202:domain (LISTEN)
named 615 named 13u IPv4 1713 TCP ns1.runlevel6.com:rndc (LISTEN)
named 616 named 8u IPv4 1712 UDP *:32769
named 616 named 9u IPv4 1705 UDP ns1.runlevel6.com:domain
named 616 named 10u IPv4 1706 TCP ns1.runlevel6.com:domain (LISTEN)
named 616 named 11u IPv4 1710 UDP 192.168.0.202:domain
named 616 named 12u IPv4 1711 TCP 192.168.0.202:domain (LISTEN)
named 616 named 13u IPv4 1713 TCP ns1.runlevel6.com:rndc (LISTEN)
named 617 named 8u IPv4 1712 UDP *:32769
named 617 named 9u IPv4 1705 UDP ns1.runlevel6.com:domain
named 617 named 10u IPv4 1706 TCP ns1.runlevel6.com:domain (LISTEN)
named 617 named 11u IPv4 1710 UDP 192.168.0.202:domain
named 617 named 12u IPv4 1711 TCP 192.168.0.202:domain (LISTEN)
named 617 named 13u IPv4 1713 TCP ns1.runlevel6.com:rndc (LISTEN)
named 618 named 8u IPv4 1712 UDP *:32769
named 618 named 9u IPv4 1705 UDP ns1.runlevel6.com:domain
named 618 named 10u IPv4 1706 TCP ns1.runlevel6.com:domain (LISTEN)
named 618 named 11u IPv4 1710 UDP 192.168.0.202:domain
named 618 named 12u IPv4 1711 TCP 192.168.0.202:domain (LISTEN)
named 618 named 13u IPv4 1713 TCP ns1.runlevel6.com:rndc (LISTEN)
xinetd 632 root 5u IPv4 1721 TCP *:daytime (LISTEN)
xinetd 632 root 6u IPv4 1722 TCP *:imap (LISTEN)
xinetd 632 root 7u IPv4 1723 TCP *:imaps (LISTEN)
xinetd 632 root 9u IPv4 1724 TCP *:pop3 (LISTEN)
xinetd 632 root 10u IPv4 1725 TCP *:pop3s (LISTEN)
xinetd 632 root 11u IPv4 1726 TCP ns1.runlevel6.com:32769 (LISTEN)
xinetd 632 root 12u IPv4 1729 TCP *:telnet (LISTEN)
ntpd 646 ntp 4u IPv4 1769 UDP *:ntp
ntpd 646 ntp 5u IPv4 1770 UDP ns1.runlevel6.com:ntp
ntpd 646 ntp 6u IPv4 1771 UDP 192.168.0.202:ntp
lpd 660 lp 6u IPv4 1798 TCP *:printer (LISTEN)
master 736 root 11u IPv4 1913 TCP *:smtp (LISTEN)
smbd 797 root 9u IPv4 2074 TCP *:netbios-ssn (LISTEN)
nmbd 801 root 6u IPv4 2077 UDP *:netbios-ns
nmbd 801 root 7u IPv4 2078 UDP *:netbios-dgm
nmbd 801 root 8u IPv4 2082 UDP 192.168.0.202:netbios-ns
nmbd 801 root 9u IPv4 2083 UDP 192.168.0.202:netbios-dgm
miniserv. 839 root 4u IPv4 2166 TCP *:10000 (LISTEN)
miniserv. 839 root 5u IPv4 2167 UDP *:10000
X 895 root 1u IPv4 2235 TCP *:x11 (LISTEN)
[root@ns1 sbin]#

Also, I'm hosting my own DNS and I seem to be able to resolve fine. Running a report on www.dnsreport.com shows all this information and the fact that it can't find my mail server.

Again, any help would be greatly appreciated!

--gary:study:

Gareman 02-10-2003 11:40 AM

One more bit of info
 
One more bit of info. Although I was able to telnet in without trouble from another network yesterday, a friend pointed out his problems connecting. He tried:

telnet runlevel6.com 25

220 ns1.runlevel6.com ESMTP Postfix
500 Error: bad syntax


Feel free to try this yourself.

Thanks!

--gary


All times are GMT -5. The time now is 07:33 PM.