惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

D
DataBreaches.Net
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Google DeepMind News
Google DeepMind News
博客园 - 聂微东
Microsoft Azure Blog
Microsoft Azure Blog
V
Visual Studio Blog
IT之家
IT之家
博客园 - 【当耐特】
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
B
Blog
爱范儿
爱范儿
阮一峰的网络日志
阮一峰的网络日志
云风的 BLOG
云风的 BLOG
Vercel News
Vercel News
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
H
Hackread – Cybersecurity News, Data Breaches, AI and More
H
Help Net Security
J
Java Code Geeks
aimingoo的专栏
aimingoo的专栏
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
B
Blog RSS Feed
Blog — PlanetScale
Blog — PlanetScale
S
SegmentFault 最新的问题
Apple Machine Learning Research
Apple Machine Learning Research

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
OpenClaw outbound agents need deliverability checks befor...
live-direct- · 2026-05-19 · via DEV Community

live-direct-marketing

Some agents can even schedule or send campaigns automatically.

But most outbound agents still do not know one important thing before sending:

Will the email land in Inbox, Spam, Promotions, or Junk?

For cold outreach, recruiting, investor updates, partnership outreach, and deal-flow automation, this becomes a real operational risk.

AI agents are getting very good at:

copy generation
personalization
sequencing
lead enrichment
autonomous workflows

But email deliverability is a different layer entirely.

An agent can generate a perfectly reasonable email that still lands directly in Spam.

That happens because deliverability depends on factors the model usually does not evaluate:

sender-domain reputation
SPF/DKIM/DMARC alignment
mailbox-provider filtering
HTML structure
tracking links
subject line patterns
sending infrastructure reputation

The result is a common failure mode:

The agent believes the campaign succeeded because emails were technically sent, while recipients never actually see them.

For autonomous outbound systems, this is a dangerous blind spot.

Before bulk outbound, run a deliverability preflight. If inbox placement is below 70%, pause and report fixes instead of sending.

That policy works surprisingly well as a safety rail for outbound agents.

Instead of optimizing only for “send success”, the agent also evaluates whether messages are likely to reach the inbox.

Two OpenClaw skills for deliverability preflight

I built two small OpenClaw skills around this workflow.

They are intentionally focused on outbound safety behavior rather than “email marketing”.

Skill 1 — LDM Deliverability Check

This is the lightweight policy layer.

Good fit for:

default outbound-agent behavior
pre-send checks
workflow rules
autonomous pause/report logic

The skill can:

evaluate outbound risk before send
stop risky campaigns
act as a safety layer in autonomous workflows
enforce deliverability policies

ClawHub:
https://clawhub.ai/live-direct-marketing/ldm-openclaw-skill

GitHub:
https://github.com/live-direct-marketing/ldm-openclaw-skill

Skill 2 — LDM Inbox Check MCP

The second skill is the heavier workflow using real inbox-placement testing.

It uses:

ldm-inbox-check-mcp
seed-mailbox testing
provider placement validation
authentication checks

The workflow creates real test sends and evaluates placement across providers including:

Gmail
Outlook
Yahoo
Mail.ru
Yandex

It also checks:

SPF
DKIM
DMARC

If placement is bad, the agent pauses the campaign instead of continuing the send.

ClawHub:
https://clawhub.ai/live-direct-marketing/ldm-openclaw-inbox-mcp-skill

GitHub:
https://github.com/live-direct-marketing/ldm-openclaw-inbox-mcp-skill

MCP package:
https://www.npmjs.com/package/ldm-inbox-check-mcp

MCP GitHub:
https://github.com/live-direct-marketing/ldm-inbox-check-mcp

Example workflow

A simple outbound-agent flow could look like this:

OpenClaw drafts 50 cold emails.
The agent runs an LDM preflight.
Gmail or Outlook placement lands in Spam/Junk.
The agent pauses instead of sending.
The agent reports fixes:
subject line
links
authentication
HTML structure
The user updates the campaign.
The agent reruns the check.
Only then does the agent send.

This turns deliverability into a first-class decision point instead of a postmortem problem.

OpenClaw install examples

Install the lightweight policy skill:

clawhub install ldm-openclaw-skill

Install the inbox-placement MCP skill:

clawhub install ldm-openclaw-inbox-mcp-skill

Example MCP configuration:

{
"mcpServers": {
"inbox-check": {
"command": "npx",
"args": ["-y", "ldm-inbox-check-mcp"],
"env": {
"INBOX_CHECK_API_KEY": "icp_live_xxxxxxxxxxxxxxxxxxxxxxxx"
}
}
}
}
Useful outbound-agent use cases

The workflow is useful anywhere autonomous systems send external email:

cold email campaigns
recruiting outreach
investor updates
deal-flow alerts
partnership outreach
transactional-mail audits
sender-domain warmup QA

The important part is not “sending more email”.

The important part is teaching outbound agents when not to send.

Closing note

If you are building outbound, recruiting, investor-update, or deal-flow agents with OpenClaw, I’d love feedback on the workflow.

Resources:

https://check.live-direct-marketing.online
https://developers.live-direct-marketing.online
https://clawhub.ai/live-direct-marketing/ldm-openclaw-skill
https://clawhub.ai/live-direct-marketing/ldm-openclaw-inbox-mcp-skill
https://github.com/live-direct-marketing/ldm-openclaw-skill
https://github.com/live-direct-marketing/ldm-openclaw-inbox-mcp-skill
https://github.com/VoltAgent/awesome-openclaw-skills/pull/465