My ISP doesn't allow telnet access to the server from outside the system -- unless the individual has been previously authorized to do so. I haven't asked, but I suspect that means either password protection or a special "non-standard" port for acces. The reason is system security. Telnet is one thing if you are simply signing into your account, that could be fine. But a lot of people can't work in Linux/shell environment so ... Bigger problem is telnet into other than login port; it leaves system subject to bad attacks and malicious destruction. For those who cannot use telnet, the other option I've mention here -- going to http://www.startmail.com It can access your mail on the ISPs server, and can even get past the security my ISP has put up. That way you can list your mail, glance at it [you could have figured out what #57 was], delete a message, etc. l.d. ==== On Fri, 21 Jan 2000 13:19:05 -0500, Samuel W. Heywood wrote: > It sure is good to be able to use Telnet in order to deal with the kind of > problem described above. I used to have similar problems every now and > then with the POP3 server at my former ISP. I was always able to simply > delete the offending file from the server simply by using Telnet. With my > current ISP I have so far never suffered the experience of having a message > getting "stuck" on the POP3 server. If I should ever have a problem like > that, I don't know what I could do about it. My current ISP does not even > permit its subscribers to accesss the POP3 server by means of Telnet. > I wonder why they would have a policy of prohibiting Telnet access. Does > anyone have any thoughts on the matter? > Sam Heywood > P.S. To see a web page having really great tips on the usefulness of > Telnetting, go to http://stud1.tuwien.ac.at/~e8926506.siberia.htm > -- This mail was written by user of Arachne, the Ultimate Internet Client -- Arachne V1.60;b1, NON-COMMERCIAL copy, http://arachne.cz/
