Results 1 to 8 of 8
Thread: Postfix on Suse is not working
-
11-21-2008, 05:33 PM #1Junior Guru Wannabe
- Join Date
- Sep 2008
- Location
- Bangalore
- Posts
- 77
Postfix on Suse is not working
Hello WHT,
I need your help again now. I have a server which runs suse linux on it. Postfix is already installed on it.
But, the problem is i am not able to send mail using root. I mean using mail -v command.
I am new to suse linux. I could see the following in mail logs. I know 2 files main.cf and master.cf are there.
Not, sure what to change and how.
Nov 21 21:17:56 CSIDB3 postfix/smtp[14577]: connect to mx3.domain.com [x.x.x.x]: Connection timed out (port 25)
Nov 21 21:17:56 CSIDB3 postfix/smtp[14577]: 61715223EE: to=<sabarish@domain.com>, relay=none, delay=30, status=deferred (connect to mx3.domain.com[x.x.x.x]: Connection timed out)
The same thing happens will Gmail also. I think outgoing mail is not working at all.
Nov 21 20:27:41 CSIDB3 postfix/smtp[13907]: connect to gsmtp183.google.com[64.233.183.27]: Connection timed out (port 25)
Nov 21 20:27:41 CSIDB3 postfix/smtp[13907]: 5A177223E1: to=<sabarish@gmail.com>, relay=none, delay=189739, status=deferred (connect to gsmtp183.google.com[64.233.183.27]: Connection timed out)
-
11-21-2008, 05:35 PM #2Junior Guru Wannabe
- Join Date
- Sep 2008
- Location
- Bangalore
- Posts
- 77
cat /etc/issue
Welcome to SUSE Linux Enterprise Server 10 (x86_64) - Kernel \r (\l).
/etc/init.d/postfix status
Checking for service Postfix: running
-
11-21-2008, 06:14 PM #3WHT Addict
- Join Date
- Aug 2008
- Location
- Shoreline WA
- Posts
- 160
Are you able to send mail via any other user? The fact that it is showing in the logs that it is trying to send the message makes me think that perhaps outgoing port 25 is being blocked, but if you can send email via any other user, then that is not the case. I do not know your hosting situation, so it is a possibility.
__________________
Jonathan Kinney
Data Systems Specialist
Advantagecom Networks, Inc.http://www.simplywebhosting.com
-
11-22-2008, 05:26 AM #4Newbie
- Join Date
- Jan 2008
- Location
- Perth, Australia
- Posts
- 12
I would second that, looks like firewall issue as it is attempting to connect as you can see in the log files. Can you post up your iptables firewall script, maybe we can spot something in there that could be causing the problem.
With that said have you done any basic troubleshooting such as trying to telnet to those servers referenced in the logs on port25? Can you get to them outside of using Postfix basically..
-
11-24-2008, 01:56 PM #5Junior Guru Wannabe
- Join Date
- Sep 2008
- Location
- Bangalore
- Posts
- 77
Quote:
Originally Posted by claymen
I would second that, looks like firewall issue as it is attempting to connect as you can see in the log files. Can you post up your iptables firewall script, maybe we can spot something in there that could be causing the problem.
With that said have you done any basic troubleshooting such as trying to telnet to those servers referenced in the logs on port25? Can you get to them outside of using Postfix basically..
I think, Suse is not using iptables. Its using Yast. Using yast, I have allowed all services.
Also, i m not able to connect localhost on 110.
Will this can cause an issue. But, outgoing mails are using 25.
-
11-24-2008, 01:58 PM #6Junior Guru Wannabe
- Join Date
- Sep 2008
- Location
- Bangalore
- Posts
- 77
telnet localhost 110
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused
Trying ::1...
telnet: connect to address ::1: Connection refused
# telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
It will be great, if you help me. Because, i need to fix this asap.
-
11-24-2008, 02:23 PM #7Junior Guru Wannabe
- Join Date
- Sep 2008
- Location
- Bangalore
- Posts
- 77
This is what i get in logs,
relay=none, delay=0, status=deferred (delivery temporarily suspended: connect to mx3.domain.com[x.x.x.x]: Connection timed out)
-
11-24-2008, 06:32 PM #8Newbie
- Join Date
- Jan 2008
- Location
- Perth, Australia
- Posts
- 12
Connecting to yourself on port 25 isn't quite what I meant. What I wanted to find out is can you telnet to the destination mail servers that you are sending mail to.
E.g. your mail server sends mail on to the destination users mail server on port 25 so telnet to the destination to check connectivity.
Are you running POP3 on your local machine? If not then that would explain why you can't hit port 110.
That final log bit you posted is still the same thing, it couldn't connect and just timed out which could be firewall or other connectivity problems. Try telnetting to gsmtp183.google.com on port 25 or any other destination mail server you have in your logs that is failing. Confirm that you can actually get out or not. If you can't connect then you start looking at firewall/connectivity because if you can't then your mail-server won't be able to either.