Not anymore with all the custom domain names.

Can we reconsider this?

Even with the profusion of new TLDs it is still impossible to have an email address of the form name@oneword; technically an email address like user@localhost is valid but that seems like an edge case that would never arise in a real-world site, while somebody omitting the ".com" from their email address is a relatively common error.

Suggest a regex that requires at least one character on either side of at least one period after the @ would resolve this without requiring an exhaustive list of TLDs.

@skeggse?

@hueniverse sorry for the delay.

isemail does intentionally validate shouldbe@invalid as valid.

I guess I could add a domains option that specifies how many domains should be present for the address to be considered valid.

What's considered valid? Would be useful to have a flag that we can use to meet expectations.

The intended use is to validate the domain using the checkDNS option. That option makes isemail asynchronous, so it might not work so well with joi.

I would really prefer not to include a hardcoded list of valid top-level domains to validate against, but I don't really see any other way. That shouldn't be a difficult change to make, but feel free to submit a pull request.

@skeggse would you rather I checked for tld outside of isemail?

@seldo: worth mentioning that the email address human@io is valid--.io has an MX record and supports email addresses directly.

@hueniverse I added a tldWhitelist option and a minDomainAtoms option (naming flexible) in globesherpa/node-isemail#3.

This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.