Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PHP error when attempting to open a message with a message/rfc822 part #8953

Closed
GTMSMitch opened this issue Mar 23, 2023 · 4 comments
Closed

Comments

@GTMSMitch
Copy link

This error occurs when attempting to view a message which has another message attached as a 'message/rfc822' part. RoundCube displays an "Oops.. Something went wrong!" internal error, and the error logs display "Uncaught TypeError: strtolower(): Argument #1 ($string) must be of type string" on line 2149 in rcube_imap.php. These messages display as expected in other email clients.

I am using Roundcube version 1.6.1, Apache version 2.4.56 and PHP version 8.2.4 but I have tried with previous versions of PHP and Apache and encountered the same issue.

I've attached an example email that causes the issue:
DisplayErrorEmailText.txt

@GTMSMitch
Copy link
Author

GTMSMitch commented Mar 24, 2023

Update: Can replicate simply by creating an email using RoundCube and either forwarding as an attachment or attaching an EML file using the "Attach a file" button on the right hand side.

I have previously seen attaching EMLs in this way working and displaying as normal because they were attached as a text/html part rather than a message/rfc822 part, however I'm unsure as to what combination of RC / Apache / PHP this was.

@alecpl
Copy link
Member

alecpl commented Mar 24, 2023

Duplicate of #8803.

@alecpl alecpl closed this as completed Mar 24, 2023
@alecpl
Copy link
Member

alecpl commented Mar 24, 2023

But it supposed to be fixed in 1.6.1 and I'm unable to reproduce using git-master. So, I'm not sure.

@alecpl
Copy link
Member

alecpl commented Jul 9, 2023

Actually this might be another issue. I was still not able to reproduce and I think it may depend on the content of your IMAP server response. Anyway, I added some code that should prevent the error to appear.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants