Path: csiph.com!usenet.pasdenom.info!aioe.org!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "J.O. Aho" Newsgroups: comp.lang.php Subject: Re: PHP Mailto(); Date: Mon, 01 Jul 2013 19:30:20 +0200 Lines: 22 Message-ID: References: <51d1ba64$0$6547$9b4e6d93@newsspool4.arcor-online.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net lVt4khTKUHiExG5+F3hCHAAvg20K3zANm74FNZp8a1yD8tMZue Cancel-Lock: sha1:pkhhO9XkMxSoy9Z/qWDnycfIGnI= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130628 Thunderbird/17.0.7 In-Reply-To: <51d1ba64$0$6547$9b4e6d93@newsspool4.arcor-online.net> Xref: csiph.com comp.lang.php:10015 On 01/07/13 19:21, Christoph Michael Becker wrote: > J.O. Aho wrote: >> RFC is one thing and PHP uses some replacing of carriage return and new >> lines to make the data sent to the mail sever correct, which makes it >> better to have \r\n on ms-windows, \r on OSX/MacOS and \n on Linux/Unix. > > According to the documentation on php.net[1] it is not PHP that replaces > the line breaks, but some MTAs: Maybe some does, but there is also this nice comment: /* This pattern converts all single occurences of \n (Unix) * withour a leading \r to \r\n and all occurences of \r (Mac) * without a trailing \n to \r\n * Thx to Nibbler from ircnet/#linuxger */ -- //Aho