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 🙏

© 2026 – Pkg Stats / Ryan Hefner

haraka-plugin-mail_from.is_resolvable

v1.3.0

Published

Haraka plugin that checks that the domain used in MAIL FROM is resolvable to an MX record

Downloads

46,147

Readme

CI Test Status Code Climate

haraka-plugin-mail_from.is_resolvable

This plugin checks that the domain used in MAIL FROM is reachable via DNS. A domain passes when:

  1. It publishes an MX record that resolves to at least one non-bogus IP (IPv4 or IPv6), or
  2. It has no MX record but has an A/AAAA record (RFC 5321 §5.1 implicit MX fallback), and that address is non-bogus.

"Non-bogus" means the address does not match the configured re_bogus_ip (IPv4) or net_utils.ipv6_bogus (IPv6). A domain whose MX targets resolve only to bogus addresses is treated the same as a domain with no MX (controlled by [reject].no_mx).

The Null MX record (RFC 7505: priority 0, exchange "") is recognized and always denied — those domains explicitly do not send mail.

Configuration

This plugin uses the INI-style file format and accepts the following options:

  • [main] allow_mx_ip=[true | false]

    Allow MX records that return IP addresses instead of hostnames. This is not allowed as per the RFC, but some MTAs allow it.

  • [main] re_bogus_ip=<regex>

    IPv4 regex matching addresses considered unusable. Default: ^(?:0\.0\.0\.0|255\.255\.255\.255|127\.). An MX target whose A record matches is treated as unreachable.

  • [main] timeout_ms=<integer>

    Maximum time (ms) to wait on each DNS call (MX lookup and MX-host resolution). A timeout returns DENYSOFT so the sender retries. Default 5000. Node's resolver has its own per-query timeouts; this is a soft cap on cumulative retries that would otherwise stall an SMTP transaction.

  • [reject] no_mx=[deny|defer|no]

    Applies when the domain has no MX, no usable A/AAAA fallback, or all of its MX targets resolve only to bogus IPs. "deny" returns DENY and rejects the command. "defer" returns a DENYSOFT (TEMPFAIL) and the client will retry later. "no" allows the transaction to continue to the next plugin.