Issue when updating customer email in Admin Panel with ö and .swiss domain

magento / magento2

Prior to making any Submission(s), you must sign an Adobe Contributor License Agreement, available here at: https://opensource.adobe.com/cla.html. All Submissions you make to Adobe Inc. and its affiliates, assigns and subsidiaries (collectively “Adobe”) are subject to the terms of the Adobe Contributor License Agreement.

Open Software License 3.0

11.57k stars 9.32k forks source link

Preconditions and environment

Magento versions tested:

2.4.5-p10
2.4.6-p7
2.4.7

Steps to reproduce

Go to the Admin Panel.
Navigate to Customers > All Customers and select a customer.
In the Account Information section, try to update the email address to something like max@möstermann.swiss.
Save the changes.

Expected result

Email address and customer saved successfully

Actual result

After attempting to save the email, the following error message is displayed at the top of the page:

"Email" is not a valid hostname.
'xn--mstermann-07a.swiss' looks like a DNS hostname but we cannot match it against the hostname schema for TLD 'swiss'.
'xn--mstermann-07a.swiss' looks like a local network name, which is not an acceptable format.

Additional information

Observations:

When I enter an email like max@möstermann.com, it works fine.
When I enter max@möstermann.swiss with the ö, the email is converted to its Punycode equivalent (xn--mstermann-07a.swiss), and the error is triggered.
I tried .swiss by itself without the special character ö (e.g., `max@mail.swiss) and it works fine.

It seems like the combination of the ö character and .swiss is causing the issue. The email address gets converted to Punycode, but it seems Magento or the underlying validation logic doesn't handle this combination correctly.

Release note

No response

Triage and priority

[X] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
[X] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
[ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
[ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
[X] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

To learn more about issue processing workflow, refer to the Code Contributions.

Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

Hi @engcom-Delta. 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: :point_down:

[ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
[ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.4-develop branch
Details
- 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.

magento / magento2