The most delicate surgery was the DKIM signing. Without it, their emails were anonymous, unsigned letters. She generated new 2048-bit keys, linked them to the DNS records, and told PMTA:
Not with a dramatic spark or a scream, but with a slow, agonizing wheeze. Every outgoing email, from a forgotten password reset to a multi-million dollar invoice, hung in its queue like a condemned prisoner. The logs were a scarlet tide of errors: 550 5.7.1 , 421 4.7.0 , and the most feared of all, Deferred: Connection timed out . pmta configuration
The final step was the outbound access rules. She built a firewall in code: The most delicate surgery was the DKIM signing
She opened the file. It was a cathedral of text—thousands of lines of directives, domain keys, DKIM selectors, and IP pools. It looked less like a config file and more like a spell book written by a paranoid genius. Every outgoing email, from a forgotten password reset
Vera had inherited Artemis from a ghost. The previous admin, a wizard of arcane scripts named "Grendel," had left behind a single sticky note: PMTA config: /etc/pmta/config . No password. No explanation. Just a file path.
The dam broke. The queue, once a frozen river, became a raging, orderly torrent. Messages flew out—receipts to accountants, password resets to panicked users, and yes, the cat trees. But now they were polite cat trees. Respectful cat trees. Cat trees that had been properly introduced, rate-limited, and cryptographically signed.
“It’s the reputation,” said Vera, the senior sysadmin, staring at the blinking cursor. Her coffee had gone cold hours ago. “We’re not just a server anymore. We’re a suspect.”