Nuntly

Over the limit? Fixes: 1. Replace `include:` with `ip4:` for static services 2. Remove includes for services you no longer use 3. Flatten nested includes (refresh when IPs change) Nuntly uses a single include. One lookup. nuntly.com/blog/email-del… #EmailDeliverability #SPF

How to audit your SPF lookups: 1. Run `dig TXT yourdomain.com +short` 2. Count each `include:`, `a:`, `mx:`, and `redirect=` 3. Follow each include and count its nested lookups 4. Total must stay under 10 Over 10? Your SPF silently fails on every email.

SPF records have a 10 DNS lookup limit. Most developers don't know this, and their authentication silently fails when they exceed it. Here's how to check yours and fix it: 🧵 #email #security #spf

Resend gives your agent an email. Nuntly gives it an inbox with memory. That's the difference between sending notifications and having real conversations. Make your OpenClaw happy with Nuntly. #OpenClaw #AIAgents #EmailAPI #DevX

Make your OpenClaw happy. Give it an inbox with memory! ...not only an email address. With Nuntly, your OpenClaw agent can create inboxes, receive messages, load conversation history, reply, and persist context. #OpenClaw #AIAgents #EmailAPI #DevX nuntly.com/blog/ai-agent-…

4 new webhook events: - message.received - message.security.flagged - message.agent.triggered - message.sent All support event replay. Available on all plans (free tier included). nuntly.com/blog/introduci…

Use case 3: Multi-tenant routing with namespaces. One namespace per customer, client, or agent cluster. Isolated inboxes, separate state, single API call to query all messages for a tenant. SaaS, agencies, AI platforms, ... #AI #Agent Next use case 🧵

Sending email is half the picture. Support tickets, billing queries, AI agents acting on inbound messages. All need a receiving API. Nuntly now handles inbound email natively. 📫 Same platform, same API, same domain. Three use cases shipped today 🧵 #inbound #outbound #DevX

DNS setup is a solved problem. The feedback loop around it wasn't. Now it is 👍

When something doesn't match, you get debug commands ready to copy/paste into your terminal. When everything is green, you know it instantly 🥰

Setting up a sending domain shouldn't feel like guesswork. Every developer who's configured email DNS records knows the drill: copy a DKIM key, paste it into your DNS provider, add SPF, DMARC, MX records. Then wait 🤨 Thread 🧵

We also added a "summary" memory. Instead of replaying full conversation history to your LLM, you generate a short summary after each turn. Coming soon on Nuntly 🥰 #AI #Agent

Your AI Agent handles incoming emails ... but Agents have no memory between messages 😱 An agent without memory is just an auto-responder! We built "Nuntly Agent Memory" to fix this. Coming soon on Nuntly 🥰 #AI #Email #AIAgent