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

@mulmobridge/email

v0.1.1

Published

Email bridge for MulmoBridge — checks an IMAP mailbox and replies via SMTP

Readme

@mulmobridge/email

Experimental — please test and report issues.

Email bridge for MulmoClaude. Polls an IMAP mailbox for unread mail and replies via SMTP preserving threading (In-Reply-To + References). Outbound-only — no public URL needed.

Good for async / slow workflows where you don't need instant replies: delegate tasks by email, get structured results back in your inbox.

Setup

1. Get a mailbox

Any IMAP+SMTP-capable mailbox works. A dedicated mailbox is strongly recommended — the bridge marks messages as \Seen after processing.

  • Gmail — create an app password (requires 2FA). Use imap.gmail.com:993 / smtp.gmail.com:465 (TLS) or 587 (STARTTLS).
  • Fastmail / iCloud / Outlook — similarly, prefer app passwords.
  • Self-hosted (Postfix + Dovecot, mailcow, Stalwart) — use your regular credentials.

2. Run the bridge

EMAIL_IMAP_HOST=imap.gmail.com \
[email protected] \
EMAIL_IMAP_PASSWORD=your-app-password \
EMAIL_SMTP_HOST=smtp.gmail.com \
[email protected] \
EMAIL_SMTP_PASSWORD=your-app-password \
[email protected] \
npx @mulmobridge/email

Send an email to the bot address — you'll get a reply threaded under your original message.

Environment variables

| Variable | Required | Default | Description | |----------------------------|----------|---------|-------------| | EMAIL_IMAP_HOST | yes | — | IMAP server hostname | | EMAIL_IMAP_USER | yes | — | IMAP username | | EMAIL_IMAP_PASSWORD | yes | — | IMAP password (use an app password for Gmail / Fastmail) | | EMAIL_IMAP_PORT | no | 993 | IMAP port | | EMAIL_IMAP_TLS | no | true | Use implicit TLS (false for plain + STARTTLS) | | EMAIL_SMTP_HOST | yes | — | SMTP server hostname | | EMAIL_SMTP_USER | yes | — | SMTP username | | EMAIL_SMTP_PASSWORD | yes | — | SMTP password | | EMAIL_SMTP_PORT | no | 587 | SMTP port | | EMAIL_SMTP_TLS | no | auto | true for implicit TLS (465), false for STARTTLS (587). Auto-detected from port if unset | | EMAIL_FROM | yes | — | Bot's email address (usually equal to EMAIL_SMTP_USER) | | EMAIL_ALLOWED_SENDERS | no | (all) | CSV of allowed sender addresses (case-insensitive) | | EMAIL_POLL_INTERVAL_SEC | no | 30 | Poll interval in seconds (min 10) | | MULMOCLAUDE_AUTH_TOKEN | no | auto | MulmoClaude bearer token override | | MULMOCLAUDE_API_URL | no | http://localhost:3001 | MulmoClaude server URL |

How it works

  1. At startup, the bridge logs into IMAP via imapflow and enters a poll loop on INBOX.
  2. Every EMAIL_POLL_INTERVAL_SEC, SEARCH UNSEEN returns new messages. Each is fetched, parsed with mailparser, and (after allowlist check) forwarded to MulmoClaude keyed by the sender's address.
  3. The reply goes out via nodemailer with In-Reply-To = original Message-ID and References = full thread chain, so mail clients render it as a proper thread reply.
  4. Processed messages are flagged \Seen so they aren't re-processed on restart.

Troubleshooting

| Symptom | Cause | Fix | |---|---|---| | NO Invalid credentials | Using raw password on Gmail / Fastmail | Create an app password with IMAP + SMTP scopes | | Replies end up in recipient's Spam | Lack of SPF / DKIM on the bot domain | Send from a provider that already signs (Gmail, Fastmail, etc.) or set up DKIM on your own server | | Reply not threaded in the sender's client | Client ignored References | Some corporate clients strip threading headers — not fixable bridge-side | | Mail loop (bridge replies to its own replies) | The bridge's own From address is in EMAIL_ALLOWED_SENDERS | Remove it, or use a separate address for the bot |

Security notes

  • Use a dedicated bot mailbox. Revocation of the app password then won't affect your personal mail.
  • The IMAP password is read-write — the bridge can delete mail if compromised. Store it via a secret manager, not plain env.
  • Allowlist via EMAIL_ALLOWED_SENDERS is strongly recommended. Without it, anyone who emails the bot can converse with your MulmoClaude, and spam is a real risk.
  • Replies include the bot's response text in plain email. Don't bridge sensitive content unless both mailboxes are under your control.
  • Attachments are not processed in v0.1.0 — image / PDF forwarding may land in a follow-up.

Ecosystem

Part of the @mulmobridge/* package family.

Shared libraries:

Bridges (one npm package per platform):