Email FAQ

Who actually sends my email?

Either CoreX's platform default (Resend), or your own connection. Add one under Settings → Email sending — SMTP or a provider of your own — and CoreX sends through it, so replies, reputation and deliverability sit with your domain rather than a shared one. The platform default is listed there too, as a read-only connection, so you can always see which one is in play.

Why won't my domain verify?

Domain verification is DNS, and DNS is slow and literal. The three records:

  • SPF authorizes the sending host. If you already have an SPF record, merge the include into it — two v=spf1 records is the same as none.
  • DKIM signs the message. Copy the key exactly; a wrapped or truncated value fails silently.
  • DMARC tells receivers what to do when the first two disagree. Start at p=none and tighten once you see clean reports.

Publish, then wait for the TTL to expire before re-checking. A domain sits in pending until every record resolves.

What happens to a bounce or a spam complaint?

CoreX ingests the provider's delivery webhook and records delivered, opened, clicked, bounced and complained against the individual send. Bounces and complaints also add the address to your suppression list automatically, with the reason recorded — so the next campaign skips it without you doing anything.

Can I remove someone from the suppression list?

Yes, under Email → Suppressions, and you can add addresses manually too. Treat removing a hard bounce or a complaint as a deliverability decision, not an administrative one: repeatedly mailing an address that complained is the fastest way to damage a domain's reputation.

How does unsubscribe work?

Every marketing email carries a one-click unsubscribe header (RFC 8058) as well as the {{unsubscribe_url}} link in the footer, so a recipient can opt out from the inbox UI without opening the message. Either route lands them on the suppression list immediately.

Why is my campaign still "scheduled"?

A campaign moves draft → scheduled → sending → sent. campaigns:dispatch-due picks up scheduled campaigns every minute, so a campaign that stays scheduled past its send time means the scheduler or the queue worker is not running — check those before suspecting the campaign.

My campaign went to nobody. Why?

Almost always the audience. A campaign targeted at a segment sends to the members that segment resolves to at send time — an empty or deleted segment yields no recipients rather than falling back to everyone. Check the segment's live count before scheduling, and send yourself a test first.

Do merge tags work everywhere?

Yes — campaigns, templates and the send_email flow action all use the same renderer. See Email variables for the full list. An unknown tag renders empty rather than as literal {{…}}, so proof a test send.