World: r3wp

ahah

no .... it does bad things :)

Graham, you code looks clean, i like it

sever sends me a bye

if you enline the message, it actually sends the complete email

Graham have you an smtp server where we can test your code ?
i don't have one

Not me ... I'm using my ISPs and I don't know my password!

just use your ISP's :)

don't have one

wifi spot

ie. I can't test the authentication because I don't actually have 
an email account with them.

smtp.gmail.com

yeah ... sure :)

465

i just have to create an account on gmail that's right ?

No, gmail only uses secure smtp

ah, forgot about that, yes

mail.gmx.net, then

you don't even need an account, try if you get to the server rejecting 
your message :)

oh .. any isp will do ...

graham, i need the awake handler in port/state/awake to be set, otherwise 
awake doesn't get called

I took it out to see why it was needed :)

I mean I open the port and do a read .. and off goes my email

hmm, doesn't work for me

what do you mean?

the smtp port's awake is never called

ah, i see, you have the awake on the tcp port instead

strange

not strange, it's the only way

fake ports (not tcp one) never receive events

the strange was rather a remark about the script not working for 
me

what happens in the trace?

nothing

but i think i know the reason

it's because the event device is not really working on linux

I mean net-log

if i add a wait 1 after the wait port/state/connection, it's working

cool

gets me to a script error, at least :)

eek!

ok, dropping the write from connect works fine as well

; ready for the next state
				client/spec/state: 'INIT
				; trigger flow of data
				read client

well, this is going to be fun ...

that's what i'm using now

ok, and the script error is in the auth response parsing

because the server i'm testing with doesn't offer any auth at all 
:)

Well, if I do a read in the connect event, I get a 221 response from 
the server

going to try writing a NOOP

221 means ?

waiting for a EHLO ? ahah