Legacy package names under
@masonjames/*are deprecated. Install the unscoped packages below.
Use this path when you control the codebase and want full provider parity.
pnpm add emdash-smtpimport { defineConfig } from "astro/config";
import emdash from "emdash/astro";
import { emdashSmtp } from "emdash-smtp";
export default defineConfig({
integrations: [
emdash({
plugins: [emdashSmtp()],
}),
],
});Use this path when you are developing against a sandbox-compatible environment and want the marketplace-safe descriptor from code.
pnpm add emdash-smtp-marketplaceimport { defineConfig } from "astro/config";
import emdash from "emdash/astro";
import { emdashSmtpMarketplace } from "emdash-smtp-marketplace";
export default defineConfig({
integrations: [
emdash({
sandboxRunner: "@emdash-cms/cloudflare/sandbox",
sandboxed: [emdashSmtpMarketplace()],
}),
],
});- Configure marketplace access and sandbox support for your EmDash deployment.
- From this repo, publish the marketplace package for the
emdash-smtpplugin withpnpm publish:marketplace. - Install EmDash SMTP from Plugins → Marketplace in EmDash.
- Open the plugin’s Providers page and configure the active provider.
- Resend: configure an API key and a verified sender domain, then set Resend as the primary provider.
- Google / Gmail: configure either a direct access token or a
clientId+clientSecret+refreshTokencredential set. The plugin refreshes Google access tokens during delivery when refresh credentials are present. - Microsoft / Outlook and Zoho Mail follow the same credential model as Google for long-lived OAuth-backed operation.
- Choose
emdash-smtpif you need Generic SMTP or local sendmail. - Choose
emdash-smtp-marketplaceif you need an EmDash marketplace install path or sandbox-safe code install. - Do not install
emdash-smtp-coreoremdash-smtp-node-transportsdirectly; they are implementation packages. - Both variants use the same EmDash plugin ID:
emdash-smtp. - Do not install both variants at the same time on the same site.