Blazalek.com

Transfer DMARC reporting to a new MSP: client handover

When a client transitions to a new provider, its DMARC telemetry, DNS authorization records, and administrative access share collectors and accounts with clients who are staying. This register guides the handover step by step, pausing when dependencies are unverified and revoking access without disrupting neighboring domains.

By

On this page

To transfer DMARC reporting to a new MSP without interrupting clients who stay, each client needs its own reporting and change register, complete with named owners for every outstanding decision. When a client leaves, that register guides the transfer of historical reports, routing configuration, and administrative access. This procedure assumes domain intake and sending responsibilities are already documented.

Every review ends in a decision

Agree on a review cadence and escalation triggers with each client. At each review, log the policy domain, Author Domains, reporter, report ID, UTC period, arrival timestamp, and input reference. An aggregate report covers a single policy domain, and its metadata identifies the reporting source and timeframe, as RFC 9990 sets out. For operational guidance on handling volume, see how to process DMARC aggregate reports at scale without ignoring them.

Compare incoming files against expected reporting sources, log missing feeds, and record your treatment of duplicate or overlapping inputs. Missing evidence is never a zero-failure result. Policy changes can also produce reports that mix periods, so store record revisions alongside evidence rather than attributing historical data to the latest configuration (RFC 9990 on policy transitions).

The client summary separates three elements: what incoming reports show, what the client’s approved source map confirms, and what actions remain outstanding. DMARC authentication validates a domain’s use in a message, which is the scope RFC 9989 gives it; in practice that means client business approval and domain or access ownership need evidence of their own. Report message counts include traffic that subsequent filters may block, and the disposition code reflects the DMARC policy outcome. Neither proves inbox delivery (RFC 9990: counted messages; DMARC disposition; placement limits).

For each proposed change, attach an operational ticket detailing its rationale, evidence references, exact previous, proposed, and observed DNS strings, TTL values, timestamps, approvals, anticipated results, and verification steps. Name the decision, DNS, data, access, and rollback owners, identifying the specific technician who executes DNS restoration. These are accountability roles rather than formal corporate titles. Retain historical revisions so incoming engineers understand why previous values changed.

Two clients, two different decisions

All individuals, evidence artifacts, and dates below are synthetic. The four domains cedar.example, birch.example, old-msp.example, and new-msp.example represent distinct Organizational Domains. Each client publishes an explicit DMARC record at its policy domain, which also serves as the header_from in its report.

ClientDecision ownerDNS executorData ownerAccess administratorRollback owner
Cedar, C-17MiraTheoAdaRaviNora; Theo executes DNS restoration.
Birch, B-09LeaIvoNoahZaraLee; Ivo executes DNS restoration.

The only reporter represented in this snapshot is receiver.example. Both reports cover 2026-10-06, 00:00:00–23:59:59 UTC, reach the legacy collector on October 7 at 06:00 UTC and are reviewed at 10:00 UTC. The files sit in isolated client workspaces. One technician maintains separate direct grants for Cedar and Birch within a shared administrative account; in this baseline scenario, no group grants exist.

Client and evidenceFindingsDecision and next action
Cedar: R-CED-06, report ID cedar-20261006120 messages from 192.0.2.10 pass evaluated DKIM alignment; disposition is none. Source-map entry C-SEND-1 records Mira’s approval of Cedar’s transactional service.Hold reporting-transfer ticket CED-17: successor authorization is absent. Ravi must obtain confirmation from the successor and record its access. Theo verifies authorization before changing DNS.
Birch: R-BIR-06, report ID birch-2026100639 messages from 192.0.2.20 pass evaluated DKIM alignment; one from 198.51.100.44 fails both evaluated DKIM and SPF alignment. All have disposition none. B-SEND-1 records Lea’s approval of the first service; the other source has no known business owner.Continue monitoring with source-identification exception BIR-09 open. Lea identifies the source; Zara preserves the technician’s Birch access. Review on October 8 at 10:00 UTC; escalate unresolved ownership to Lea.

Cedar’s report covers 120 messages; Birch’s covers 39 + 1 = 40. Neither dataset represents exhaustive receiver coverage. Merging them into a single portfolio pass rate would obscure Birch’s unverified sending source, and that authentication failure neither proves hostile spoofing nor justifies adding the unknown IP address to SPF.

What stops the transfer: the missing DNS confirmation

At the review, the active DNS records are:

_dmarc.cedar.example. 3600 IN TXT "v=DMARC1; p=none; rua=mailto:cedar@reports.old-msp.example"
_dmarc.birch.example. 3600 IN TXT "v=DMARC1; p=none; rua=mailto:birch@reports.old-msp.example"
cedar.example._report._dmarc.reports.old-msp.example. 3600 IN TXT "v=DMARC1"
birch.example._report._dmarc.reports.old-msp.example. 3600 IN TXT "v=DMARC1"

Ticket CED-17 proposes exclusively this Cedar modification:

_dmarc.cedar.example. 3600 IN TXT "v=DMARC1; p=none; rua=mailto:cedar@reports.new-msp.example"

Where the policy domain and report destination reside in distinct Organizational Domains, external reporting requires DNS confirmation: the query prepends the policy domain to _report._dmarc and the destination host, and RFC 9990 requires that an unconfirmed destination be ignored.

