Help please with Email

Originally Posted by timwilky

I agree with TSM, attempt to simulate a SMTP session using the telnet port 25 to your service provider.

Now then. When things started failing on my smtp I found it was the sneaky gits at McAffee to blame. their virusscan was blocking tcp port 25

Errr yeah, that'll be it. Now why didn't I think of that before.

Ah yes I remember now. It's cause I know F.... all about what they are talking about.

[timwilky]

Don't worry Simon.

Using telnet with an address and tcp port number is an easy way to check routing firewalls and existence of a remote listener service.

for instance if you were having problems talking to the forum and wanted to check if there was something wrong at a network level. a quick "telnet forums.sv650.org 80" from a command prompt would check there is nothing blocking the routing etc.

[TSM]

Originally Posted by timwilky

Don't worry Simon.

Using telnet with an address and tcp port number is an easy way to check routing firewalls and existence of a remote listener service.

for instance if you were having problems talking to the forum and wanted to check if there was something wrong at a network level. a quick "telnet forums.sv650.org 80" from a command prompt would check there is nothing blocking the routing etc.

yep but with telnet to the forum you will have to the put GET / afterwards to get the server to show the output to the telnet session.

[timwilky]

True, true TSM. I wasn't going to go into the protocol dialogs as I think we have already ventured into extreme geekdom simply by knowing telnet can be used for anything more than a terminal connection to a geeky computer system.

although in my example you would get the connection. This to me is enough to indicate that the remote listener has accepted the connection and forked the appropriate handler and thus we again venture into geekdom.

Nuff said. It is a very useful diagnostic tools only used by yup you guessed. Geeks

[TSM]

Originally Posted by timwilky

True, true TSM. I wasn't going to go into the protocol dialogs as I think we have already ventured into extreme geekdom simply by knowing telnet can be used for anything more than a terminal connection to a geeky computer system.

although in my example you would get the connection. This to me is enough to indicate that the remote listener has accepted the connection and forked the appropriate handler and thus we again venture into geekdom.

Nuff said. It is a very useful diagnostic tools only used by yup you guessed. Geeks

Ahh yep, too geeky

Anyway for everyone else, in a telnet session, as long as it does not close imediatly or just stick on "Connecting to ....." but moves to somthing else then the remote computer is there, if it does the prev mentioned things then there is an issue.

Just a note, on vista you cant put telnet into the run type box in the start menu, it does not work, you have to type "cmd" first then type the telnet bit in from the command line.