Opened 2 years ago
Last modified 11 days ago
#17491 reopened defect (bug)
Make is_email() compliant with RFC2822 — at Version 13
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Future Release |
| Component: | General | Version: | 3.1.2 |
| Severity: | minor | Keywords: | has-patch dev-feedback |
| Cc: |
Description (last modified by kawauso)
is_email('toto.@…') returns true
Change History (15)
comment:2
scribu
— 2 years ago
- Keywords needs-patch added; dev-feedback removed
- Milestone changed from Awaiting Review to Future Release
- Severity changed from critical to minor
- Summary changed from is_email('toto.@toto.com') returns true !!!! to is_email('toto.@toto.com') returns true
Let's not get carried away.
comment:3
sivel
— 2 years ago
- Keywords has-patch added; needs-patch removed
Patch adds in the rest of the regex from http://www.regular-expressions.info/email.html for the local part.
comment:6
arena
— 18 months ago
- Keywords dev-feedback added
Here is a new fix (#17491.patch) with code from the class swiftmailer
to comply with RFC2822
comment:7
follow-up:
↓ 8
arena
— 18 months ago
- Resolution set to duplicate
- Status changed from new to closed
duplicate with #19759
comment:9
in reply to:
↑ 8
helenyhou
— 18 months ago
- Resolution duplicate deleted
- Status changed from closed to reopened
Replying to kawauso:
Are we closing an existing ticket with feedback and milestone in favour of a new one with a similar patch and issue or am I missing something?
I think arena may be trying to bump the ticket. Closing #19759 as duplicate - patch is exactly the same as #17491.patch.
comment:10
arena
— 18 months ago
my purpose was not to bump but to clarify the situation with a more specific title : making is_email() compliant with rfc2822.
comment:11
helenyhou
— 18 months ago
- Summary changed from is_email('toto.@toto.com') returns true to Make is_email() compliant with RFC2822
comment:12
arena
— 17 months ago
- Summary changed from Make is_email() compliant with RFC2822 to Make is_email() compliant with RFC2822 !
comment:13
kawauso
— 17 months ago
- Description modified (diff)
- Summary changed from Make is_email() compliant with RFC2822 ! to Make is_email() compliant with RFC2822
No need, really. Especially for those of us with email threads.
toto.@… does not comply with RFC 2822