🚀 go-pugleaf

In article <860400733snz@dsl.co.uk>, Brian {Hamilton Kelly}
<bhk@dsl.co.uk> writes
>carry *all* the RFCs in an FTP archive.  Throw away that new-fangled web
>crap and point an FTP client at your nearest (electonically) FTP archive.

In hindsight, yes I wish I'd thought of doing that. That said I don't
spend much time looking at stuff such FTP sites, or usually know where
to look when I do, so a search engine seemed like a good idea. Plus if
you have RSI, less typing. Mind you, had I known exactly what I wanted
(the URL you quoted in a previous article) I would've been fine.

>For example, all the RFCs can be found at Demon, on ftp.demon.co.uk, in
>the directory /pub/doc/rfc.  There's a number of files therein that are
>indices to the various RFCs, STDs, FYIs, etc.

Thanks.

I've got a sample POP3 client working, with no error checking, so I'll
no implement the real thing. Several things were going wrong. I'll list
them here for you all to guffaw at:-

1) Yes I wasn't waiting for the +OK demon ready message
2) Initially I was terminating in \n, which then got changed to \r\n\n
Thats what you get for the typo of print/println (which adds the \n)
such that the USER phrase was accepted but -ERR was response for PASS
phrase.
3) Parsing of number of messages was slightly out.
4) My comment about Turnpike, well that was overzealous drunken
misunderstanding of the instructions late at night. Garbage in/Garbage
out.

Many thanks for your help and the help of the other contributors to this
thread.
-- 
Stephen Kellett
Object Media Limited    Unix/C++/Java/Windows/X Windows/Multimedia
If you are suffering from RSI, contact me for advice.
Unsolicited email from spam merchants not welcome.