Moving DMARC from p=none to p=reject
Your DMARC record has said p=none for two years. Read the reports, fix alignment for every sender, then step to quarantine and reject without losing mail.
Filtering by topic #email · clear
Your DMARC record has said p=none for two years. Read the reports, fix alignment for every sender, then step to quarantine and reject without losing mail.
What Stalwart's single Rust binary replaces in a Postfix and Dovecot stack, what it cannot fix, and when a mailcow install is still the better call.
Send mail from self-hosted apps without running a mail server. One SMTP relay at host level, SPF, DKIM and DMARC, and a fix for blocked port 25.
Receiving mail on your own VPS is easy. Getting it delivered to Gmail is the hard part. What deliverability really demands, and when to relay instead.
Catch every test email on a throwaway domain with Mailpit, read it in a web UI, and stop your staging app from ever mailing a real customer again.
Abuse mail about your VPS IP follows a fixed pipeline. Who reports, how the notice reaches you, what each category means, and how to answer in time.
An attacker submits a victim's address to hundreds of signup forms at once. Confirmed opt in and rate limits stop your server sending one of them.
Run an MCP email server on your VPS so Claude can triage your inbox. App password scoping, sender allowlists, draft-only replies, and the injection risk.
Install Listmonk on Ubuntu 24.04 with Postgres, config.toml, a systemd unit and TLS, then connect SMTP and understand what deliverability really costs.
Test outbound port 25 before installing mailcow: a block means mail never leaves the queue. Then set the DNS that stops Gmail's 550 5.7.25 PTR rejection.