r3wp [groups: 83 posts: 189283]
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

World: r3wp

[!REBOL3 Schemes] Implementors guide

Graham
8-Jan-2010
[545x2]
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
Andreas
8-Jan-2010
[547]
hmm, doesn't work for me
Graham
8-Jan-2010
[548]
what do you mean?
Andreas
8-Jan-2010
[549x3]
the smtp port's awake is never called
ah, i see, you have the awake on the tcp port instead
strange
Steeve
8-Jan-2010
[552x2]
not strange, it's the only way
fake ports (not tcp one) never receive events
Andreas
8-Jan-2010
[554]
the strange was rather a remark about the script not working for 
me
Graham
8-Jan-2010
[555]
what happens in the trace?
Andreas
8-Jan-2010
[556x3]
nothing
but i think i know the reason
it's because the event device is not really working on linux
Graham
8-Jan-2010
[559]
I mean net-log
Andreas
8-Jan-2010
[560]
if i add a wait 1 after the wait port/state/connection, it's working
Graham
8-Jan-2010
[561]
cool
Andreas
8-Jan-2010
[562]
gets me to a script error, at least :)
Graham
8-Jan-2010
[563]
eek!
Andreas
8-Jan-2010
[564x2]
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
Graham
8-Jan-2010
[566]
well, this is going to be fun ...
Andreas
8-Jan-2010
[567x3]
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 
:)
Graham
8-Jan-2010
[570x2]
Well, if I do a read in the connect event, I get a 221 response from 
the server
going to try writing a NOOP
Steeve
8-Jan-2010
[572x2]
221 means ?
waiting for a EHLO ? ahah
Andreas
8-Jan-2010
[574x2]
could you try `system/contexts/system/read client` instead
please
Graham
8-Jan-2010
[576]
still triggers a 221 from the server
Andreas
8-Jan-2010
[577x3]
very strange
or, well
what do you get if you simply telnet to the server?
Graham
8-Jan-2010
[580x3]
221 	<domain> Service closing transmission channel
works fine with R2
>> c: open/lines tcp://smtp.clear.net.nz:25
>> pick c 1
== "220 smtp4.clear.net.nz -- Server ESMTP (CLEAR Net)"
>>
Andreas
8-Jan-2010
[583x2]
hm, works for me
port opened ...
waiting on port
=== Client event: lookup
=== Client event: connect
connected
=== Client event: read
S: 220 smtp4.clear.net.nz -- Server ESMTP (CLEAR Net)

C: EHLO my-r3-developement-pc
Graham
8-Jan-2010
[585x2]
hmm.. spelled development wrong
I guess others need to test ...
Andreas
8-Jan-2010
[587]
hehe
Graham
8-Jan-2010
[588x4]
I'm on windows 7
Fixed the typo :)
this is some other code I had lying around..

		DATA [
			either code = "354" [ 
				message: first messages
				replace/all message "^/." "^/.."
				insert smtp message
				insert smtp "."
				print "message inserted"
				either tail? messages: next messages [
					state: 'END
				][
					state: 'FROM
				]
			][
				print "Not letting us send .. so quit"
				break
			]
		]
so that you can send a block of messages ....
Andreas
8-Jan-2010
[592]
nice
Graham
8-Jan-2010
[593x2]
needs to be fixed ...
never tested ... I guess you need to find the to address and switch 
states ... etc