Path: csiph.com!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!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:05:46 +0200 Lines: 37 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net jWIgfpoFLKku1h/EIAo2Iw21KIYsjloUlu1MexCiLaYGKLY60A Cancel-Lock: sha1:948uQ9QVsE5BJDnUilbI7SOyRbc= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130628 Thunderbird/17.0.7 In-Reply-To: Xref: csiph.com comp.lang.php:10012 On 01/07/13 17:34, Tim Streater wrote: > In article , Twayne > wrote: > >> On 2013-07-01 7:50 AM, bill wrote: >> > On 6/30/2013 7:29 PM, Twayne wrote: >> >> Hi,; > >> >> I've tried the Headers method, simply adding them inlilne. No Good. >> >> I've also tried "and"ing things together like " $comments . >> >> $respond " for instance, but then they all run together and it's >> >> difficult to spot the additional information since there are no >> >> line breaks. > >> > I do believe that you use \n for a new line in the body of the email. >> > >> >> If anyone is interested, there seems to be a pretty good Q&A for EOL at: >> >> http://stackoverflow.com/questions/128560/when-do-i-use-the-php-constant-php-e >> >> ol >> >> Almost all the pros & cons are sensible, thought-out comments. > > How about reading the RFCs to see what you are *actually* supposed to > do. Such as RFC 2821 section 2.3.7. 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. -- //Aho