Getting Postfix to run SMTPS on port 465

While setting up my new server, I followed the guide found here. Because of SmartBro’s braindead policy of forcing its subscribers to use their flaky SMTP server, I am forced to work around this issue by running SMTPS instead. I followed Step 5 of the guide and I was wondering why Evolution could not connect to the server. I have already enabled port 465 to go through on Bastille firewall but running nmap on the server does indicate that Postfix was not listening on port 465 as it should be.

I even went as far as regenerating my self-signed SSL certificates to be sure I had everything buttoned down. This just another one of those face-in-palm moments where the cause of the problem was so obvious. I forgot to enable SMTPS in master.cf. I simply uncommented the following lines in master.cf:

smtps     inet  n       –       n       –       –       smtpd
  -o smtpd_tls_wrappermode=yes
  -o smtpd_sasl_auth_enable=yes
  -o smtpd_client_restrictions=permit_sasl_authenticated,reject

Then I restarted Postfix and nmap now reports port 465 open.

4 Responses to “Getting Postfix to run SMTPS on port 465”

  1. orefalo Says:

    Thank you !

    I ended up in the same situation ! forgot to uncomment the line !

  2. sepins Says:

    I seem to be at a loss, if im not getting messages bounced they are getting queued but I can not get them to send using postfix and tls, if this thread is still active you think you could give me a hand with it? I have followed nearly every tutorial on the net, maybe i could get a copy of all the involved conf files or something. Thank you in advance for you help

  3. nimrod.abing Says:

    @sepins, where are you running your Postfix SMTP server? If you are running it on your local machine, it’s possible that your ISP is blocking well-known ports for both SMTP and SMTPS. In which case you are out of luck on this one.

    It’s impossible to tell what’s wrong with your setup since you did not say what OS you are running. You should turn on verbose debug logging and check your log files to see what’s going on. If you are running CentOS 5 it might be your firewall settings but I am just taking a shot in the dark here.

  4. nux Says:

    It’s funny how something as simple as this can be forgotten. Thanks for publishing this, first result in Google and just what I was looking for.

Leave a Reply

Comments are moderated by the administrator. If this is your first time posting a comment, your comment will go to a moderation queue and it may take a while for your comment to appear. Or it may get deleted.