On Sun, 15 Jul 2001 10:04:13 +0000, Ron Clarke wrote:
<snip>
> Yes, I guess it has. Probably just as well. I think I need
> instruction.
The first time I read Ron's message, my silent response was ME TOO!!!
But being the bullheaded female I am, I kept reading Glenn's
instructions and trying to get the server to work so I could do my
thing.
First Lesson: TelNet is not for the general dozerwarez using public
Second Lesson: Instructions given for telnet have to be *very* clear
Third Lesson: When reading instructions for telnet, user must NEVER
assume s/he knows what is meant.
Like Ron, I have telnetted directly into an ISP to access my account;
the server *always* prompts for user & password.
I have also done a LOT of shell account accessing for FTP, and once
again the server *always* prompts for user & password.
And I have used Telnet to access my shell account, and yet again the
server *always* prompts for user & password.
What Glenn didn't say, and what I didn't understand, is that the server
will NOT always prompt for authorization ... and port 110 is one place
where it doesn't. [It had me pulling out my already thin hair.]
When one telnets into a mail server, one must do *all* the authorization
work from scratch.
At the prompt the user must type USER personal.username <enter>
If nothing shows up except another blank prompt, so far so good ... <G>
At the prompt the user must type PASS personal.password <enter>
At that point you should see a message saying you're on and good to go!
There are tricks to learn for handling mail via telnet which I'm not
going to go into here. But I'll give you a hint: If you don't
currently use POP3.log then turn it on the next time you download mail;
you can then look at it to see the commands your server accepts and what
each command can do. And the ALT-H in the telnet package *can* be a big
help, even if you screw up like I did a few times.
l.d.
-- Arachne V1.70;rev.3, NON-COMMERCIAL copy, http://arachne.cz/
