Describe the bug 🐛
Please provide option to validate email by RFC5322

https://dart.dev/null-safety/migration-guide

thanks you guys for this awesome plugin

Hi,

The validate function return TRUE for an address like “user@👕.com” but an emoji email isn't a valid email

Thanks

The version number listed in the README is for V1.0.6. Using this version results in the following when trying to run an application:
Error: Cannot run with sound null safety, because the following dependencies

Hey 👋 Thanks for your library!

I wanted to check if you would consider including a way, to provide the reason the validation fails?
Maybe by returning enum values or something.

I guess many use the library to validate an email input, but then can only add an error message like "Please enter a valid email address", while most users don't really get why the entered address isn't working. Especially if they added an accidental whitespace at the end.

We are currently adding some additional validations for certain cases like whitespaces, but this also means we start to duplicate logic from your library, which doesn't feel right.

Looking forward to hear your thoughts on this.
Cheers

Describe the bug 🐛
EmailValidator.validate("ö@gmail.com") returns true

To Reproduce
Steps to reproduce the behavior:

1. Use any non latin in the address, like ö, 🙂, ß
2. Call EmailValidator.validate(email)

Expected behavior
Regarding to Wikipedia (https://en.wikipedia.org/wiki/Email_address#Local-part) non Latin characters shouldn't be allowed.

Email validator not working if we add emoji after "."

For Example : ******@gmail.❤️️ -> This is not a valid email but email validator validates it.

See https://pub.dev/packages/email_validator/score. Would be nice to have 130/130.

If someone has time I would appreciate it! Nice way to contribute to the project or open source as a first timer 👍

[email protected] returns valid for whatever reason.

Isn't there a downloadable list from arin.net you can toss in an array?

First of all, thanks for creating such a wonderful package. I'm not sure if it's really an issue or not, and I just want to help this package get better. When testing the package with emails like [email protected] or [email protected], everything is fine. However, when giving the package inputs like:

ایمیل@جیمیل.کام

it returns true. In my case, I don't want to accept such emails in my program. I'm not sure if there is any email address like this or not, but I have never seen one. The above inputs are written in the Persian language, and the package only checks the pattern of an email and doesn't check the language of characters.

Input : a#[email protected]

Current Result : Valid Email Format

Expected Result : Invalid

Hey 👋

I've noticed that the GitHub and pub.dev readmes still mention the old version (1.0.5). Not a big deal, yet, if you'll have a minute 🙂

This is a low hanging fruit for anyone wanting to contribute

Currently the library only has 20/30 points in the Pass static analysis section on pub.dev. See https://pub.dev/packages/email_validator/score.

Describe the bug 🐛
email@example is reported as a valid email, when it is infact invalid.

To Reproduce
EmailValidator.validate("email@example", true, false);

Expected behavior
return value should be false

its allowing [email protected] .
please dont allow if there's only special characters before @ symbol.

Description
Hi developer team, we were using email_validator package with version 2.0.1, and it was fine with the codebase. However, recently found out that updating version 2.1.2-2.1.16 will break the code with the error messages shown below:

Environments
OS: MacOs Monterey v12.3 x64
Language: Dart SDK version: 2.17.6 (stable)
email_validator version: 2.1.2 or later

Hello, I have an email address of the format xsdffgbh###@gmail.com (letters followed by three numbers) that is being rejected by the package. Can anyone assist me with this?

Please provide an option to validate email by RFC822

name@slp_holding.com this email is failed

Before adding null check

When using the TextFormField's validator parameter, passing the value to EmailValidator.validate() warns that I need to Add a null check (!). Screenshot showing the warning with suggested fix.

After adding null check (plus print statement)

However, if I add the null check bang, and try to print the result of EmailValidator.validate(value!), I get a different warning:

Warning: Operand of null-aware operation '!' has type 'String' which excludes null.

Question

Is this warning something that should be fixed in this email-validator package? The Stack Overflow posts I've read for this warning from other packages indicated that a fix was necessary in the package's code. E.g. https://stackoverflow.com/questions/67389956/why-im-getting-this-error-warning-operand-of-null-aware-operation-has-type

given a email that is like [email protected] is this a valid or invalid email ?

Describe the bug 🐛

admin@mailserver1 (local domain name with no TLD, although ICANN highly discourages dotless email addresses)

It's time to get rid of nullsafety suffix)

https://medium.com/dartlang/preparing-the-dart-and-flutter-ecosystem-for-null-safety-e550ce72c010

Should be a low hanging fruit for anyone interested in contributing to the repository 😄

Hi,

The validate function return TRUE for an address like "[email protected]" but a 1 letter TLD isn't a valid TLD

Thanks

email_validator: '^1.0.6'1

Error: Cannot run with sound null safety, because the following dependencies
don't support null safety:

 - package:email_validator

For solutions, see https://dart.dev/go/unsound-null-safety
Unhandled exception:
Bad state: Unsupported Null Safety mode NonNullableByDefaultCompiledMode.Invalid, in null.
#0      ProgramCompiler.emitModule (package:dev_compiler/src/kernel/compiler.dart:472:9)
#1      JavaScriptBundler.compile (package:frontend_server/src/javascript_bundle.dart:152:33)
#2      FrontendCompiler.writeJavascriptBundle (package:frontend_server/frontend_server.dart:665:47)
<asynchronous suspension>
#3      FrontendCompiler.compile (package:frontend_server/frontend_server.dart:573:9)
<asynchronous suspension>
#4      listenAndCompile.<anonymous closure> (package:frontend_server/frontend_server.dart:1154:11)
<asynchronous suspension>
Finished with error: the Dart compiler exited unexpectedly.
Failed to compile application.

{
"resource": "/C:/Flutter Project/newproject/awesome-flutter/email-validator.dart/test/email_validator_test.dart",
"owner": "dart",
"code": {
"value": "undefined_function",
"target": {
"$mid": 1,
"external": "https://dart.dev/tools/diagnostic-messages#undefined_function",
"path": "/tools/diagnostic-messages",
"scheme": "https",
"authority": "dart.dev",
"fragment": "undefined_function"
}
},
"severity": 8,
"message": "The function 'equals' isn't defined.\nTry importing the library that defines 'equals', correcting the name to the name of an existing function, or defining a function named 'equals'.",
"source": "dart",
"startLineNumber": 135,
"startColumn": 59,
"endLineNumber": 135,
"endColumn": 65,
"tags": []
}

I'm using your dependency for validating email address in my flutter project and for values like '[email protected]' or '[email protected]' validate function is returning 'true' like it's valid value and it should return false.

Describe the bug 🐛
If a pass in 'kkkk@' is returns with confirming to be a valid email which I don't believe.

To Reproduce
Steps to reproduce the behavior:

Expected behavior
If I use https://isemail.info for instance, it says: "The general result is: Address is invalid for any purpose. The specific diagnosis is: Address has no domain part."

Additional context
Add any other context about the problem here.

Describe the bug 🐛
Email addresses with a hyphen in the domain are marked as not valid but they are.

To Reproduce
Test the email address: [email protected]

Expected behavior
Should be correct.

Additional context
Validator returns false.