Magento 2.3.5-p2 issue on sending email with Chinese Sender Name "Invalid header value detected"

[arslan-eg]

Summary (*)
When a customer or user wants to change its password in his dashboard password change option. If the Store Email Addresses configuration (Admin->stores->settings->configurations->general->Store Email Addresses->Customer Support->Sender Name) is set in Chinese e-g "蘭芝台灣" and save configuration. In this scenario email is not sending and shows the error "Invalid header value detected".

Preconditions (*)

1. Magento 2.3.5-p2
2. Sender name in configuration is set in Chinese.

Steps to reproduce (*)

1. In Admin Panel navigate to (Admin->stores->settings->configurations->general->Store Email Addresses->Customer Support->Sender Name).
2. Add Sender Name in Chinese e-g "蘭芝台灣" and save configuration
3. Login at website then navigate to My Account->Change Password and click on change password and add new password

Expected result (*)

1. Email should be send to the user when he changed the password.

Actual result (*)

1. Email is not received by the user and shows the error flash message "Invalid header value detected"

Further Details(*)
Video recording of this issue

[m2-assistant]

Hi @arslan-eg. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-Alfa. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Alfa]

Hi @arslan-eg . Thank you for your report!

Unfortunately, we are not able to reproduce the issue on fresh 2.4-develop.

Manual testing scenario:

1. In Admin Panel navigate to (Admin->stores->settings->configurations->general->Store Email Addresses->Customer Support->Sender Name).
2. Add Sender Name in Chinese e-g "蘭芝台灣" and save the configuration

3. log in to Storefront, then navigate to My Account->Change Password and click on change password and add a new password

Actual Result: ✔️ An email is sent to the user when he has changed his password.

@arslan-eg Maybe we missed some details? Could you take a look?
Thanks!

[arslan-eg]

Hello @engcom-Alfa Thank you for your response.

I'm using magento version 2.3.5-p2. which producing this email sending error with Chinese Sender Name.
While you are testing this scenario at magento 2.4

Could you please check this scenario in version 2.3.5-p2. And what will be the solution for this.

Thank you!

[betooliveirame]

@magento give me 2.3.5-p2 instance

[magento-deployment-service]

Hi @betooliveirame. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @betooliveirame, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[arslan-eg]

@magento give me 2.3.5-p2 instance

[magento-deployment-service]

Hi @arslan-eg. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @arslan-eg, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[tuyennn]

@magento give me 2.3.5-p2 instance

[magento-deployment-service]

Hi @tuyennn. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @tuyennn, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[tuyennn]

Seem this is duplicate of #24902

[engcom-Alfa]

@magento give me 2.3.5-p2 instance

[magento-deployment-service]

Hi @engcom-Alfa. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Alfa, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[engcom-Alfa]

Hi @arslan-eg

Unfortunately, we are not able to reproduce this issue on 2.3.5-p2, 2.4.1 and 2.4-develop.
Everything works as expected.

Actual Result: ✔️ An email is sent to the user when he has changed his password.

It seems that the issue was solved by changes from PR #24906.
So, we have to close it.

Please feel free to comment, reopen or create new ticket according to the Issue reporting guidelines
if you are still facing this issue on the latest 2.4-develop branch.
Thank you for collaboration.