reject unwanted mail during the SMTP transaction. don’t accept it and bounce it later.
the bounce goes to a forged sender, which makes you the spammer. spamhaus calls that backscatter and it costs you reputation.
5xx at RCPT TO, not a DSN afterwards.
full guidelines in the reply 👇
ses is the cheapst per send, no args. it's just that it's only the send.
templates, webhooks, scheduling, tracking, suppression, all yours to build.
and the domain onboarding process says no more often than you'd think.
As for HA: don't let your services talk to any provider synchronously. drop a local smtp relay in the cluster, it accepts in
milliseconds into a durable queue and drains with retry. a provider blip stops being your incident.
That's the transactional outbox pattern.
disclosure, We've build mailkube and we ship exactly that relay as a container:
https://t.co/m4EeAmEztX. run it cluster-wide with a persistent spool though, not as a sidecar, or queued mail dies with the pod.
rotate and keep it server-side is the actual fix, no argument.
worth adding a second layer though: pin the key to an ip allowlist and a key that does leak is useless from anywhere but your own servers. doesn't excuse shipping it, just means the blast radius is near zero while you rotate.
disclosure, i build one of these.
https://t.co/nzPOidH7TH
rotate and keep it server-side is the actual fix, no argument.
worth adding a second layer though: pin the key to an ip allowlist and a key that does leak is useless from anywhere but your own servers. doesn't excuse shipping it, just means the blast radius is near zero while you rotate.
disclosure, i build one of these.
https://t.co/nzPOidH7TH
a domain registered in the last 24 hours lands on spamhaus’ zero reputation list automatically.
their recommendation: wait at least 30 days before sending from a new domain, and warm it up like an IP. need a new stream? use a subdomain, not a fresh lookalike.
full guidelines in the reply 👇
spamhaus is explicit on this one: warm-up services that fake opens, clicks or replies are prohibited.
engagement inflation gets you listed. real warm-up is slow volume to engaged recipients, and treating every new IP or HELO as a fresh asset.
full guidelines in the reply 👇
a line from the spamhaus guidelines worth printing out: list validation services don’t clean spam traps and don’t replace permission.
validation catches typos and dead domains. it doesn’t make a purchased list yours.
full guidelines in the reply 👇
what spamhaus says about spam traps surprised me the first time I read it.
don’t try to identify or remove individual trap addresses. find the source that put them on your list, and remove the source.
a mailbox inactive for 12+ months can become a trap. sunset your inactives.
full guidelines in the reply 👇
spamhaus is direct about it: don’t stay at p=none permanently.
none is a monitoring mode. you set it, read the reports, fix alignment, then move to quarantine and reject. parking there for years means you have DMARC on paper and nothing else.
full guidelines in the reply 👇
two DKIM details from the spamhaus guidelines most setups miss:
2048-bit keys recommended (1024 is the floor), and rotate at least once a year.
most DKIM keys I’ve seen were generated once, years ago, and never touched.
full guidelines in the reply 👇
@devhunt_ Good list. Worth adding the tags and topics bit works over SMTP headers too, not just the API, so you get the same per-send labelling without rewriting your mail layer.
Nice if you're moving off an existing SMTP setup and don't want to touch application code.
Thanks for the feature.
The unlimited sending domains part is what I'd underline. Most free tiers give you one, and anyone running a side project plus a client thing plus a
startup hits that wall immediately.
https://t.co/IakiyUrhy1
⇨ mailkube by @fourat provides transactional email infrastructure through REST and SMTP. Send up to 4,000 emails per month for free, use unlimited sending domains and manage templates, webhooks and scheduled delivery.
Learn more: https://t.co/AGmn74C2FB