Feature #56771
closedAdditional check for valid domain in validEmail()
100%
Description
If using a correct email address (= correct syntax),
but the domain name has no valid DNS entry,
then a given email is validated as valid,
but the destination is still wrong. In some cases
the email should be completely validated.
By adding an additional PHP call to check if
the DNS entry is valid, the validEmail() can
be put in a stricter mode if called explicitly.
Updated by Gerrit Code Review over 10 years ago
- Status changed from Accepted to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/28264
Updated by Gerrit Code Review almost 10 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/28264
Updated by Gerrit Code Review almost 10 years ago
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/28264
Updated by Gerrit Code Review almost 10 years ago
Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/28264
Updated by Benni Mack almost 10 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 5033a33d7b7ed13f6672db6846ad097b8120315b.
Updated by Steffen Müller almost 10 years ago
Updated by Steffen Müller almost 10 years ago
- Status changed from Resolved to Accepted
- Target version changed from 6.2.0 to 7.1 (Cleanup)
- TYPO3 Version changed from 6.2 to 7
Updated by Steffen Müller almost 10 years ago
- Tracker changed from Bug to Feature
Updated by Steffen Müller almost 10 years ago
How to proceed with this ticket? I doubt we need this feature in the core, since it can be achieved with a basic php function.
Updated by Benni Mack almost 10 years ago
- Status changed from Accepted to Rejected
We leave it for now (rejected), and the customer should implement it on his own. :(