Thank you! You put me on the right track, anyway.
Since I am reading variables for the user and service, I had to use the
'to-lit-word to make it happen:
user: to-lit-word (username-variable)
service: to-lit-word (server-variable)
set-net [ (rejoin [user "@" service]) (service) none none none none ]
then send works OK.
Interesting note: the parens around the second value (service) apparently
are required to evaluate it, otherwise it tries to connect to the address
"service"! I know the 'rejoin evaluates it's parameters.
Any other comments or clarifications would be great on why this is so.
<snip>
>
> user: 'username
> service: 'mail.server.edu
>
>
> set-net [ (rejoin [user "@" service]) (service) none none none none ]
>
> Note that I ended up using literal words instead of strings for user and
> service and removed your to-url stuff.
>
> Apparently set-net expects literal words in these positions. If you
replace
> them values of type url, then send complains on attempting to open the
port
> (which happens in the second line of send's execution block). Of course
you
> can check that out yourself (if you want), with source send.
>
> Hope this helps
>
> Elan
</snip>
