Solved

Enabling SASL on Centos 5 / Postfix / Dovecot leads to 'connection refused'

Posted on 2010-11-18
4
832 Views
Last Modified: 2013-11-10
I followed the instructions to add SASL support to working postfix / dovecot install on Centos 5.
(instructions found here: http://www.linuxmail.info/postfix-smtp-auth-dovecot-sasl/  )
After changing to require SASL, server always shows:

[root@web1 etc]# telnet mydomain.com smtp
Trying 69.72.208.163...
telnet: connect to address 69.72.208.163: Connection refused

telnet localhost pop3 is ok

No messages in maillog or messages.
This is on a hosted Virtual private server. Appears to be using parallels
Thoughts?
0
Comment
Question by:JerryNorton
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 
LVL 26

Expert Comment

by:jar3817
ID: 34175200
Is your MTA listening for connections? Type this command to find out:

# netstat -an |grep 25.*LISTEN
0
 

Author Comment

by:JerryNorton
ID: 34180185
it is listening. [root@web1 ~]# netstat -an | grep 25
tcp        0      0 127.0.0.1:25                0.0.0.0:*                   LISTEN
0
 
LVL 23

Accepted Solution

by:
Maciej S earned 500 total points
ID: 34180224
It is listening on localhost interface only.

Post here output of "postconf -n" command.
Additionally, attach (or paste its content here) your master.cf file.
0
 

Author Closing Comment

by:JerryNorton
ID: 34181737
I had ADDED a line inet_interfaces = all.
However, I didn't comment out the line inet_interfaces = localhost when I did that. I had 'all' before 'localhost'. Thanks!
0

Featured Post

MIM Survival Guide for Service Desk Managers

Major incidents can send mastered service desk processes into disorder. Systems and tools produce the data needed to resolve these incidents, but your challenge is getting that information to the right people fast. Check out the Survival Guide and begin bringing order to chaos.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Granting full access permission allows users to access mailboxes present in their database. By giving full access permission one can open and read the content of any mailbox but cannot send emails from that mailbox.
The new Gmail Phishing Scam going around is surprising even the savviest of users with its sophisticated techniques.
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question