billingHelp

Email through SMTP2GO

Creating the SMTP2GO account, verifying the sender domain with SPF, DKIM and DMARC, the API key, the bounce and spam webhook, and testing.

Receipts, password resets, invitations, alerts and digests are sent through SMTP2GO's HTTP API. Until email is configured, messages wait in the outbox (Super → Health & jobs) and nothing is lost.

1. Create the account#

Sign up at smtp2go.com. Choose a plan that covers your monthly volume: one email per payment, plus account emails, alerts and digests.

2. Verify the sender domain#

The sender address is receipts@ your domain (for example [email protected]). In SMTP2GO → Sending → Verified Senders → Sender Domains, add the domain. SMTP2GO shows DNS records to create at your DNS host:

RecordPurpose
CNAME records for DKIM (s….domainkey)Signs every message so receivers can trust it
CNAME for the return path (em….yourdomain)Handles bounces and aligns SPF
CNAME for link tracking (optional)Branded tracking links; leave tracking off for receipts

Wait until SMTP2GO shows the records as verified.

3. SPF and DMARC#

  • SPF: with SMTP2GO's return-path record, SPF aligns on that subdomain. If your domain already has an SPF record for other mail, keep a single SPF record and add include:spf.smtp2go.com to it.
  • DMARC: publish a TXT record at _dmarc.yourdomain, starting with monitoring and tightening later:
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain; adkim=r; aspf=r

After a few weeks of clean reports, move to p=quarantine, then p=reject.

4. Create the API key#

SMTP2GO → Sending → API Keys → Add API Key. Allow the /email/send endpoint; nothing else is needed. Copy the key (api-…).

5. Configure the platform#

Super → Settings → Email:

  1. Transport SMTP2GO, the sender address, the API key (stored sealed) and the API region of your account.
  2. Save, then Send test message. It goes to your own address and runs the sender at once.

6. Add the bounce and spam webhook#

The Email screen shows a webhook URL. In SMTP2GO → Settings → Webhooks, add it for bounce and spam events. Addresses that bounce hard or complain are then suppressed: no more email is sent to them, and the Email screen lists them so you can lift a suppression after the customer fixes their address.

Checking deliverability#

  • Send the test message to a Gmail and an Outlook address and open Show original: SPF, DKIM and DMARC should all say PASS.
  • Each workspace's emails use the workspace name as the sender name and its support email as Reply-To, so customers' replies go to the right store.
  • If messages pile up in the outbox, the Email screen and Health & jobs show the last error from SMTP2GO.