Prad Nukala
6406208b35
- 16 cross-shell utilities converted to sh/bash chezmoi executables: ai c2p cp-appid extract_agents fab gdc gh-sonr-org-migrate ghg-clone ghn gho git-summary launch_omp_livediff_overlay lc-elir mdcp mdp pj (ghg-clone not named ghg: unrelated cargo binary owns that name) - cwd/history helpers stay per-shell: yy c cd clip-last + ghg/ghn/gho cd-wrappers in bash/functions/ and zsh/functions/, loaded by rc files - fish keeps only shell-state functions; converted ones now hit PATH - cp-appid ignore gating moved to .local/bin path - dot_agents/skills: 82 skills materialized from dotstate storage so dot_claude skill symlinks resolve on fresh bootstrap; dotstate profile/symlinks.json released .agents/skills .bashrc .zshrc
3.4 KiB
Cloudflare Email Routing Skill Reference
Overview
Cloudflare Email Routing enables custom email addresses for your domain that route to verified destination addresses. It's free, privacy-focused (no storage/access), and includes Email Workers for programmatic email processing.
Available to all Cloudflare customers using Cloudflare as authoritative nameserver.
Quick Start
// Basic email handler
export default {
async email(message, env, ctx) {
// CRITICAL: Must consume stream before response
const parser = new PostalMime.default();
const email = await parser.parse(await message.raw.arrayBuffer());
// Process email
console.log(`From: ${message.from}, Subject: ${email.subject}`);
// Forward or reject
await message.forward("verified@destination.com");
}
} satisfies ExportedHandler<Env>;
Reading Order
Start here based on your goal:
- New to Email Routing? → configuration.md → patterns.md
- Adding Workers? → api.md § Worker Runtime API → patterns.md
- Sending emails? → api.md § SendEmail Binding
- Managing via API? → api.md § REST API Operations
- Debugging issues? → gotchas.md
Decision Tree
Need to receive emails?
├─ Simple forwarding only? → Dashboard rules (configuration.md)
├─ Complex logic/filtering? → Email Workers (api.md + patterns.md)
└─ Parse attachments/body? → postal-mime library (patterns.md § Parse Email)
Need to send emails?
├─ From Worker? → SendEmail binding (api.md § SendEmail)
└─ From external app? → Use external SMTP/API service
Having issues?
├─ Email not arriving? → gotchas.md § Mail Authentication
├─ Worker crashing? → gotchas.md § Stream Consumption
└─ Forward failing? → gotchas.md § Destination Verification
Key Concepts
Routing Rules: Pattern-based forwarding configured via Dashboard/API. Simple but limited.
Email Workers: Custom TypeScript handlers with full email access. Handles complex logic, parsing, storage, rejection.
SendEmail Binding: Outbound email API for Workers. Transactional email only (no marketing/bulk).
ForwardableEmailMessage: Runtime interface for incoming emails. Provides headers, raw stream, forward/reject methods.
In This Reference
- configuration.md - Setup, deployment, wrangler config
- api.md - REST API + Worker runtime API + types
- patterns.md - Common patterns with working examples
- gotchas.md - Critical pitfalls, troubleshooting, limits
Architecture
Internet → MX Records → Cloudflare Email Routing
├─ Routing Rules (dashboard)
└─ Email Worker (your code)
├─ Forward to destination
├─ Reject with reason
├─ Store in R2/KV/D1
└─ Send outbound (SendEmail)