npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

email-deep-validator

v3.3.0

Published

Verify email address checking MX records, and SMTP connection.

Downloads

9,373

Readme

email-deep-validator

Build Status

Verify email address checking MX records, and SMTP connection.

Installation

Install the module through NPM:

$ npm install email-deep-validator --save

Requires Node 7.6 or above

Examples

Include the module, create a new EmailValidator object and call verify method:

const EmailValidator = require('email-deep-validator');

const emailValidator = new EmailValidator();
const { wellFormed, validDomain, validMailbox } = await emailValidator.verify('[email protected]');
// wellFormed: true
// validDomain: true
// validMailbox: true

When a domain does not exist or has no MX records, the domain validation will fail, and the mailbox validation will return null because it could not be performed:

const { wellFormed, validDomain, validMailbox } = await emailValidator.verify('[email protected]');
// wellFormed: true
// validDomain: false
// validMailbox: null

A valid Yahoo domain will still return validMailbox true because their SMTP servers do not allow verifying if a mailbox exists.

Configuration options

timeout

Set a timeout in seconds for the smtp connection. Default: 10000.

verifyDomain

Enable or disable domain checking. This is done in two steps:

  1. Verify that the domain does indeed exist;
  2. Verify that the domain has valid MX records.

Default: true.

verifyMailbox

Enable or disable mailbox checking. Only a few SMTP servers allow this, and even then whether it works depends on your IP's reputation with those servers. This library performs a best effort validation:

  • It returns null for Yahoo addresses, for failed connections, for unknown SMTP errors.
  • It returns true for valid SMTP responses.
  • It returns false for SMTP errors specific to the address's formatting or mailbox existance.

Default: true.

Testing

$ npm test

Changelog

2.0.0

  • (BREAKING) Requires node 7.6 for async/await.
  • (BREAKING) Instead of throwing on any invalidation, the lib now returns an object with which validations failed.
  • (BREAKING) Configuration property verifyMxRecords renamed to verifyDomain.
  • (BREAKING) Configuration property verifySmtpConnection renamed to verifyMailbox.

Contributing

This module was originally written to be used with Conversio and is used in a production environment currently. This will ensure that this module is well maintained, bug free and as up to date as possible.

Conversio's developers will continue to make updates as often as required to have a consistently bug free platform, but we are happy to review any feature requests or issues and are accepting constructive pull requests.