Guides
GuideSend From Your Own Address

Send email from your own address

Connect a mailbox you already own and your site sends from your address instead of ours. Set it up once under Email accounts.

What we send, and what you send

Your site’s system email is written and sent by us, so it goes out from our sending address by default and is included in your plan:

  • “Verify your email” when someone signs up
  • “Reset your password”
  • Receipts for purchases made on your site

Anything you write yourself — a newsletter, an announcement, a promotion, a campaign to your members — sends from your own mailbox. That is the only route for it, on every plan.

Why it works this way. Our sending address is shared by every site on the platform. If one person uses it to send something a lot of people mark as spam, Gmail and Outlook start distrusting that address — and then everyone’s password-reset emails start landing in spam.

Sending your own mail from your own address means your reputation is yours: yours to build, and nobody else’s to damage.

Connecting your mailbox

Go to Email accounts and choose Add sending account. You can use a mailbox you already have — Gmail, Outlook, or any address that came with your domain or hosting.

  1. From address — the address people will see, e.g. hello@yourdomain.com.
  2. From name — what appears as the sender, e.g. your business name.
  3. Server details — your provider’s outgoing (SMTP) server, port, username and password. Your email provider publishes these; search their help for “SMTP settings”.
  4. Use an app password, not your normal one. Gmail and Outlook both require this. In your email account’s security settings, create an app password and paste that here — it only works for sending mail and you can revoke it any time without changing your real password.
  5. Send a test before saving. If it fails, the error tells you which detail is wrong.

Using it

Once a mailbox is connected, Campaigns and Journeys will offer it as the sender — pick it and send as normal. In function code, use ctx.email.sendVia():

const accounts = await ctx.email.accounts();

await ctx.email.sendVia(accounts[0].id, {
  to: 'member@example.com',
  subject: 'This month at Acme',
  html: '<p>Here is what is new…</p>',
  unsubscribeUrl: 'https://yourdomain.com/unsubscribe?u=123',
});

See Backend Functions → ctx.email for the full reference.

Optional: system email from your address too

Once a mailbox is connected you can also point your site’s signup, password-reset and receipt emails at it, so everything your site sends comes from your own domain. That is a choice, not a requirement — leave it and we keep sending those for you.

Getting into the inbox

If you are sending to more than a handful of people, set these up on your domain once. Your domain provider’s help pages have step-by-step instructions, and your email provider gives you the values to paste in.

  • SPF and DKIM — these prove the mail really came from you. Without them, a lot of it goes to spam.
  • DMARC — tells mailbox providers what to do with mail that fails those checks.
  • Start small. A brand-new address that suddenly sends thousands of emails looks like spam. Build up over a couple of weeks.

Only email people who asked to hear from you. Bought lists and cold outreach get your address blocked quickly, and that is your own domain you are burning.

Every campaign includes a one-click unsubscribe link and honours your suppression list. Never work around it — it is a legal requirement in most countries, not a preference.