>> You must use <literal>\r\n</literal> to separate headers, although >> - some Unix mail transfer agents may work with just a single newline >> - (<literal>\n</literal>). >> + some Unix mail transfer agents replace <literal>\n</literal> by >> + <literal>\r\n</literal> automatically (leads to doubling >> + <literal>\r</literal> if <literal>\r\n</literal> is used).
Aidan Lister wrote: > The problem with this is \n is wrong, and \r\n is right. If you're a new > user, and you read the above, what would you use? I'd most certainly use \n, > which is exactly what we don't want, right? Both of \n and \r\n can be wrong, it depends on the transfer agent. Some Unix transfer agents replace \n with \r\n so using \r\n will lead to \r\r\n - it's wrong the same as plain \n is. Jakub Vrana
