Hmmm, that's strange Ingo, cuz the following just worked fine for me:

>> em: make email! "Russ <[EMAIL PROTECTED]>"
== Russ%20<[EMAIL PROTECTED]>
>> type? em
== email!
>> print em
Russ <[EMAIL PROTECTED]>
>> send em "test"
>> 

Received email showed "To: Russ <[EMAIL PROTECTED]>" just as expected.

============================================
At 06:58 PM 10/17/99 +0200, you wrote:
>Hi Chris,
>
>Noone seems to have answerd you, so I'll try ...
>
>I haven't had a look at the selma source code, but I think that this
>behaviour is caused by rebols email data-type:
>
>an email is something like: [EMAIL PROTECTED]
>
>There's no place to save the additional real-name data in this, like:
>
>"Me <[EMAIL PROTECTED]>"
>
>when importing an email header this additional info is stripped.
>You can try the send function:
>
>>> send to-email "me <[EMAIL PROTECTED]>" "This is a test"  
>connecting to: fuchur.2b1.de
>** User Error: Server error: tcp 501 <me <[EMAIL PROTECTED]>>: "@" or "." expected
after "me".
>** Where: insert port reduce data
>
>Maybe someone can convince REBOL Tech, that support of real-name info
>would be desirable.
>
>
>regards,
>
>Ingo
> 
>
>Those were the words of [EMAIL PROTECTED]:
>> I have noticed that in this list (the only one that I'm subscribed to
>> that uses SELMA to my knowledge) the To: and From: headers seem to
>> have data stripped from them.  For example, whenever I send an email,
>> the From: header shows "Chris Elliott <[EMAIL PROTECTED]>"
>> (minus the quotation marks, of course...).  Some where between when I
>> send the mail out, and when I get it back from SELMA, the From: header
>> is stripped down to just the email address.  
><...> 

Reply via email to