World: r3wp

and what is actually being sent is  .. lf "." lf

gmail just hangs on this because it is expecting to see crlf "." 
crlf

Is it sending lf or is it sending the platform-specific line ending?

Now if you send  crlf "." crlf to smtp.gmail.com, gmail just then 
drops the line on you.

because the port is opened with /lines, it is actually sending crlf 
"." crlf lf

which gmail does not like at all.

so, you have to send crlf ".^M" instead !

I think you can open a port with /lines in a way that specifies the 
line ending string.

I've only tested this on windows .. will have to see what core does 
on linux

but all the internet protocols use crlf and not lf

It seems to me that crlf should be specified as the line ending for 
most internet protocols.

yes

Sorry, you just said that.

took me a few days of puzzling what was going on.

of course ethereal turned out to be no help because I was tracing 
ssl.

This seems like an easy fix to someone who has the time, the SDK 
source and the inclination.

Yep

most of us are missing all three

I'm just missing the time (and the need).

wait! i know why that is happening.

the default for tcp:// is CRLF

BUT the default for ssl:// is LF! that is a bug i reported some time 
ago. (it created problems for https:// too)

you can workaround it by adding a  /with refinement to the open (it 
will not hurt tcp either)

http://www.rebol.net/cgi-bin/rambo.r?id=3532&

Can such /with refinements be added to the default protocols built 
on SSL? It shouldn't hurt when the ssl:// default is eventually fixed.

it was added to http, it should to any other protocol that uses ssl.

but the bug should really be fixed! i have reported it in 2004 ;)

Good to know!

that history is repeating itself :(

Perhaps you can use the /with refinement in your esmtps protocol, 
Graham.

Yeah ..

yes, i think it will work fine if you just open/with

Someone at RT should really go thru the old bugs and make sure that 
they are all fixed

that will eventually happen.

that's why they are in rambo - they won't be forgotten.

is forgetting them better than not fixing them?  I wonder  ;-)

I'm looking at the http protocol source, and I find no indication 
of any fix to the default line ending of ssl:// - do I have the right 
source? It is dated 5-Dec-2005...

same as mine

hmm, was that lost?

my understanding is, that the usage of the /ONLY refinement is an 
error in cases like:

    a-string: ""
    insert/only a-string "ab"


currently REBOL just ignores the refinement, what are your preferences?

what should /only do for strings?

If you carefully read my post, then you may see that you asked the 
same question I did

ok, sorry, I understood it as if you had the answer and wanted to 
hear others first. :-)

I just have my preferences, but don't know what the others prefer

It should put  a string in the position of one char :D
Its an programmer-error. Do we  need a runtime-check?

I guess, that it is simpler to silently ignore the refinement from 
the interpreter designer POV

Ok, I guess, I'm completely misunderstanding the problem. Volker, 
what do you mean by putting a string in the position of one char?

that is what insert/only a-string "ab" requests for, althought it 
cannot be done

ah, so it would replace the character at the position and then insert 
the string from there?

Henrik, look at how  it works with  blocks ;)