Help centre

How can we help?

Guides, FAQ, and integration walkthroughs. Search or browse by topic.

← All topics

Email SMTP2Go

Email sending (SMTP2GO)

Send every system email (password resets, quote PDFs, consent forms, enquiry replies) from your own verified domain with SPF and DKIM so it lands in the inbox, not spam.

Before you start

  • Access to the DNS for the domain you want to send from. Usually your Cloudflare, Route53, Namecheap or GoDaddy control panel.
  • An email address at that domain you can receive mail on (e.g. hello@yourdomain.com) so SMTP2GO can send the verification link.
  • A SMTP2GO account (or use the pre-provided default key on Launch, described below).
  • 15 minutes for the setup, plus up to 24 hours for full DNS propagation (usually 5-10 minutes in practice).

You can now configure your own sender per company

Head to Settings > Integrations > Email sending (per company). Set your From address, From name, an optional SMTP2GO sub-account API key and an optional Reply-to. The live DKIM / SPF / DMARC health card below the form tells you at a glance whether your DNS is set up correctly, and the Send test email button sends a real test using the sender you configured.

Leave the API key blank to use the platform's shared SMTP2GO key while still sending from your own From address. Add your own SMTP2GO sub-account key for full isolation and dedicated bounce reporting.

Setting up SPF, DKIM and DMARC

Three DNS records get you from "sends via SMTP2GO" to "verified inbox delivery from your own domain". You add all three in your DNS provider's control panel. Propagation is usually 5-15 minutes.

1. SPF (TXT)

  • Host: @ (or the root of your domain)
  • Type: TXT
  • Value: v=spf1 include:spfa.smtp2go.com ~all

If you already have an SPF record on the root domain, extend it rather than adding a second one. Two SPF records break authentication. For example, if you have v=spf1 include:_spf.google.com ~all, change it to v=spf1 include:_spf.google.com include:spfa.smtp2go.com ~all.

2. DKIM (CNAME)

  • Host: smtp2go._domainkey (some providers want smtp2go._domainkey.yourdomain.com)
  • Type: CNAME
  • Value: dkim.smtp2go.net

SMTP2GO also accepts a selector called s2048._domainkey. Either works. The DNS health card in the CRM checks both plus a couple of other common selectors, so whichever your DNS UI lets you add is fine.

3. DMARC (TXT)

  • Host: _dmarc
  • Type: TXT
  • Value: v=DMARC1; p=quarantine; rua=mailto:you@yourdomain.com (replace you@yourdomain.com with the address you want DMARC aggregate reports sent to)

Start on p=none for a week if you want to monitor before enforcing. Once you are confident SPF and DKIM are aligned, move to p=quarantine (or eventually p=reject) to protect your domain from spoofing.

Provider notes

Cloudflare
Set the DKIM CNAME to DNS only (grey cloud). Cloudflare's proxy strips CNAME records. TXT records for SPF and DMARC are fine either way. TTL: leave on Auto.
Namecheap
Under Advanced DNS, add each record with Host as shown above. Namecheap adds the domain suffix for you; do not repeat it.
GoDaddy
Under DNS Management, click Add for each record. GoDaddy sometimes takes 30-60 minutes to propagate the first change on a domain.

Verify with the health card

After you save your sender in the CRM, click Recheck DNS. The three pills show your live status:

  • Green - record found and correct.
  • Amber - record found but not optimal (e.g. SPF missing SMTP2GO, or DMARC still on p=none).
  • Red - record missing. Emails may fail authentication or land in spam.

Click any pill to open the details drawer and see the exact DNS record found plus a "How to fix this" note.

Step 1: Create the SMTP2GO account

  1. Go to smtp2go.com.
  2. Click Sign up free. Free tier includes 1000 emails per month, no card required.
  3. Verify your email address via the link SMTP2GO sends you.
  4. Choose the free plan or upgrade if you know you will send more than 1000 per month.

Step 2: Add and verify your sending domain

  1. Log into app.smtp2go.com.
  2. Left nav: Sending > Verified Senders.
  3. Click Domains > Add domain.
  4. Enter your domain (without www): yourdomain.com.
  5. Click Save. SMTP2GO now shows you a table of DNS records you must add.

Step 3: Add the DNS records

SMTP2GO shows three records. All are TXT or CNAME on subdomains, not on the root. Copy them exactly - even a leading space breaks verification.

SPF record

  • Type: TXT
  • Host: @ (or root, depending on your DNS UI)
  • Value: v=spf1 include:spfa.smtp2go.com ~all

If you already have an SPF record on the root domain, do NOT add a second one - combine them. E.g. if your existing record is v=spf1 include:_spf.google.com ~all, change it to v=spf1 include:_spf.google.com include:spfa.smtp2go.com ~all. Two SPF records = neither works.

DKIM CNAME

  • Type: CNAME
  • Host: s2048._domainkey
  • Value: dkim.smtp2go.net

Some registrars require you to add the domain to the host (s2048._domainkey.yourdomain.com). Others expect just the prefix. Read your DNS UI's help text carefully.

Return path (bounce handling)

  • Type: CNAME
  • Host: em
  • Value: return.smtp2go.net

Step 4: Verify

  1. Back in SMTP2GO's domain list, click Verify next to your domain.
  2. If DNS has propagated (usually 5-10 minutes), you get three green ticks: SPF, DKIM, Return Path.
  3. If you see red, wait 15 minutes and try again. If still red after 30 minutes, use dnschecker.org to verify the records are actually visible globally. Common cause: your DNS provider added the domain suffix twice, resulting in s2048._domainkey.yourdomain.com.yourdomain.com.

Step 5: Create an API key

  1. SMTP2GO left nav: Settings > API Keys.
  2. Click Add API Key.
  3. Description: Unavoidable CRM.
  4. Scope: leave defaults (send emails).
  5. Click Save.
  6. Copy the key. It starts with api- followed by 32 hex characters. Paste into a password manager immediately - SMTP2GO does not show it again.

Step 6: Paste your sender into the CRM

  1. In the CRM go to Settings > Integrations.
  2. Scroll to Email sending (per company) near the top.
  3. Fill in From email (e.g. hello@yourdomain.com) and From name (e.g. your company name).
  4. Optionally paste your SMTP2GO sub-account key into SMTP2GO sub-account API key. Leave it blank to use the shared platform key.
  5. Optionally set a Reply-to email. Defaults to your From email if left blank.
  6. Click Save sender. The DNS health card auto-refreshes.
  7. Click Send test email and enter your inbox. The test uses your configured sender
Still stuck?
Email us and we’ll come back within one business day.
info@unavoidablecrm.com