Cedar’s successor report mailbox and portal workspace are prepared, but the verification query returns no authorizing TXT record, and no wildcard confirmation exists in the target zone:

dig TXT cedar.example._report._dmarc.reports.new-msp.example

Elin, the successor’s endpoint administrator, must publish the confirming TXT string starting with v=DMARC1; Theo cannot edit that external zone. Until then, no DNS records change and no credentials are revoked. Exception CED-E1 logs Ada and Mira’s authorization for continued legacy collection until the next review on October 8 at 10:00 UTC, and Ravi escalates to them if confirmation remains missing or permission expires. Birch’s reporting configuration remains untouched.

How do you verify that the new MSP receives the reports?

Once confirmation exists, Theo can apply the approved Cedar revision and logs the observed value and timestamp. Ravi then verifies a parsed report attributable to Cedar, checking the reporting source and interval, and confirming that the successor sees Cedar’s telemetry and nothing else. Set the observation window from the expected sending volume and how often each reporter sends reports, because report delivery can fail and a published DNS record proves nothing about backend ingestion (RFC 9990 on report delivery).

This example supplies no successor report and no acceptance, so CED-17 remains open. If ingestion fails following a subsequent change, Nora coordinates restoration of the recorded Cedar value through Theo only while Ada and Mira still authorize the old recipient and that endpoint remains available. Otherwise the owners must select a permitted receiving arrangement.

Prior to final sign-off, furnish the successor with Cedar’s sender source map, coverage gaps, routing history, agreed evidence exports, open exceptions, and key technical contacts. Ada determines export boundaries, excluded records, retention schedules, and procedures for late-arriving reports; no universal data retention period applies. Formally document which operational responsibilities the successor assumes and who owns each unfinished task.

Removing Cedar’s access without touching Birch

Following formal handover acceptance, Ravi revokes Cedar’s outgoing permissions and handles separately inventoried service identities and credentials through their actual mechanisms; credentials stay out of the shared register. Zara verifies that Birch remains fully operational, because deleting the shared technician account or the collector platform would go beyond what Cedar’s departure requires.

Check inherited permissions alongside direct grants. For example, Cloudflare combines direct and group policies to determine effective permissions (documentation checked September 15, 2026), so inspect both direct and inherited views. Always confirm how your specific provider handles inherited roles before revoking access. Membership checks alone do not establish what happened to separate credentials.

Retire Cedar’s client-specific authorization TXT record once it is no longer required, preserving Birch’s record intact. A shared wildcard record that continues to cover Cedar’s query authorizes external report receipt even after the specific hostname record is deleted, and deauthorization must account for positive DNS caching up to the record’s TTL (RFC 9990: external authorization).

If other active clients require that wildcard record, maintain their service and document Cedar’s residual authorization as an open exception, with Ravi coordinating between the endpoint administrator, Ada, and Mira, backed by a scheduled review date. Deauthorization remains incomplete while that wildcard covers Cedar. Once Cedar’s collection authorization terminates, remove the legacy address from approved routing and follow Ada’s agreed process for late-arriving reports.

If forensic failure reporting is active, review its recipient addresses, diagnostic payload, header redaction, and access controls separately with Ada. Failure reports can expose message content and headers, and migrating aggregate telemetry offers no operational reason to activate ruf (RFC 9991: failure-report privacy).

Complete the next-action register before concluding the review: Cedar awaits Elin’s DNS confirmation coordinated through Ravi; Birch awaits Lea’s source identification. Both cases return for scheduled review on October 8 at 10:00 UTC.

Two related resources cover neighboring operational workflows: Interpret a DMARC aggregate report and Document client domain authority.

Frequently asked questions

Does changing the rua address prove the new collector receives reports?

No. Modifying DNS proves nothing about ingestion, and report delivery can fail. Handover requires verifying a parsed aggregate report attributable to the client, confirming its reporter and interval, and validating tenant data isolation.

Is missing report evidence a zero-failure result?

No. Missing report telemetry reflects an evidence gap rather than successful authentication. Compare arrived reports against expected reporting sources and log missing feeds as open items.

Does a DMARC report count prove delivery or inbox placement?

Report counts include messages that other filters may block, and the disposition describes the DMARC policy result. Neither proves delivery or inbox placement.

Does removing a client’s _report._dmarc record end external authorization if a wildcard remains?

A shared wildcard that still covers the client’s query continues to authorize external receipt even after the client’s specific record is gone. Withdrawal also has to allow for positive DNS caching up to the confirming record’s TTL.

Should transferring aggregate reporting include enabling failure reports?

Transferring aggregate reporting is no reason to enable failure reports, because such reports can expose headers or message content. If failure reporting is already enabled, review its recipients, diagnostic content, redaction and access separately with the client’s data owner.

Complete your client handover register

Email deliverability consultant

Get a second opinion on your email setup

Tell me what your customers are seeing or what you’re planning to change. In 30 minutes, we’ll work out what your team can check first and whether a deliverability audit would help.

I led deliverability at GetResponse, designed a dedicated newsletter system for Easy.Tools and helped Youmoney migrate its automated emails in stages. Read the case studies

Book free call

Email deliverability audit

See what I check and read a sample report with recommendations for your team.