dicode

https://github.com/javanile/php-imap2/pull/12 I've fixed most of the issues in BodyStructure.php, perhaps that will help you as well.

@Orgoth I've tested this version on over 2000 e-mails and compared the output to the original imap_fetchstructure function to make sure these matched exactly, I think I got most of...

@Orgoth probably caused by yet another flashy structured e-mail indeed, causing it to break much earlier in parsing and landing here with wrong item data. If you need help just...

@Orgoth To me it seems something before we get into getEncoding is broken, a list of attachments should never arrive at that function. Although your fix hides the issue I...

@Orgoth could you also supply the json encode of the original imap_fetchstructure of the message?

@Orgoth I've fixed the array version, only there is some discrepancy in the output/source for the text/html part ``` ["lines"]=>int(167) ["bytes"]=>int(5493) ``` vs ``` "lines": 194, "bytes": 5852, ``` but...

@Orgoth I will update my patch shortly. For the "*" e-mail, is it possible to get the raw IMAP response from the FETCH command? Perhaps by using telnet to speak...

https://github.com/javanile/php-imap2/pull/12/commits/2874eb99723414e2951596bf6ab5563ec5eeda28 is the new commit for the array issue, this was caused by how a related part was parsed.

Fixed in https://github.com/javanile/php-imap2/pull/12/commits/f119d258b22e1c340bacaa53c7fbe5b8e38d94bd No need to compensate, I need this php-imap2 library working properly too :-)

Fixed in https://github.com/javanile/php-imap2/pull/12/commits/2fe8fade8e5091a90a47155f707f84ea64fa69b9 However the output still differs in line/bytes on the RFC822 part but possible thats caused by the different imap servers used.