ispCP - Board - Support
No SMTP sending but, no errors - Printable Version

+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Support Area (/forum-30.html)
+--- Forum: Usage (/forum-34.html)
+--- Thread: No SMTP sending but, no errors (/thread-4698.html)



No SMTP sending but, no errors - Sens0r - 10-15-2008 02:33 AM

Hello,

I have a strange problem on my standard ispCP RC 6 installation on my debian Server.

In fact, everything concerning the sending/receiving of e-mails works fine, except the sending over smtp from a Mailclient, Thunderbird for example.

First of all, I have to say that the webmail just works perfectly.
The strange "thing" about my smtp Server problem is that I can't get a connection to my server, thunderbird always returns me an error that it didn't managed to connect to the server.

I analyzed several things, I scanned the port range of my server and got the following output (I only pasted the line related to smtp):
25/tcp filtered smtp

which seems to be alright in my eyes, it is filtered to avoid spammers to misuse the server.

Further, I searched the logs of postfix for errors, warnings and so on, but everything is perfect. Then I tried restarting postfix, didn't change anything.

So, again, I have to ask for your help. I would be very pleased if someone could help me.

Thanks a lot & Greetings,
Steven


RE: No SMTP sending but, no errors - joximu - 10-15-2008 08:14 AM

You might telnet your smtp-server and talk with him in smtp language to find the problem.

Also try port 587. And of course send a username/password while sending mails (smtp authentication)

/J


RE: No SMTP sending but, no errors - Sens0r - 10-16-2008 04:58 PM

Well thanks for your answer.

In fact when I try to login on port 25 over telnet I can't get a connection, port 587 just works fine. So I think this should solve the problem...

Thanks,

Steven


RE: No SMTP sending but, no errors - joximu - 10-16-2008 05:39 PM

hm - but port 25 is also important: all receiving mails for this server are arriving on port 25...
so this must also be fixed...

/J