Peter Brodersen <usenet@ter.dk> writes:
> Det synes jeg ikke er et godt råd. Jeg synes, man skal gå ud fra at
> headers er RFC2822-compliant.
>
> ==
> [..] A line is a series of characters that is delimited with the two
> characters carriage-return and line-feed; that is, the carriage return
> (CR) character (ASCII value 13) followed immediately by the line feed
> (LF) character (ASCII value 10). (The carriage-return/line-feed pair
> is usually written in this document as "CRLF".)
>
> A message consists of header fields (collectively called "the header
> of the message") followed, optionally, by a body. The header is a
> sequence of lines of characters with special syntax as defined in
> this standard. [..]
> ==
>
> PHP-manualen nævner også:
>
> "Note: You must use \r\n to separate headers, although some Unix mail
> transfer agents may work with just a single newline (\n)."
>
> Hvis man falder over en mailserver, der ikke kan finde ud af CRLF
> (\r\n), så er man alligevel bedre tjent med at holde snitterne langt
> fra den. At begynde at rette kode fra "\r\n" (som altså skal virke)
> til "\n" (som måske kan virke) er ikke et skridt i den rigtige
> retning.
Så blev jeg også klogere i dag, tak
--
Med venlig hilsen
- Jacob Atzen