The country / region of mail sent from the admin panel is translated into the admin locale.

[Taku-Yamashita]

Preconditions (*)

1. Magento2.3.3
2. PHP7.2
3. Two stores (JP & EN)
4. Admin user locale is ja_JP

Steps to reproduce (*)

1. place order in EN store.
2. send order Email from admin panel using admin user locale ja_JP.

Expected result (*)

Displayed in English.

Actual result (*)

Country is Displayed in Japanese (admin user locale) even though this order is placed on EN store.

if I change admin panel locale to en_US from ja_JP , it will work fine.

When sending mail from admin panel, Magento\Backend\Model\Locale\Resolver::setLocale method is used. And it force to set admin user local to county & region .

[m2-assistant]

Hi @Taku-Yamashita. 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.

@Taku-Yamashita do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

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

[m2-assistant]

Hi @shikhamis11. 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.

[Taku-Yamashita]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @Taku-Yamashita. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @Taku-Yamashita, here is your Magento instance.
Admin access: https://i-26521-2-4-develop.instances.magento-community.engineering/admin_e831
Login: 9c9f1517 Password: 2e8c375a74bc
Instance will be terminated in up to 3 hours.

[m2-assistant]

Hi @shikhamis11. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

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

• 2. 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!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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

[magento-engcom-team]

✅ Confirmed by @shikhamis11
Thank you for verifying the issue. Based on the provided information internal tickets MC-30798 were created

Issue Available: @shikhamis11, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[ilnytskyi]

The country is not translated in async mailing mode too.
e.g. enable async sending; use a few stores with different locales; see that translation falls to default store locale

[shikhamis11]

I am working on this issue at #MM20IN

[m2-assistant]

Hi @engcom-Charlie. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
• 2. 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!
• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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

[gabrieldagama]

Hi @Taku-Yamashita. Thank you for your report.
The issue has been fixed in #31875 by @engcom-Charlie in 2.4-develop branch
Related commit(s):

• c0d11778a646ed160aed39f95ba8fff908f803be
• e971004d32752f53fc7733bf724a4ffe5e601176

The fix will be available with the upcoming 2.4.3 release.