dotMARC v0.8.1: DKIM records filled in for you, and a tidier API description
A small release after v0.8.0, from setting up DKIM with the new push on real domains.
A small release after v0.8.0, from setting up DKIM with the new push on real domains.
The biggest release since v0.7.0. dotMARC now keeps a record of who changed what,
takes domains in bulk, warns you when a domain's DNS goes wrong rather than waiting for the reports to show it, can
fix SPF and DKIM for you, and can be driven from your own scripts and tools.
A small release after v0.7.2. Now that dotMARC loads every Halo client, the list
is long enough that scrolling through it gets old, so the dropdowns that grow with your data can now be searched.
A small release after v0.7.1, with one fix for anyone with a lot of Halo clients and a
couple of things that make day-to-day work quicker.
A small release after v0.7.0, mostly about how things look and one warning that
shouldn't have been there.
Since v0.6.0, this release has mostly been about trust: fixing things that were
quietly not working, and giving you ways to see for yourself that they do.
Since v0.5.0, the Dashboard and Manage Domains tables have picked up the two
things people ask for first once they're managing more than a handful of domains: sorting and
filtering.
Since v0.4.0, dotMARC picked up a third DNS push provider, a genuinely new kind
of insight into why mail gets rejected or quarantined instead of just that it did, and a
self-hosting story that no longer assumes you already know how to wire up a reverse proxy.
Since v0.3.0, dotMARC picked up four things worth calling out: tickets that open
and close themselves in HaloPSA, DNS pushes that can now fix a record instead of just refusing to
touch it, one more Azure-only gap closed in MTA-STS, and a real breakdown of everything dotMARC
actually knows about a domain's health.
Since v0.2.0, dotMARC picked up four things worth calling out: alerts when a
domain goes quiet, a second report type alongside DMARC, a much faster way to make the DNS changes
dotMARC asks for, and a way to tell us what you want next.