DKIM: a field note from a marina

We do not start with a platform when handling DKIM. We write down who types what, who gets the mail, and what must not get lost. That list is always shorter than a vendor pitch deck.

The registrar dashboard crashed twice while we were fixing DKIM for a marina. We filed a ticket; they replied four days later with a template answer.

We found a CAA record that blocks the new CA during a routine check of DKIM. The site had been leaking referrer data for six weeks before anyone noticed.

Fixing DKIM cost less than the lunch meeting where a marina decided to wait another quarter. Waiting is never free.

If you only touch DKIM once a year, a dashboard is extra risk. Files, a mailbox you read, and a person who still answers will outlast any SaaS control panel.

Before you touch DKIM, take a screenshot of the current state. Half of our emergency calls come from people who cannot remember what was there before the change.

More notes

Related notes

• Managing DKIM at a walk-in clinic
• Managing DKIM at a restaurant
• Managing DKIM at cabin rentals
• A practical look at DKIM for a plant nursery