Atomicorp

My SMTP service stopped accepting non-secure and TLS connections. It does accept connections via SSL, but the response time is extremely slow...upto a minute or two to send each email.

Another thing that is happening is that my IMAP server refuses to open more connections and tells me that I have too many open connections.

I have checked the log files and the only thing I can see is that I am getting a lot of xinetd relaylock messgaes.

The only thing that I have installed on the server recently was SugarCRM and I'm not sure why that would affect my Qmal / SMTP services.

Does anyone know how I can trach down the problem and get this fixed?

Thanks in advance!

First off: SMTP (qmail) and IMAP (courier) are two different services.

Did you try restarting SMTP?

Sending mail takes a long time: http://kb.swsoft.com/article_22_298_en.html

Allow more connections to Courier: http://kb.swsoft.com/article_22_165_en.html

Yes, they are different services. So, most likely different issues.

Yes, I restarted SMTP and the whole server.

I changed my imap settings:

/etc/courier-imap/imapd

MAXPERIP= 10
MAXDAEMONS= 50

and my smtp_psa file looks fine:
When I telnet to the server on port 25 I don't get an ESMTP greeting, just a black hole.

And still can not send email via port 25 but CAN send via 443.

Maybe your ISP is blocking port 25 outbound except to their own SMTP server? A lot of IPSs seem to be doing that these days to prevent spam. Can you ssh into your server and then connect to localhost on port 25?

I can do both:

ssh to my server and telnet localhost 25 and it shows the ESMTP greeting

and

from windows

telnet hostname 25 (this gives me a black hole)

also in my maillog I see tons of these:
Is this normal?

cgraham wrote:I can do both:

ssh to my server and telnet localhost 25 and it shows the ESMTP greeting

and

from windows

telnet hostname 25 (this gives me a black hole)

Well, then it looks like there's nothing wrong with the SMTP service, you only cannot connect to it, probably because of some firewall. I guess it's your ISP blocking port 25 outbound. You could ask someone who knows he doesn't have port 25 outbound blocked to check if they can telnet to port 25 on your server.

also in my maillog I see tons of these:

Code: Select all

May 12 11:15:18 hostname relaylock: /var/qmail/bin/relaylock: mail from 80.103.104.195:3466 (195.pool80-103-104.dynamic.orange.es)
May 12 11:15:43 hostname relaylock: /var/qmail/bin/relaylock: mail from 218.15.150.132:3022 (132.150.15.218.broad.mz.gd.dynamic.163data.com.cn)
May 12 11:16:49 hostname relaylock: /var/qmail/bin/relaylock: mail from 91.76.114.230:1839 (ppp91-76-114-230.pppoe.mtu-net.ru)
May 12 11:16:49 hostname relaylock: /var/qmail/bin/relaylock: mail from 91.76.114.230:1841 (ppp91-76-114-230.pppoe.mtu-net.ru)
May 12 11:16:49 hostname relaylock: /var/qmail/bin/relaylock: mail from 91.76.114.230:1840 (ppp91-76-114-230.pppoe.mtu-net.ru)
May 12 11:16:49 hostname relaylock: /var/qmail/bin/relaylock: mail from 91.76.114.230:1837 (ppp91-76-114-230.pppoe.mtu-net.ru)
May 12 11:16:49 hostname relaylock: /var/qmail/bin/relaylock: mail from 91.76.114.230:1838 (ppp91-76-114-230.pppoe.mtu-net.ru)
May 12 11:16:56 hostname relaylock: /var/qmail/bin/relaylock: mail from 213.184.21.197:14130 (asa-ds.man.olsztyn.pl)
May 12 11:17:01 hostname relaylock: /var/qmail/bin/relaylock: mail from 190.74.25.144:2804 (190.74-25-144.dyn.dsl.cantv.net)
May 12 11:17:03 hostname relaylock: /var/qmail/bin/relaylock: mail from 201.52.133.76:1462 (c934854c.virtua.com.br)
May 12 11:17:07 hostname relaylock: /var/qmail/bin/relaylock: mail from 201.51.62.29:3267 (20151062029.user.veloxzone.com.br)
May 12 11:17:48 hostname relaylock: /var/qmail/bin/relaylock: mail from 201.29.131.101:4378 (20129131101.user.veloxzone.com.br)
May 12 11:18:21 hostname relaylock: /var/qmail/bin/relaylock: mail from 216.211.144.154:2889 (mx2.direct-info-service.net)

Is this normal?

Well, it's machines trying to connect to your mail server. That will happen, yes.

Sure enough. It looks like my ISP suddenly flipped the switch on outbound port 25...now all my neighbors are calling me for tech support...LOL

Just curious, is there an easy way to set up my smtp server to listen on port 587 or 465 via SSL like Yahoo or Google?

Thanks!

Hi,

The slow response behaviour from SMTP can also be caused by too many RBL's in your RBL list or if one of your RBL servers is having a bad day and being slow to respond.

I've seen this on a few occasions with my own servers. Obviously, when there's an inbound SMTP connection, the RBLs have to be queried and results received before the connections can be processed, if there is no response from the RBL, then you have to wait for the timeout.

Hope this helps

Cheers

T.

cgraham wrote:Sure enough. It looks like my ISP suddenly flipped the switch on outbound port 25...now all my neighbors are calling me for tech support...LOL

You could instruct them to just use their ISP's SMTP server.

Just curious, is there an easy way to set up my smtp server to listen on port 587 or 465 via SSL like Yahoo or Google?

Your SMTP service already does SMTPS. Check out smtp_psa and smtps_psa in /etc/xinetd.d. I believe you can listen on extra ports by copying smtp_psa under another name and setting an alternative port. I believe there are tons of posts on this on SWsoft's forums.

And it already listens on port 465