Re: correct email formatting

From: Date: Thu, 28 Sep 2000 03:47:29 +0000
Subject: Re: correct email formatting
References: 1 2 3  Groups: php.general 
Request: Send a blank email to php-general+get-17852@lists.php.net to get a copy of this message
On Thu, 28 Sep 2000, Justin French wrote: > David Robley wrote: > > > Funny - I just quoted that at someone here yesterday :-) > > > > Stab in the dark time, as I don't know for sure, but.... Looking in my > > mailbox (on a Linux system), I find that it's 0A hex or linefeed which is > > the system EOL marker. And a look in my NT thing's mail shows 0D0A which is > > the MSDOS EOL. So my guess is - use the system EOL for whatever system you > > are working on. > > > > Course I suppose you could do a replace in any case to convert say CRLF to > > just LF or CR to LF (for Mac EOL to *nix) or somesuch. > > > I'm on a FreeBSD box both for local development > and for live pages. > > Does splitting on \n\r seem likely? > > Sorry, got no clue when it comes to linefeed, > new lines, carrige returns, ASCI, and all that :) Dear oh dear, what _are_ they teaching the young these days ;-( > I know I could simply test it, but I was after > something more reliable than "it works for this > email sender, on this server, today" kinda thing. > > Justin French FreeBSD is *nix so your separator between header and body should be allee same like mine, \n\n. But I'd suggest you test for all possible configurations and convert them to a single format, just to be on the safe side. Your possiblities are: *nix - \n\n DOS - \r\n\r\n Mac - \r\r (I think, check this out seeing you are using a PPC) so you'd want to change say any \r\n to \n Any \r to \n and then search for \n\n as the separator. That should work on most anything except something that uses another EOL combination :-) -- David Robley | WEBMASTER & Mail List Admin RESEARCH CENTRE FOR INJURY STUDIES | http://www.nisu.flinders.edu.au/ AusEinet | http://auseinet.flinders.edu.au/ Flinders University, ADELAIDE, SOUTH AUSTRALIA

« previous php.general (#17852) next »