Open
Description
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., `[email protected]) 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
- Severity: S0 - Affects critical data or functionality and leaves users without workaround.
- 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.
- Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
Metadata
Metadata
Assignees
Labels
Gate 3 Passed. Manual verification of the issue completed. Issue is confirmedOnce P0 defects have been fixed, a defect having this priority is the next candidate for fixing.Indicates original Magento version for the Issue report.Indicates original Magento version for the Issue report.Indicates original Magento version for the Issue report.The issue has been reproduced on latest 2.4-develop branch
Activity