Bug #73616
closed
Different standards used in GeneralUtility::validEmail (RFC 3696) and swiftmailers Swift_Mime_Grammar-class (RFC 2822)
0%
Description
Tested in 6.2.18, but may also occur in current versions.
At the moment GeneralUtility::validEmail() is following RFC3696, where as the internally used swiftmailer is follwing RFC 2822.
We had a case where an email with the format "user@¹gmx.at" was checked as valid by TYPO3s internal function but lead to an Swift_RfcComplianceException when sending an email.
The problem may or may not occur because of the different standards that were used. Currently this would mean, that as a TYPO3 developer you would always have to check against the \Swift_Mime_Grammar instead of GeneralUtility::validEmail() to be on the safe side, if the email at some time should be sent by TYPO3s internal methods.
Updated by Mathias Brodala over 7 years ago
- Related to Bug #81524: Cannot send mails with special characters in local part added
Updated by Georg Ringer almost 6 years ago
- Related to Bug #87077: Scheduler: Notification email address (e.g. system report) does not allow a local mail address added
Updated by Georg Ringer almost 6 years ago
- Related to Feature #87691: Allow email adresses with "+" in GeneralUtility::validEmail() added
Updated by Riccardo De Contardi about 5 years ago
should this be tested on version 10 where Swiftmailer has been removed (https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/10.0/Breaking-88643-RemovedSwiftmailerswiftmailerDependency.html)?
Updated by Georg Ringer almost 5 years ago
- Related to Feature #90370: Use Egulias\EmailValidator for email validation added