Technical note · Third-party sender integration

What to check before a third-party platform sends using your domain

A CRM, billing platform or website can become an email sender before the organization has decided who owns its configuration. The application works, the first message arrives, and the integration is treated as complete. Authentication, access and ongoing responsibility may still be unresolved.

In this note
  1. Begin with the purpose and the owner
  2. Establish which system actually sends
  3. Choose the domains and identities deliberately
  4. Verify authentication and alignment together
  5. Review access separately from DNS
  6. Agree the change and the evidence of success
  7. Make reporting and offboarding part of the handoff
  8. Primary sources

A useful readiness review follows each intended message from the application to the receiving system. It establishes which identities the platform will use, which changes are necessary and who will maintain them after launch.

Begin with the purpose and the owner

Record what the platform needs to send: individual correspondence, invoices, password resets, appointment notices, campaigns or another defined message type. Identify the audience, expected volume, business consequence of failure and mailbox that should receive replies. An invoice and a newsletter may need different operating arrangements even when they originate in the same product.

Assign a business owner who can confirm that purpose, a technical owner for authentication and routing, and an administrator authorized to approve changes. Include the existing IT provider where responsibilities overlap. The resulting sender inventory should identify the application, relevant account, domains, message types and responsible people. A vendor login alone does not establish ownership of the organization's email configuration.

Establish which system actually sends

An Outlook or Gmail add-in may display CRM information or record correspondence while the mailbox platform continues to send the message. Another function in the same CRM may generate email through the vendor's infrastructure or through a configured relay. Each path needs its own review.

Salesforce's guidance distinguishes sending through Gmail, Office 365, Salesforce and Email Relay. It also explains that workflow and system messages can follow a different path from messages composed by a user. Successful installation of an add-in therefore establishes little about the authentication of every outbound function.

Map those functions separately. Ask the vendor which service submits each message, which relays intervene and where logs can be obtained. Confirm that description against representative received messages before changing DNS.

Choose the domains and identities deliberately

For each path, record three identities:

  • Visible From domain: the domain in the address presented to the recipient.
  • DKIM signing domain: the d= value in a signature that validates.
  • Envelope-sender domain: the SMTP MAIL FROM identity, normally reflected in the delivered message's Return-Path.

Decide whether the application should use the main domain or a dedicated subdomain, and identify the applicable authentication and DMARC policy. Microsoft recommends considering a subdomain for third-party sending outside the organization's direct control. The choice should also reflect who administers that sender, how replies and bounces are handled, and how the service will eventually be retired.

A subdomain still needs a documented configuration. Treat it as an explicit part of the domain estate, with ownership and review responsibilities attached.

Verify authentication and alignment together

RFC 9989, the current DMARC specification, evaluates alignment between the visible From domain and an authenticated SPF or DKIM identity. At least one aligned mechanism must succeed for DMARC to pass. A provider can pass authentication for its own domain while the message fails DMARC for the organization's visible From domain.

For DKIM, record the signing domain and selector, then verify the signature on a received message. The DKIM specification explains how the selector and signing domain locate the verification key. Publishing a vendor-supplied record should be followed by a check that the intended sending function actually signs with it.

Review the vendor's exact setup rather than assuming every service needs the same records. For example, SendGrid documents CNAME-based authentication, custom return-path domains and selector choices. Record any delegated DNS names, their purpose and existing dependencies before adding or replacing them.

For SPF, establish which domain the receiving system evaluates. Adding a vendor to the main domain's record does not change a provider-controlled envelope-sender identity. Preserve one SPF policy at each relevant name and assess the full evaluation path, including nested includes. RFC 7208 limits the DNS-querying terms used during an SPF evaluation to ten; this is not a limit of ten vendors. An unnecessary include can consume lookup headroom without correcting alignment.

Review access separately from DNS

An application may need permission to send through a mailbox even when no new external sending infrastructure is introduced. Review the requested permissions, the accounts or mailboxes affected, who grants consent and how that access can be withdrawn.

Microsoft Graph distinguishes delegated access from application access. The former acts on behalf of a signed-in user; the latter operates using the application's own identity. Those differences matter when assessing the reach of an integration. Grant the access needed for the agreed functions and document any broader requirement that cannot be avoided.

Record which credentials and permissions the application uses, who owns them and how access can be revoked. Keep secret values out of ordinary project notes. Specify the owner responsible for renewing or rotating credentials.

Agree the change and the evidence of success

Before implementation, record the proposed DNS and platform changes, approvals, dependencies and rollback procedure. Preserve the previous configuration. Confirm who can pause the application's sending if tests expose a problem.

Test each material message type through its intended path. Capture complete received headers and compare the From domain, envelope sender, sending infrastructure, DKIM domain and selector, and authentication results. Separately verify replies, bounce handling and the application's required workflow. Record the destination and circumstances of each test so its limits are clear.

Provider requirements also extend beyond authentication. Google's sender guidelines for mail to personal Gmail accounts address transport security, sending practices and additional requirements for bulk or subscription mail. Apply the requirements relevant to the proposed use. A successful sample and valid authentication do not establish future inbox placement across all recipients.

Make reporting and offboarding part of the handoff

Assign responsibility for reviewing the new sending path after rollout. DMARC aggregate reporting is specified in RFC 9990; its records include source addresses, message counts, identities and authentication or policy results. Use available reports alongside message samples and platform logs to assess whether the intended configuration is operating as expected. Record reporting coverage and any remaining uncertainty.

Changes to From addresses, sending products, relays or account configuration should trigger another review. Before stronger DMARC enforcement, account for legitimate streams and unresolved exceptions; receiving systems retain discretion over message handling under RFC 9989.

The handoff should also explain how the platform will be removed: stop scheduled and triggered sending, resolve queued work, revoke its access, and review the DNS names and reporting destinations it uses. Remove obsolete authorization only after checking dependencies, then update the sender inventory.

Boutique Ink approaches sender integration as a defined configuration and handoff project. The useful result is a sending path that the organization can explain, verify and maintain, with the limits of testing and any remaining responsibilities recorded.

Primary sources

Sources checked November 10, 2026. Provider instructions are specific to their products and should be rechecked before implementation.

  1. RFC 9989 — DMARC, especially §§4.4 and 5.1–5.3. Published May 2026; supersedes RFCs 7489 and 9091.
  2. RFC 7208 — SPF, especially §§3.2 and 4.6.4.
  3. RFC 6376 — DKIM, especially §§3.1 and 3.5.
  4. RFC 9990 — DMARC aggregate reporting, especially §3.1.1.
  5. Salesforce — Email setup options.
  6. Microsoft — SPF for custom cloud domains.
  7. Microsoft — Microsoft Graph permissions.
  8. Twilio SendGrid — Domain authentication.
  9. Google — Email sender guidelines.

Plan the next sender.

A short description of the domain, the objective and the platforms involved is enough to begin.

Discuss a sender integration

Full message headers and DMARC aggregate reports are welcome. Please omit credentials, message bodies and their attachments, and DMARC forensic/failure reports. Full inquiry guidance

Explore Third-Party Sender Integration
← Return to Insights