Valimail vs.
Free DMARC Weekly Digests by Postmark in 2026

In Valimail, Microsoft 365 and Google Workspace were recognized within the first report cycle and separated from SendGrid, Mailchimp, and the support desk sender. The SPF pass with visible-from mismatch was called out as a failure that needed sender correction, and the DKIM pass on the marketing subdomain stayed visible enough for policy planning. The unknown sender was easier to classify because Valimail grouped traffic by sender identity instead of leaving us with only IP fragments.

Free DMARC Weekly Digests by Postmark gave us the weekly pattern: top sources, pass/fail totals, and a clear signal that the unauthorized spoof sample existed. It worked for a one-domain watchlist, but the top-source cap and email-only workflow meant Microsoft 365, Google Workspace, SendGrid, and Mailchimp context had to be reconciled manually. The forwarded SPF failure showed up as a problem, but the digest did not explain the forwarding path well enough for a support handoff.

Valimail onboarding was clear but not instant: the primary domain and marketing subdomain needed more DNS verification steps than the parked domain, and paid-tier boundaries appeared while we tested reports and exports. Once traffic landed, the unknown sender was easier to trace because sender grouping, auth status, and domain scope lived in the same work area. Explaining the forwarded SPF failure still required DMARC knowledge, but the interface provided enough raw evidence for an internal note.

Postmark's free workflow was the easiest to start on the parked domain: create the DMARC record, verify DNS, wait for the weekly email. That simplicity became a constraint when the unknown sender appeared because the digest did not support a drilldown path or durable classification queue. The forwarded SPF failure could be described after reading the digest, but the explanation lived outside the product.

During setup, Valimail's path gave clearer expectations for DNS handoff, especially when Microsoft 365 and Google Workspace were approved but SendGrid and Mailchimp still needed service-owner confirmation. Escalation made sense on paid plans where account management and onboarding help are part of the purchase. For the support desk sender, the strongest support moment was having enough sender context to ask the right internal owner for DKIM evidence.

Postmark's free DMARC Weekly Digests did not need much support for the parked domain because setup was short and the weekly email was readable. That became less useful when the unknown sender and visible-from mismatch needed a decision path, not just a report. Enterprise onboarding, DNS handoff, and escalation were outside the free product experience we tested.

Valimail handled account separation better for an enterprise team than for a classic MSP book of clients. The primary domain, marketing subdomain, and parked domain could be grouped for internal ownership, and recurring executive-style reporting made sense for leadership updates. Client handoff still needed care because MSP-specific grouping and bulk client notes were not as direct as the sender investigation views.

Postmark's free product fit the SMB or owner-operator case: one domain, weekly email, and limited operational overhead. It did not give us account separation, client grouping, recurring client reports, or a shared classification workflow for MSPs. For enterprise use, the lack of drilldown made the support desk sender and unknown sender harder to hand off.