mailescrow

Queue outbound emails for human approval before SMTP sending.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/acroca/mailescrow --skill mailescrow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mailescrow
Source: https://github.com/acroca/mailescrow/tree/main
Command: npx skills add https://github.com/acroca/mailescrow --skill mailescrow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

mailescrow provides a safe, human-supervised path for sending and receiving emails via a REST API, ensuring that outbound messages cannot be sent without explicit human approval and inbound messages are surfaced only after human review.

Core Features & Use Cases

  • Outbound emails are queued and require a human to approve or reject in a web UI before being sent via SMTP.
  • Inbound emails are captured via IMAP poll and presented for approval, then retrieved via API once approved.
  • The solution exposes a REST API for programmatic submission and retrieval; a web UI provides the approval workflow; IMAP folders track lifecycle; and SQLite persists emails.

Quick Start

Submit an outbound email via the REST API and approve it in the web UI to send.

Frequently Asked Questions about mailescrow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a human approval step before sending emails via a REST API?

To add a human approval step to email workflows, outbound messages submitted via a REST API are queued in a web UI where a human must explicitly approve or reject them before they are sent via SMTP.

What is a human-in-the-loop email proxy and how does it handle inbound emails?

A human-in-the-loop email proxy captures inbound emails via IMAP poll and presents them in a web UI for human review, making them available for retrieval via API only after they have been explicitly approved.

Can I integrate IMAP and SMTP workflows with a human approval gate for production use?

Yes, you can integrate IMAP and SMTP workflows with a human approval gate using SQLite persistence, ensuring production-grade email queuing and state tracking for both inbound and outbound messages.

What's the best way to queue outbound SMTP emails for manual review before dispatch?

The best way to queue outbound SMTP emails for manual review is to submit them through a REST API that stores messages in SQLite, surfacing them in a web UI for human approval before final SMTP delivery.

How do I retrieve approved inbound emails via API after IMAP polling?

You retrieve approved inbound emails by polling an IMAP folder that tracks the message lifecycle; once an email is approved in the web UI, it becomes accessible for retrieval through the REST API.

Do I need a database to persist email approval states in a human-in-the-loop workflow?

Yes, SQLite is used to persist email approval states and lifecycle data, ensuring that queued inbound and outbound emails are reliably tracked across the REST API and web UI.