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

@alimzen/relayo-bounces

v0.1.0

Published

Turns bounce reports (DSN, RFC 3464) and spam complaints (ARF, RFC 5965) received by email into Relayo events.

Readme

@alimzen/relayo-bounces

Reads the emails that come back to your bounce address and turns them into Relayo events:

  • Delivery status notifications (DSN, RFC 3464) from Postfix, Exim, Gmail, Microsoft 365 and any standards-compliant server: failures become bounced, delays deferred, success reports delivered.
  • Spam complaints from feedback loops (ARF, RFC 5965) become complained.
  • Non-standard bounces that list X-Failed-Recipients are understood too.
  • Out-of-office and other auto-replies are recognized and ignored.

This is what gives you bounce events when you send through your own mail server with @alimzen/relayo-smtp: SMTP has no webhooks, so bounces arrive as email. No runtime dependencies.

npm install @alimzen/relayo @alimzen/relayo-bounces

Usage

import { parseBounceEmail } from '@alimzen/relayo-bounces';

// rawEmail: the full message as received (string or bytes), e.g. from IMAP, an inbound-email
// webhook (SES, Mailgun, Postmark...) or a file.
const { kind, events } = parseBounceEmail(rawEmail);

for (const event of events) await relayo.emit(event); // your relayo.on(...) handlers run as usual

kind tells you what the email was: dsn, arf, non-standard, auto-reply or unrecognized. Only the first three produce events. Leave unrecognized mail for a human, or delete it.

Events have the same shape as provider webhooks: bounced events carry bounceType (hard, soft, block), reason, smtpCode, enhancedCode and diagnostic, classified the same way as every other driver's. Event ids are derived from the report, so reading the same mailbox twice gives the same ids.

Pass { provider: 'mailserver' } if your SMTP driver uses a name other than "smtp".

Matching reports to your sends

Most reports quote the original message's headers. @alimzen/relayo-smtp sends X-Relayo-Message-ID, X-Relayo-Metadata and Message-ID: <relayo-id@your-domain>, so events come back with your messageId and metadata. If a report only quotes the Message-ID, the id is recovered from it. Some feedback loops redact the recipient: those complaints have recipient: '', but still the messageId.

To read the mailbox automatically, use @alimzen/relayo-imap.

Where bounces go

Receiving servers send reports to the envelope sender (the Return-Path), which is your from address unless you change it. To collect them in a dedicated mailbox:

smtp(transport, { bounceAddress: '[email protected]' });