Skip to main content

dotMARC v0.11.1: keep several rua addresses, and a DKIM column on the dashboard

· 3 min read
Creator of dotMARC

A small follow-up to v0.11.0. It catches a rua= mistake the last release missed, lets the DMARC push keep more than one report destination, and adds DKIM to the dashboard table.

A rua address without mailto: is flagged​

rua= is a list of URIs, so every address needs its mailto: prefix. A record such as rua=mailto:[email protected],[email protected] is wrong: receivers skip [email protected], so that destination quietly receives nothing. v0.11.0 ignored the entry and showed a plain OK.

The DMARC check now reports Misconfigured for any address missing its prefix, and the detail names the address. It alerts like any other misconfigured record, and the DNS push can fix it.

The DMARC push can keep several destinations​

The push used to replace rua= with dotMARC's mailbox alone, so it could not be used while you still wanted another tool to receive reports. It now writes dotMARC's mailbox first, then:

  1. the additional rua address, if you set one,
  2. then the other addresses already in the record, in their original order, with any missing mailto: added,

up to the two a record can reliably list. The confirm step shows the exact record before anything is written. Two settings in the DNS records section of the DNS push settings page control this:

  • Keep other rua addresses when pushing is on by default. Turn it off and a push writes dotMARC's mailbox, plus the additional address if there is one, and nothing else. Use that when you finish a trial and want the other address gone.
  • Additional rua address is a second destination added to every DMARC record dotMARC pushes, for example to keep sending reports to another tool. If its domain differs from the domain being monitored, that domain has to publish an authorization record or receivers won't send reports to it.

The DMARC and MTA-STS page has the details.

Smaller changes​

  • DKIM on the dashboard. The domain table has a DKIM column beside SPF, with the same filter and sorting.
  • Clearer Azure update steps. The guide now names its two steps, setting your variables and then running the update, reminds each update command which variables it needs, and tucks the "what is running now" commands into an optional section.

Upgrading​

Upgrading needs no action. There is one small database migration, which adds the two new DNS record settings and runs by itself when the new version starts. The behaviour change to know about is that a DMARC push now keeps other report addresses already in a record, up to two in total. Before, it removed them. To get the old behaviour back, turn off Keep other rua addresses when pushing.