SMTP Problem

Golem · 01-30-2002, 08:00 AM

Hi folks,

I seem to be having a problem with SMTP connecting and sending my mail. I am using the latest version of Netscape mail and I have configured the POP and SMTP servers properly as provided by my ISP. I can get my mail from the POP server no problem at all. Sending mail through the SMTP server will not connect. Netscape just sits there trying to connect until it times out.

Any suggestions?

- Mike
Red Hat 7.2

alfie · 01-30-2002, 08:44 AM

Quote:

Originally posted by Golem
Sending mail through the SMTP server will not connect.

Have you tried from a shell to telnet to your SMTP Server on Port 25? It should look like the following:

Code:

user@host:~ > telnet smtp.my.provider 25
Trying 10.10.10.10...
Connected to smtp.my.provider
Escape character is '^]'.
220 smtp.my.provider ESMTP Exim 3.34 #1 Wed, 30 Jan 2002 15:49:45 +0100

Something like that. Of course use your own smtp.my.provider and you will get a different 220 message. You can exit from there with QUIT.

If you can't connect there should be some error message that might enlighen you. You can also try to traceroute to that address to see if you can at least reach the server...

HTH,
Alfie

Golem · 01-31-2002, 06:53 AM

Thanks for the reply!

I tried to telnet to my smtp server and it worked fine. Then, last night, it just started working. I didn't do anything that I'm aware of....

Well, it works, that's the important thing.

Now just a few more hiccups to work out and I'll be happy.

Thanks for the help!!

- Mike

lfslinux · 01-31-2002, 07:05 AM

Quote:

Originally posted by Golem
Thanks for the reply!

I tried to telnet to my smtp server and it worked fine. Then, last night, it just started working. I didn't do anything that I'm aware of....

Well, it works, that's the important thing.

Now just a few more hiccups to work out and I'll be happy.

Thanks for the help!!

- Mike

For all you know it could have been your ISP who's smtp server was down. That's where telnet comes in to be a handy tool next time so you can check it right away and can determine whether or not your system is the culprit, or elsewhere.