You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have the same issue. This is triggered by Emails (like from apple mail), which are very simple plain text mails. Many mail programs create a multipart-message with a separate part for plain text, even if there is only plan text. apple mail (and maybe others) create a mail with the content-type in the header like this
"Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 (3826.500.181.1.5))
X-Mailer: Apple Mail (2.3826.500.181.1.5)
simpleplaintextcontent"
These emails content is empty with php-imap. The native php extension shows the content (retrievable from structure). Even more strange: If you receive the raw email, it is also empty.
Diving into php-imaps code.
the function ->content( in
/php-imap/src/Connection/Protocols/ImapProtocol.php: 882
public function content(int|array $uids, string $rfc = "RFC822", int|string $uid = IMAP::ST_UID): Response {
gets data from the ->fetch( function. For the body part of these emails. Fetch retrieves an empty result
The code of the fetch function, using imap protocol is too complex for my abilities. please help. I can send one of these emails to a testing address
Describe the bug
I have an email, where I check, what type, HTML or Text
$text_body = $message->hasTextBody();
$html_body = $message->hasHTMLBody();
Used config
Please provide the used config, if you are not using the package default config.
Code to Reproduce
The troubling code section which produces the reported bug.
Expected behavior
all are empty and not one of them is 1
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop / Server (please complete the following information):
Additional context
Add any other context about the problem here.
i think it has to do with the marked in the screenshot
The text was updated successfully, but these errors were encountered: