-
Notifications
You must be signed in to change notification settings - Fork 5.3k
MailAddress accepts invalid email address with consecutive dots #109690
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
Conversation
ManickaP
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks. Please also change the comment above the class:
runtime/src/libraries/System.Net.Mail/src/System/Net/Mail/DotAtomReader.cs
Lines 14 to 15 in 35d2780
| // or end, but we do allow dots at the end for compatibility with other mail clients. We also allow | |
| // multiple consecutive dots, which would normally be invalid. |
And we need to change the docs as well as they explicitly mention allowing double dots:
https://learn.microsoft.com/dotnet/api/system.net.mail.mailaddress#remarks
…et#109690) * MailAddress accepts invalid email address with consecutive dots * update DotAtomReader class comment
|
@ericstj Does this need to be documented as a breaking change? See dotnet/docs#50592. |
|
Yeah it should be. Today, reviewers self-identify, maybe we can get copilot to help in the future |
📋 Breaking Change Documentation RequiredCreate a breaking change issue with AI-generated content Generated by Breaking Change Documentation Tool - 2026-01-10 00:23:17 |
|
@ManickaP -- did you want to create the doc using the link above? |
|
Is this a braking change? I would not consider it as such. It's just making the implementation follow RFC more closely. But correct me if I'm wrong. |
The new code behaves differently from previously documented behavior (is more restrictive). I think that counts as a breaking change (regardless how bad the previous behavior was) |
Fixes #109590