🚀 go-pugleaf

RFC822 says you can have "bare" CR's and LF's in header text.  For
example, the definition of the lexical token "text" (Section 3.3, page
10) reads as follows:

    text  =  <any CHAR, including bare    ; => atoms, specials,
	      CR & bare LF, but NOT       ;  comments and
	      including CRLF>             ;  quoted-strings are
					  ;  NOT recognized.

Also, the discussion on quoting (Section 3.4.1, page 11) mentions that a
CR must be quoted (i.e., preceded by a backslash) if it occurs within a
quoted string, domain literal, or comment.  This is, I suppose, implicit
evidence that someone thinks CR's or CRLF's could appear in addresses.

What I want to know is -- does ANYONE, ANYWHERE, use (or intend to use)
"bare" CR's or LF's in addresses, or indeed anywhere else in a header?
(I am, of course, not talking about the CRLF end-of-line delimiter.)

    Rich Wales
    UCLA Computer Science Department
    3531 Boelter Hall // Los Angeles, CA 90024 // (213) 825-5683
    ARPA:  wales@UCLA-LOCUS.ARPA
    UUCP:  ...!{cepu,ihnp4,trwspp,ucbvax}!ucla-cs!wales