-
Notifications
You must be signed in to change notification settings - Fork 8
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
Fixed "Invalid header value detected" when sending an email to a pers… #10
base: master
Are you sure you want to change the base?
Conversation
…on with a name containing non-ASCII characters * Laminas addHeaders expects ASCII characters only * Using LaminasMessage::addTo circumvents this check
I'm not sure this is the correct solution here. The documentation indicates that ASCII is simply the default, but it clearly illustrates adding a To address with a different encoding: I think instead of this roundabout approach, it may be sufficient to simply add: $message->setEncoding('UTF-8'); If that approach is taken, a couple other notes (old articles, so not sure if still relevant):
I'm not currently set up to be able to test this to confirm, though. |
I see. I think I might have tried that, although it was a while back. All that it's doing, is using the Lamina's Message But maybe forcing the encoding will convert the headers as well? |
…ect containing non-ASCII characters
…-8-compatible added magento 244 and php 8 compatibility
…o2-246-php82-compatible added magento 2.4.6 composer compatibility
…nnamic-property-issue changed dynamic property declaration
…orting Improve error reporting
…on with a name containing non-ASCII characters
Fixes #9