World: r3wp

.

use with: s: open pop3://user:[pass-:-server] print read s

that should print the num of messages available

after that, print pick s 1 would print the first message

don't worry to much if it doesn't work, though. the design is stupid, 
and i'm reworking that at the moment :)

too*

works :)

nice :)

wait 1 is a linux fix?

yeah, but that's wrong

that should rather be `wait subport`, just like you do in smtp

ok

ok, another version up at http://bolka.at/share/prot-pop3.r[temporary 
url]

same functionality, improved design

the initial read is no longer needed

so try with: s: open pop3://...

print length? s

print pick s 1

stuck at the open

could you try and replace `wait either system/version/4 = 4 [1] [subport]` 
by just `wait 1`

that works

interesting

>> write mbox "RETR 1"
write
** Script error: copy does not allow char! for its value argument
** Where: write
** Near: write mbox "RETR 1"

you need []

and the first item must be solely the command

eg

`write mbox ["RETR" 1]` should work

shouldn't state always be set to 'retr after all write commands?

ie. you always want to get the response until you hit the "."

that's only for multiline commands

or a "+OK" or a "-ERR"

STAT, DELE, RSET only have one-line responses

NOOP

QUIT

(for example, yes)

actually, WRITE exposes the low-level interface here

for RETR, PICK would be the high-level interface

cause I get nothing back aftre

write mbox [ "RETR" 1 ]

etc

read mbox

and you'll get whatever the command handler deems to be the right 
result to pass along

ahh....

write mboxc [ "TOP" 1 10 ]
hangs :)

after the read ...

obviously, as there's no top handling yet :)

write mbox [ "TOP" 1 10 ]
read mbox

not the way it's suposed to work?

I see the top 10 lines and a "."

yes, in the debug output :)

open, length?, pick, close -- that's the currently supported interface

ok :)