Am 07.02.2002 00:31 meinte Karsten D�sterloh schreiben zu m�ssen:
>Hi!
>
>Graphity wrote:
>
>>Jeah. You're right. I'm sorry I didn't check the old e-Mails for that...
>>
>
>Old e-mails?!?
>
I was talking 'bout the old threat...
>>but what about #Cc or Cc# mail-addr ? would this be ok?
>>I read the RFC 2822 and didn't find anything. It's not the adress that
>>should be interpreted by the mail-server but just by mozilla which
>>changes it to smtp-server-rfc-2822-compliant-mail
>>Got what I mean?
>>
>
>Well, I think so.
>
>Nevertheless I reread RFC2822. Section 3.2.4 at least makes the # a
>non-option. But section 3.4 allows this 'group'-thing, which possibly
>can take the form "bcc:;" - but what if someone wants to write a bcc: to
>a list called "bcc:"?
>
>You need to find a dividing character, that is not allowed in the
>address fields, but still enterable via the keyboard. Section 3.2 as a
>whole makes this pretty hard... ;-)
>
>
>Karsten
>
I just tried to read the rfc but nearly fell asleep. I fighted with me
to read at least the 3.2 till 3.4 sections. But it's apity, I don't
understand how rfc are written. Is the a "how to read rfcs" or something
around?
What about "&bcc:;" just like writing special characters in HTML?
Or, just like invoking Javascript you start a comment which should not
be read by the mail-composer.
Like '"bcc:"' or something? You see, the "-character has no meaning
cu
Graphity
