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

Parsing email attachment on error encoding #232

Open
smariussorin opened this issue Mar 15, 2024 · 1 comment
Open

Parsing email attachment on error encoding #232

smariussorin opened this issue Mar 15, 2024 · 1 comment

Comments

@smariussorin
Copy link

smariussorin commented Mar 15, 2024

Hi,

Using $message->getAllAttachmentParts();, we get the following error "mb_convert_encoding(): Illegal character encoding specified".
Most of the time, the attachment is inline.
Is there any way we can get the attachments, ignoring those failing?

I tried setting the encoding to UTF, but did not help.

@zbateson
Copy link
Owner

Hi @smariussorin --

I've been knee-deep working on a version 3 and seem to have missed this. Version 3 will hopefully be released in a few days, but generally that shouldn't have prevented parsing or stopped anything as far as I'm aware? Was that just something being logged?

Anyway, please have a go with 3 and include more details about what's happening: Can you reproduce it reliably with a test email? Does it happen if you call getPart() on a specific part? What's the character encoding of the part, and what's it happening on? In order to figure out the problem, I'd need to be able to see it happening.

All the best

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

No branches or pull requests

2 participants