SMTP(S) Postfix config - ISP has me blocked on 25

17 posts / 0 new
Last post
#1 Wed, 04/01/2009 - 02:52
max

SMTP(S) Postfix config - ISP has me blocked on 25

My is has blocked port 25.

My goal is to use SMTPS to send mail on port 465 to try to get around the port 25 restriction. Hopefully 465 is not restricted too.

  • I have enabled smtps in the postfix processes.
  • Opened port 465 in the firewall.
  • restarted postfix and firewall

How do I tell postfix to use SMTPS ? How do I test it ? telnet to 465 returns nothing as of now, but does not close a connection.

NOTE: I am not using TSL...it seems to only work on port 25 and i cant use that port. Maybe that is the problem?

How are people getting around this obscured blocking of information and freedom????

Wed, 04/01/2009 - 04:51
kenlyle

rimuhosting.com has a support doc on this. Search their site for 2525.

Best,
K

Wed, 04/01/2009 - 05:12
andreychek

Yeah, if it's working, you should be able to telnet into it.

If you're SSH'd into your server, can you telnet into it from there? That should tell you if it's running.

You could also use netstat -- netstat -an | grep :465

You're on the right track though, using SMTPS and/or Submission is a good way to get around ISP port 25 restrictions.
-Eric

Wed, 04/01/2009 - 07:50
max

Great referal ! works !

But now I cant seem to authenticate when sending mail. The password works for receiving but not sending (noooooo... I want to sleep)

Wed, 04/01/2009 - 08:12
max

EDIT

maillog says:

warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory

Wed, 04/01/2009 - 08:24 (Reply to #5)
Joe
Joe's picture

<div class='quote'>warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory </div>

Looks like saslauthd isn't running.

Try restarting it.

--

Check out the forum guidelines!

Wed, 04/01/2009 - 11:29
max

[root@ns1 sysconfig]# service saslauthd restart
Stopping saslauthd: [ OK ]
Starting saslauthd: [ OK ]

Still get the same error :

postfix/smtpd[5471]: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory

What file or directory is it looking for?

Wed, 04/01/2009 - 11:32 (Reply to #7)
andreychek

What do you get if you type this on the command line:

ps auxw | grep saslauth

Wed, 04/01/2009 - 11:45
max

root 5093 0.0 0.0 5484 484 ? Ss 13:21 0:00 /usr/sbin/saslauthd -m /var/run/saslauthd -a pam
root 5094 0.0 0.0 5484 264 ? S 13:21 0:00 /usr/sbin/saslauthd -m /var/run/saslauthd -a pam
root 5095 0.0 0.0 5484 260 ? S 13:21 0:00 /usr/sbin/saslauthd -m /var/run/saslauthd -a pam
root 5096 0.0 0.0 5484 260 ? S 13:21 0:00 /usr/sbin/saslauthd -m /var/run/saslauthd -a pam
root 5098 0.0 0.0 5484 260 ? S 13:21 0:00 /usr/sbin/saslauthd -m /var/run/saslauthd -a pam
root 6419 0.0 0.0 3908 664 pts/0 R+ 13:44 0:00 grep saslauth

maybe its missing the pam file? I really have to idea because it should be just pain text authentication? right?

Wed, 04/01/2009 - 11:58
max

I might need professional help sorting this out (for the server and mentally)

I have an office not getting orders because of this email issue. Just switched the domain to point to me yesterday.

Wed, 04/01/2009 - 12:35 (Reply to #10)
Joe
Joe's picture

Try restarting postfix, as well.

What OS/version are you running? (saslauthd is way more OS dependent in its paths and configuration than anything else in a Virtualmin system, and so I can't even tell you where to look without know the OS/version. Also, some of the configuration is built into Postfix at compile time, so it looks completely magic if you're expecting to find paths in a configuration file.)

--

Check out the forum guidelines!

Wed, 04/01/2009 - 12:47
max

Virtualmin 3.67 Pro
Linux 2.6.18-92.1.22.el5 on i686
CentOS Linux 5.2

Joe,

Not sure what the support is for pro users on this issue, but I can pay you to fix it if necessary (cant pay a lot though)? I am really beat. I sent you an email.

Thanks,
Max

Wed, 04/01/2009 - 12:51 (Reply to #12)
Joe
Joe's picture

<div class='quote'>Not sure what the support is for pro users on this issue, but I can pay you to fix it if necessary (cant pay a lot though)?</div>

No need to pay. This is well within the bounds of included support.

Install the Virtualmin Support module, file a ticket, and grant us access to your system. Eric or I will be able to drop in and take a look (and no passwords ever need traverse teh interwebs).

Docs for the support module are here:

http://www.virtualmin.com/documentation/id,support_requests_and_remote_l...

--

Check out the forum guidelines!

Wed, 04/01/2009 - 12:57
max

It really is April fools day for me:::::::::::::

Now updating wbm-virtualmin-support ..

Installing package(s) with command yum -y install wbm-virtualmin-support ..

Loading &quot;fastestmirror&quot; plugin
Loading mirror speeds from cached hostfile
* virtualmin: software.virtualmin.com
* update: ftp.sonic.net
* base: ftp.sonic.net
* virtualmin-universal: software.virtualmin.com
* extras: ftp.sonic.net
ftp://ftp.sonic.net/mirrors/centos/5/updates/i386/repodata/repomd.xml: [Errno 4] IOError: [Errno ftp error] 450 repomd.xml: No such file or directory
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: update. Please verify its path and try again

.. install failed!

Wed, 04/01/2009 - 13:00 (Reply to #14)
Joe
Joe's picture

OK, just force it to only use our repository, since your OS repository is broken (you'll want to fix that, though--you can't safely run a server without regular updates, and right now you can't get updates).

yum --disablerepo=update --disablerepo=base --disablerepo=extras install wbm-virtualmin-support

--

Check out the forum guidelines!

Wed, 04/01/2009 - 13:03 (Reply to #15)
Joe
Joe's picture

Or, you can just email me the authentication details and I'll try to dig it out of my hundreds of new messages. ;-)

--

Check out the forum guidelines!

Wed, 04/01/2009 - 21:56
max

To contribute, and to all of those who are in suspense:

In the postfix /etc/postfix/master.cf

The line where I added the new port 2525
2525 inet n - - - - smtpd

I forgot to append to the saslauthd info to end of it. Sorry dont have it in front of me but see the standard smtp port in that file.