PEAR is discontinued

This is a static archive preserving historical releases and metadata. No new packages or updates will be published. For updates to existing packages, or to publish new packages, please use Composer and Packagist.

Home » Mail » Mail_Mime » Bug #6372

empty content-id field (RFC 2112 compliancy)

Details

Submitted2005-12-30 11:36 UTC
Frommail4eko at gmail dot com
StatusBogus
PackageMail_Mime
PHP Version5.0.4
OSXP
Roadmaps(Not assigned)

Comments

[2005-12-30 11:36 UTC] mail4eko at gmail dot com

Description:
------------
Hi,
it seems there are some trouble while interpreting an RFC 2112 (multipart/related) message. [content-id] attribute is missing

output of a print_r($structure):

[headers] => Array
(
[content-type] => image/jpeg; name="002.jpg"
[content-transfer-encoding] => base64
[content-id] =>
[content-disposition] => inline; filename="002.jpg"
)

Mail parsed:
Content-Type: image/jpeg;
name="002.jpg"
Content-Transfer-Encoding: base64
Content-ID: <part1.07000300.03090102@gmail.com>
Content-Disposition: inline;

Test script:
---------------
I think there is no need. If you need an example please contact me , I'll set up something

Expected result:
----------------
[headers] => Array
(
[content-type] => image/jpeg; name="002.jpg"
[content-transfer-encoding] => base64
[content-id] =>
[content-disposition] => inline; filename="002.jpg"
)

Actual result:
--------------
[headers] => Array
(
[content-type] => image/jpeg; name="002.jpg"
[content-transfer-encoding] => base64
[content-id] => <part1.07000300.03090102@gmail.com>
[content-disposition] => inline; filename="002.jpg"
)

[2005-12-30 11:42 UTC] mail4eko at gmail dot com

You should substitute what I've written in the Expected result whit what I've written in the Actual one. Soeey for this.

[2005-12-30 14:05 UTC] richard at php dot net

Thank you for taking the time to write to us, but this is not
a bug.

If you're viewing the print_r in a browser then the content id will be hidden due to the < and > at either end, (ie. it will be interpreted by the browser as a tag).

[2005-12-30 16:18 UTC] mail4eko at gmail dot com

Tnx a lot for your support, so glad that you've answered so fast! :)

Something still sounds strange to me:
the same function, upper, for the same parsed e-mail, print this:

stdClass Object
(
[headers] => Array
(
[from - tue dec 27 22] => 33:04 2005
[x-mozilla-status] => 0001
[x-mozilla-status2] => 00800000
[message-id] => <43B1B305.5090307@gmail.com>

and the part that's been parsed is this:
From - Tue Dec 27 22:33:04 2005
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00800000
Message-ID: <43B1B305.5090307@gmail.com>
Date: Tue, 27 Dec 2005 22:32:53 +0100
From: qweryboy <dummy@dummy.dummy>

(From modified for privacy ;) )

Is there any different parsing between headers and attributes?
Tnx again!
E.