-=> CHARLES ANGELICH wrote to WAYNE CHIRNSIDE <=-

 WC> Still haven't figured out what Verizon mail wants for
 WC> authentication in SMTP despite many attempts. I've got to
 WC> figure out what file defines what is in the mail.conf file
 WC> and what Verizon's SMTP wants for authemtication.

 CA> Lately many ISPs require that you use your POP3 access before
 CA> using SMTP in an attempt to discourage spamming.

The author of Basic Linux suggested the same, didn't
work. There's a very brief message flashed on the 
screen error 553, I think that's the number, "authentication
failure."

 WC> Soon as X-Windows flies I'm nuking the old Slackware
 WC> release and upgrading to 8.1 I'm going to have to link up
 WC> some files as you suggested as my POP3 mail still insists I
 WC> insert a disk with relavent info from the earlier ramdrive
 WC> version first unless I merely open and close that file on
 WC> the hard drive, than all proceeds smoothly with no need for
 WC> that disk.

 CA> If this is what I had to deal with it was that a part of the
 CA> 'pppsetup' script was required to do ppp logins and it included
 CA> the request to read the floppy. I rewrote this and haven't been
 CA> bothered about floppies since then. :-)

I must do the same!
Until then I still don't bother about floppies
just open and close the config file changing nothing.
Actually I've been meaning too try just invoking and exiting
pppsetup and seeing if that works until I employ a more
permanent fix. Until then other priorities shall prevail.

 WC> Read my old Slackware book and found it wanting in many
 WC> areas but one place it excells and that's the explaination
 WC> of the VI editor which though less comprehensive gets me
 WC> going again far quicker than the book I have on that editor.

 CA> I've always found VI to be not logical. There is no 'scent'
 CA> that I can detect to follow the logic of what keys do what and
 CA> when. How anyone gets 'used' to VI is beyond me.

I can easily understand that.
How I originally became familiar was I was going to school
with a real gung ho programmer and he tippped me
to about 11 core commands of great power that made editing
dead easy. The books are not at all intuitive.
What I NEED to do is look to the command quick reference
appendix and search out those core commands I found so useful
as I'm sure to recognize them and it will all come back to me.
I once wrote over 800 lines of working source code in one
8 hour stint taking no lunch or coffee breaks with VI, now VIM.
Damned administrator nuked the server before I could save
my previous weeks files to disk and I'm still damned mad about that.
I made tremendous progress in weeks three and four into the C 
programming course.  Was calling external files from functions,
retrieving data, modifying external files, employing
multidimensional arrays, ect.
Pretty cool stuff but all I've got on disk is the first
lousy simplistic couple of weeks of stuff :-(
Damned administrator reconfigured the network so we
couldn't access the A drive to save files or work at home
making me wonder why all us students had blown around
three grand on computers $YU%UY&$!!{at}!
 
--- MultiMail/PBellDOS v0.42