ConnfigConnfig Docs

Sending Domains

Adding a sending domain, DNS/DKIM/DMARC verification, warmup limits, and suppression logic

Campaign emails are sent from your own domains, which you add to Connfig and verify via DNS records. Domain management lives on the Profile page: adding a new domain, viewing DNS records, verifying, and deleting all happen there.

Use a subdomain for sending rather than your main domain (e.g. mail.example.com or crm.example.com). If you enter a root domain (e.g. example.com), the form automatically suggests mail.example.com. This protects your main domain's email reputation.

Adding a domain

  1. Go to the Domain Management card at https://app.connfig.com/profile.
  2. Enter the domain name (e.g. mail.example.com).
  3. Enter a sender header: the display name recipients see in their inbox (e.g. "Acme Support"). It may only contain English letters and digits, with at most 15 words.
  4. Enter a sender name: the part of the email address before the @ sign (e.g. john). It may only contain lowercase English letters and digits, with no spaces; uppercase letters are lowercased automatically.
  5. The preview under the form shows the sender format recipients will see (header plus name@domain).
  6. Click Create Domain.

DNS records and verification

After creation, the domain appears in the Domains table. To verify:

  1. Open the DNS records dialog from the domain's row. You will see three groups of records:
    • Sending records: SPF (TXT) and DKIM (TXT) records — these authenticate your emails.
    • Receiving records: MX records.
    • DMARC: a TXT record to add at the _dmarc.yourdomain host. The dialog also shows whether the DMARC record is configured.
  2. Copy each record and add it as the matching record type in your DNS provider's panel (Cloudflare, GoDaddy, etc.).
  3. Click Verify in the table. If the records have propagated, the domain becomes "Verified" and is ready for sending; otherwise you get a "verification pending" notice — DNS propagation can take a while, try again later.

Only verified, non-disabled domains are used for campaign sending. The campaign dispatcher spreads the load across your domains, starting with the domain that has sent the least that day.

Warmup and daily limits

To protect the reputation of new domains, daily send limits ramp up gradually:

Cumulative total sendsDaily limit
0 - 41920 emails/day
420 - 209950 emails/day
2100 and above100 emails/day

Daily counters reset every day and the limit is recomputed from the domain's cumulative send count. In addition, a random delay (60-180 seconds by default) is inserted between consecutive sends, which keeps the sending pattern natural. If your campaign exceeds your domains' combined daily capacity, sending automatically spills over into the following days — when the campaign is planned, you receive a notification with the estimated number of days.

Suppression logic

To protect recipients and your domain reputation, Connfig adds addresses that unsubscribe or file a spam complaint to a suppression list:

  • Every campaign email automatically includes an unsubscribe link.
  • The suppression list works per account owner: if an address unsubscribed from any of your workspaces, none of the workspaces you own will ever email that address again. Other Connfig users are unaffected.
  • Suppressed addresses are excluded when the campaign recipient list is built; additionally, a second check runs at send time to catch addresses that unsubscribed mid-campaign — those recipients are marked as "skipped".
  • CRM records marked as opted out are never included in campaigns at all.

Mini scenarios

Scenario 1 — Setting up your first sending domain: A marketer is about to send their first campaign from Connfig. On the Profile page they create the domain mail.acme.com with the header "Acme" and sender name support. They add the SPF, DKIM, MX, and DMARC records from the DNS dialog to Cloudflare and click Verify a few minutes later. Once the domain shows "Verified", it becomes selectable as a sender on the Campaigns page.

Scenario 2 — Capacity planning for a large campaign: A team wants to reach a list of 5,000 contacts. Since a single new domain starts at a daily limit of 20, two weeks in advance they add and verify three subdomains (m1.acme.com, m2.acme.com, m3.acme.com) and warm them up with small campaigns. When the big campaign starts, the dispatcher splits the load across the three domains, and daily capacity grows automatically as the limits ramp up.