Configuration | Pmta

Accepted connection from 127.0.0.1 DKIM signature verified for yourdomain.com Queue started: 10 messages active Delivered: 550c7e1f to gmail-smtp-in.l.google.com (250 2.0.0 OK)

<source 192.168.1.10/28> allow-mail-from *@yourdomain.com require-auth yes max-message-size 10M max-recipients 100 </source> pmta configuration

Vera saved a backup, added a new sticky note to the monitor: PMTA config: be gentle, be verified, be boring. And for the first time in a week, she went home before sunrise. Accepted connection from 127

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 previous admin, a wizard of arcane scripts

The problem wasn’t malice. It was configuration.

The CEO, a man who believed “the cloud” was a literal weather phenomenon, had demanded answers. Their marketing campaign—ten thousand personalized offers for luxury cat trees—was stuck in a digital traffic jam. Every major email provider had flagged Artemis as a potential spammer.