On Tue, December 11, 2007 4:24 pm, Daniel Brown wrote:
On Dec 11, 2007 12:20 PM, Richard Lynch [EMAIL PROTECTED] wrote:
I dunno if RFC822 specifies which ending but I *do* know that this
breaks the current PEAR mimePart.php code.
RFC 822 has been obsolete since RFC 2822 was introduced
On Dec 15, 2007 1:09 PM, Richard Lynch [EMAIL PROTECTED] wrote:
A standard nobody follows isn't a standard; It's a waste of paper.
Only if you printed it out in the first place. ;-P
That aside, I completely agree with you. It's sort of like the ^M
versus \n versus \r\n line
Robert Cummings wrote:
Yeah, he's all over the place with his line endings. Personally, I use
an array to track the headers and use implode in one shot before
sending.
Cheers,
Rob.
Same here
--
Jim Lucas
Perseverance is not a long race;
it is many short races one after the
If you want a source to very verify against, send yourself an email,
then view it's source; then change your class till it outputs the same
info, gauranteed winner every time.
Nathan
Jim Lucas wrote:
Robert Cummings wrote:
Yeah, he's all over the place with his line endings. Personally, I
Until today, there was a very nifty MIME Message Lint tool to check
your email message here:
http://www.apps.ietf.org/msglint.html
The homepage is now the default Apache install page though, and that
URL is 404.
I'm posting it in hopes that somebody knows a good similar tool and/or
that it will
PS
GMail will not accept \r\n between header lines, only \n
I dunno if RFC822 specifies which ending but I *do* know that this
breaks the current PEAR mimePart.php code.
Editing the code to hack \r\n to just \n for the _CRLF constant works
for gmail, but may break other mail clients if \r\n is
On Dec 11, 2007 12:20 PM, Richard Lynch [EMAIL PROTECTED] wrote:
PS
GMail will not accept \r\n between header lines, only \n
I dunno if RFC822 specifies which ending but I *do* know that this
breaks the current PEAR mimePart.php code.
Editing the code to hack \r\n to just \n for the _CRLF
heh Richard! long time no see, guess you had withdrawal symtoms or you
managed to bust out of whatever compound they were holding you in ;-) ...
Richard Lynch wrote:
PS
GMail will not accept \r\n between header lines, only \n
I dunno if RFC822 specifies which ending but I *do* know that
On Dec 11, 2007 12:20 PM, Richard Lynch [EMAIL PROTECTED] wrote:
I dunno if RFC822 specifies which ending but I *do* know that this
breaks the current PEAR mimePart.php code.
RFC 822 has been obsolete since RFC 2822 was introduced in 2001.
We (that is, myself and other members of the
Dear All,
i wrote this class below to send Mail. but when i use it. i get the sender
No Body. and from the address of the server, not the From address that i
specify. and the MIME Headers as text in the message itself. and the
attachment is pasted as binary text also.
can anyone help please ??
On Tue, 2007-12-11 at 06:33 +0200, Me2resh Lists wrote:
Dear All,
i wrote this class below to send Mail. but when i use it. i get the sender
No Body. and from the address of the server, not the From address that i
specify. and the MIME Headers as text in the message itself. and the
Me2resh Lists wrote:
Dear All,
i wrote this class below to send Mail. but when i use it. i get the sender
No Body. and from the address of the server, not the From address that i
specify. and the MIME Headers as text in the message itself. and the
attachment is pasted as binary text also.
can
Robert Cummings wrote:
On Tue, 2007-12-11 at 06:33 +0200, Me2resh Lists wrote:
Dear All,
i wrote this class below to send Mail. but when i use it. i get the sender
No Body. and from the address of the server, not the From address that i
specify. and the MIME Headers as text in the message
On Mon, 2007-12-10 at 21:05 -0800, Jim Lucas wrote:
Robert Cummings wrote:
On Tue, 2007-12-11 at 06:33 +0200, Me2resh Lists wrote:
Dear All,
i wrote this class below to send Mail. but when i use it. i get the sender
No Body. and from the address of the server, not the From address that
14 matches
Mail list logo
