Skip to content
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

[BUG]: Email validation does not allow UTF8SMTP #16637

Closed
noone-silent opened this issue Aug 18, 2024 · 1 comment
Closed

[BUG]: Email validation does not allow UTF8SMTP #16637

noone-silent opened this issue Aug 18, 2024 · 1 comment
Labels
5.0 The issues we want to solve in the 5.0 release bug A bug report status: medium Medium

Comments

@noone-silent
Copy link
Contributor

noone-silent commented Aug 18, 2024

Describe the bug
With the UTF8SMTP Extension, it is possible to allow any utf-8 character in the local part. Also domain names can have umlauts, but needs different parsing. RFC: https://www.rfc-editor.org/rfc/rfc5336#section-3.2

To Reproduce
Use any email, like [email protected]

Steps to reproduce the behavior:

            $validation = new Validation();
            $validation->add('email', new Validation\Validator\Email());
            var_dump($validation->validate(['email' => '[email protected]']));

Expected behavior
Add a flag/option to allow UTF8SMTP email addresses.

When this filter is set, pass FILTER_FLAG_EMAIL_UNICODE to the filter_var function.

Details

  • Phalcon version: v5.8.0
  • PHP Version: 8.2.20
  • Operating System: debian
  • Installation type: Compiling from source
  • Zephir version (if any): -
  • Server: Nginx
  • Other related info (Database, table schema): MariaDB
@noone-silent noone-silent added bug A bug report status: unverified Unverified labels Aug 18, 2024
noone-silent added a commit to noone-silent/cphalcon that referenced this issue Aug 19, 2024
niden added a commit that referenced this issue Aug 19, 2024
…n-local-part

[#16637] - refactor: allow utf8 in email local part.
@niden niden added status: medium Medium 5.0 The issues we want to solve in the 5.0 release and removed status: unverified Unverified labels Aug 19, 2024
@niden niden added this to Phalcon v5 Aug 19, 2024
@niden niden moved this to Implemented in Phalcon v5 Aug 19, 2024
@niden
Copy link
Member

niden commented Aug 19, 2024

Resolved in #16638

Thank you @noone-silent

@niden niden closed this as completed Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5.0 The issues we want to solve in the 5.0 release bug A bug report status: medium Medium
Projects
Status: Implemented
Development

No branches or pull requests

2 participants