#1352 [Bgs]: $crlf in Mail_Mime example should be "\n"
| From: | pear dot neufeind at speedpartner dot de | Date: | Fri, 21 May 2004 13:21:51 +0000 |
| Subject: | #1352 [Bgs]: $crlf in Mail_Mime example should be "\n" | ||
| References: | 1 | Groups: | php.pear.doc |
| Request: | Send a blank email to pear-doc+get-4061@lists.php.net to get a copy of this message | ||
Edit report at: http://pear.php.net/bugs/bug.php?id=1352&edit=1
ID: 1352
Updated by: pear.neufeind@speedpartner.de
Reported By: mhaertl at emiga dot de
Status: Bogus
Package: Documentation
Operating System: any
PHP Version: Irrelevant
Assigned To: danielc
New Comment:
I've used the standard-setting of \r\n for quite a while myself, during
development on a project. And I knew it was according to the RFC
(looked that up). But a customer using, if I remember correctly,
Outlook Express said that he had problems that the mail was not
interpreted correctly. Changing the linebreaks to \n helped in that
case. Seems like some Micros*ft-tools are not fully RFC-compliant?
But from the practical point of view, may it be a good idea to at least
mention to try "\n" if you're having problems with certain
Outlook-versions? Even works with just \n on all other mail-clients I
was able to test so far.
Previous Comments:
------------------------------------------------------------------------
[2004-05-21 09:05:09] danielc at analysisandsolutions dot com
Regarding
http://pear.php.net/manual/en/package.mail.mail-mime.example.php
you are saying it contains "\n\r". It contains "\r\n". This has been
the case since the files were uploaded in September 2002. "\r\n" (aka
CRLF) is the correct line separator for mail as per RFC 2822
(ftp://ftp.rfc-editor.org/in-notes/rfc2822.txt).
If you are having problems with your programs, please ask for help on
the pear-general mailing list. Subscribe at
http://pear.php.net/support.php. If people there
indicate there really
is a bug with Mail_MIME, then open a new bug report for the Mail_MIME
package directly rather than the documentation.
Thanks.
------------------------------------------------------------------------
[2004-05-21 04:11:15] mike@php.net
This bug has been fixed in CVS.
In case this was a documentation problem, the fix will show up at the
end of next Sunday (CET) on pear.php.net.
In case this was a pear.php.net website problem, the change will show
up on the website in short time.
Thank you for the report, and for helping us make PEAR better.
Hi, it will show up on Sunday.
------------------------------------------------------------------------
[2004-05-21 04:03:57] mhaertl at emiga dot de
Sorry, but it's still not fixed in the online docs. Have a look:
http://pear.php.net/manual/en/package.mail.mail-mime.example.php
There's still $crlf="\n\r";
------------------------------------------------------------------------
[2004-05-20 10:50:27] danielc at analysisandsolutions dot com
I went to go fix this and found that the change had already been made.
Thanks for your report.
------------------------------------------------------------------------
[2004-05-06 05:52:19] mhaertl at emiga dot de
Description:
------------
In the Mail_Mime Example you use
$crlf = "\n\r";
The Documentation for Mail_Mime::Mail_Mime() says:
'Normaly, it is not necessary to set the $crlf parameter. But, if you
want to send the generated MIME message using Mail then you have to
set $crlf to "\n".'
Since i used the example code i got a lot of trouble with users
receiving illegible MIME mails.
------------------------------------------------------------------------
--
Edit this bug report at http://pear.php.net/bugs/bug.php?id=1352&edit=1