Description: ------------ 468c468 < if (is_array($param_value) AND $param_value[0] == '"') { --- > if ($param_value[0] == '"') { Test script: --------------- <?php require_once("Mail/mimeDecode.php"); // this is an email we received $string = file_get_contents("http://www.emailcenteruk.com/pear_report/example_email.eml"); $params = array(); $params['include_bodies'] = true; $params['decode_bodies'] = true; $params['decode_headers'] = true; $parser = new Mail_mimeDecode($string); $structure = $parser->decode($params); print_r($structure); ?> Expected result: ---------------- The structure of the email is printed without any errors/notices. Actual result: -------------- The structure of the email is printed with the notice: Notice: Uninitialized string offset: 0 in /usr/share/php/Mail/mimeDecode.php on line 468

Changed summary to be more descriptive...

Moved to Mail_MimeDecode subpackage.

The suggested fix is wrong. $param_value is a string, and $param_value[0] is used to get the first character. The problem occurs, when $param_value is "", e.g. when a header like the following is encountered: Content-Type: text/plain; charset= Headers like these occur regularly in bounce messages generated by some mailservers. A better fix is something like this: - if ($param_value[0] == '"') { + if (substr($param_value, 0, 1) == '"') {

Any chance a fix for this will make it in the next release? I'd rather not have to use @ to mute errors from decode().

This is a very straightforward, one-line fix, please apply. The notice can be triggered by any empty content type parameter, e.g.: Content-Type: multipart/signed; boundary="=_2tcul05gfp2c"; protocol="application/pkcs7-signature"; micalg="sha1"; name=""