Skip to content

Unhandled checks on email validator #108

Closed

Description

@devikasondhi

Hello,

I've come across a few checks that the current email validator does not take into account. Sharing them below.

  1. Local part of the email address should be less than 64 bytes. However, the validator returns True for john56789.john56789.john56789.john56789.john56789.john56789.john5@example.com

  2. The name <email_id> format isn't supported, even though it is valid as per RFC 2822 (https://tools.ietf.org/html/rfc2822#page15). Example: Abigail <abigail@example.com> is unexpectedly returned as invalid

  3. Multiple @ in the email aren't handled. Example of a valid email: Abigail<@a,@b,@c:abigail@example.com>

Thanks.

Activity

  1. kvesteri commented on Dec 27, 2018

    @kvesteri
    Collaborator

    PRs welcome.

  2. micahcochran commented on Jan 25, 2019

    @micahcochran

    #22 has a few other examples in which the email validator could use some improvement.

  3. ShivaShankerReddy commented on Dec 12, 2019

    @ShivaShankerReddy

    @devikasondhi i will say everything is vaid other than 2. I don't think we should email along with name?

  4. added
    outdatedIssue/PR: Open for more than 3 months
    maintenancePR: Alters existing source code
    and removed
    enhancementIssue/PR: A new feature
    on Mar 11, 2023
  5. nandgator commented on Mar 11, 2023

    @nandgator
    Collaborator

    RFC 2822 is obsoleted by RFC 5322

  6. added a commit that references this issue on Mar 12, 2023
    660cf55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    maintenancePR: Alters existing source codeoutdatedIssue/PR: Open for more than 3 months

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions