CLI Reference / Email

Email Commands

Deploy and manage AWS SES email infrastructure with event tracking, analytics, and domain management.

wraps email init

Deploy new email infrastructure to your AWS account. This is the primary command for setting up Wraps email for the first time.

Usage

terminal.sh

npx @wraps.dev/cli email init [options]

Options

-d, --domain <domain>

Domain to configure for sending emails (e.g., yourdomain.com)

-r, --region <region>

AWS region to deploy infrastructure (default: us-east-1)

--preset <preset>

Configuration preset: starter, production, enterprise, or custom

-p, --provider <provider>

Hosting provider: vercel, lambda, ecs, or ec2

--preview

Preview infrastructure changes without deploying

What It Does

Validates your AWS credentials and account access
Prompts for configuration preferences (if not provided via flags)
Shows estimated monthly AWS costs based on selected features
Deploys AWS SES, DynamoDB, Lambda, EventBridge, SQS, and IAM roles
Sets up OIDC provider for Vercel deployments (if selected)
Creates configuration metadata for future commands
Takes 1-2 minutes to complete

Examples

Interactive setup (recommended for first time):

terminal.sh

npx @wraps.dev/cli email init

Non-interactive with all options:

terminal.sh

npx @wraps.dev/cli email init --domain yourdomain.com --region us-west-2 --preset production --provider vercel

wraps email status

Display detailed status for email infrastructure, including SES domains, verification status, and configuration details.

Usage

terminal.sh

npx @wraps.dev/cli email status

What It Displays

SES domain verification and DKIM status
MAIL FROM domain configuration
Active features and preset
Deployed AWS resources
DNS records that need configuration

wraps email domains

Manage domains in AWS SES. Add domains, list all configured domains, retrieve DKIM tokens, verify DNS records, and remove domains from SES.

wraps email domains add

Add a new domain to AWS SES with DKIM signing enabled.

Usage

terminal.sh

npx @wraps.dev/cli email domains add -d <domain>

Options

-d, --domain <domain> (required) Domain name to add

wraps email domains list

List all domains configured in AWS SES with their verification and DKIM status.

Usage

terminal.sh

npx @wraps.dev/cli email domains list

wraps email domains get-dkim

Retrieve DKIM tokens for a domain to configure DNS records.

Usage

terminal.sh

npx @wraps.dev/cli email domains get-dkim -d <domain>

Options

-d, --domain <domain> (required) Domain name to get DKIM tokens for

wraps email domains verify

Check the DNS verification status of a domain, including DKIM, SPF, and DMARC records.

Usage

terminal.sh

npx @wraps.dev/cli email domains verify -d <domain>

What It Checks

SES domain verification status
DKIM DNS records (3 CNAME records)
SPF record (TXT record for sender verification)
DMARC record (TXT record for email authentication policy)
MAIL FROM MX records (if custom MAIL FROM configured)
Provides copy-paste ready DNS record values

wraps email domains remove

Remove a domain from AWS SES. This action cannot be undone.

Usage

terminal.sh

npx @wraps.dev/cli email domains remove -d <domain>

Options

-d, --domain <domain> (required) Domain name to remove
-f, --force Skip confirmation prompt

wraps email inbound

Deploy and manage inbound email receiving infrastructure. Receive emails at your domain, parse them automatically, and process with your application.

wraps email inbound init

Deploy inbound email receiving infrastructure to your AWS account.

Usage

terminal.sh

npx @wraps.dev/cli email inbound init [options]

Options

-d, --domain <domain> Domain to receive emails at
-r, --region <region> AWS region (must support SES inbound)

What It Deploys

S3 bucket for storing incoming emails
SES receipt rule set with active rule
Lambda function to parse and process emails
EventBridge rule for email.received events
IAM roles and policies for cross-service access

wraps email inbound status

Display the status of inbound email infrastructure, including MX records and receipt rules.

Usage

terminal.sh

npx @wraps.dev/cli email inbound status

wraps email inbound test

Send a test email to verify your inbound configuration is working correctly.

Usage

terminal.sh

npx @wraps.dev/cli email inbound test [options]

Options

Sends a test email to your configured inbound receiving domain. Accepts -r, --region and --json flags.

wraps email inbound verify

Check that DNS records for your inbound receiving domain(s) are correctly configured. Verifies MX records point to SES inbound SMTP and SPF records include amazonses.com. Also confirms the SES receipt rule set is active.

Usage

terminal.sh

npx @wraps.dev/cli email inbound verify [options]

Options

-r, --region <region> AWS region to check
--json Output result as JSON

What It Checks

MX record points to inbound-smtp.<region>.amazonaws.com
SPF TXT record includes amazonses.com
SES receipt rule set is active
Checks all configured inbound domains when multiple exist

wraps email inbound add

Add an additional receiving domain to your inbound email infrastructure. Requires inbound to already be deployed via wraps email inbound init. Updates the SES receipt rule and optionally auto-creates DNS records.

Usage

terminal.sh

npx @wraps.dev/cli email inbound add [options]

Options

-d, --domain <domain> Parent domain for the new inbound subdomain
--subdomain <name> Subdomain prefix (e.g., inbound, support)
--root Use root domain instead of a subdomain
-r, --region <region> AWS region (must support SES inbound)
-y, --yes Skip confirmation prompts

Examples

Add a support subdomain interactively:

terminal.sh

npx @wraps.dev/cli email inbound add

Add a specific subdomain non-interactively:

terminal.sh

npx @wraps.dev/cli email inbound add --domain yourdomain.com --subdomain support --yes

wraps email inbound remove

Remove an inbound receiving domain from SES receipt rules and metadata. Cannot remove the last domain — use wraps email inbound destroy to remove all inbound infrastructure instead.

Usage

terminal.sh

npx @wraps.dev/cli email inbound remove [options]

Options

-d, --domain <domain> The receiving domain to remove (e.g., support.yourdomain.com)
-r, --region <region> AWS region
-y, --yes Skip confirmation prompt

Important Notes

You must have at least two inbound domains to use this command
After removal, manually delete the MX and SPF DNS records for the removed domain

wraps email inbound destroy

Remove inbound email infrastructure. Stored emails in S3 will remain unless you delete the bucket manually.

Usage

terminal.sh

npx @wraps.dev/cli email inbound destroy [options]

Options

-f, --force Skip confirmation prompt

wraps email connect

Connect to existing AWS SES resources and add Wraps features non-destructively. Never modifies your existing SES setup.

Usage

terminal.sh

npx @wraps.dev/cli email connect [options]

Options

--region <region>

AWS region to scan for existing resources

--preview

Preview infrastructure changes without deploying

What It Does

Scans existing SES domains and configuration sets
Prompts for which features to add
Creates new resources with wraps- prefix
Never modifies or deletes existing resources
Configures event tracking and analytics

wraps email upgrade

Add additional features to your existing Wraps deployment. Upgrade from Starter to Production, or add individual features incrementally.

Usage

terminal.sh

npx @wraps.dev/cli email upgrade [options]

What It Does

Shows currently enabled features
Prompts for additional features to enable
Deploys new resources incrementally
Updates IAM policies with new permissions
Shows updated cost estimates

Example Upgrades

Starter → Production: Adds real-time event tracking and 90-day history
Production → Enterprise: Adds dedicated IP and 1-year history retention
Add individual features: Enable specific event types or extend storage

wraps email sync

Synchronize local state with deployed infrastructure. Useful after CLI updates or manual AWS console changes.

Usage

terminal.sh

npx @wraps.dev/cli email sync [options]

What It Does

Detects differences between local config and deployed infrastructure
Applies CLI updates (bug fixes, new features) to resources
Updates Lambda functions and IAM policies
Does not change your configuration preset or features

wraps email restore

Restore Wraps deployment from existing metadata. Useful if you've lost local configuration but infrastructure still exists in AWS.

Usage

terminal.sh

npx @wraps.dev/cli email restore [options]

What It Does

Scans AWS for existing Wraps resources
Reconstructs deployment metadata
Re-imports Pulumi stack state
Restores local configuration

wraps email destroy

Remove email infrastructure. Use this to remove only the email service while keeping other services intact.

Usage

terminal.sh

npx @wraps.dev/cli email destroy [options]

Options

-f, --force

Skip confirmation prompt (use with caution)

--preview

Preview what would be destroyed without making changes

What It Removes

Email-specific IAM roles and policies
DynamoDB tables (email history will be lost)
Lambda functions for event processing
EventBridge rules and SQS queues
Route53 DNS records (DKIM, DMARC, MAIL FROM) if confirmed
Local metadata for email service

wraps email doctor

Diagnose email infrastructure health by scanning your AWS account for all wraps-* resources and checking whether they are managed by a Pulumi stack or orphaned.

Usage

terminal.sh

npx @wraps.dev/cli email doctor [options]

Options

-r, --region <region>

AWS region to scan (auto-detected from metadata when omitted)

--cleanup

Interactively delete orphaned wraps-* resources that have no Pulumi stack. Prompts for confirmation before deleting. If a Pulumi stack exists, suggests using wraps email destroy or wraps email upgrade instead.

--json

Output result as JSON

What It Scans

SES configuration sets
SNS topics
DynamoDB tables
Lambda functions
IAM roles

Examples

Scan for issues:

terminal.sh

npx @wraps.dev/cli email doctor

Scan and clean up orphaned resources:

terminal.sh

npx @wraps.dev/cli email doctor --cleanup

wraps email test

Send a test email using the AWS SES mailbox simulator. Verify your email infrastructure is working without affecting your sender reputation.

Usage

terminal.sh

npx @wraps.dev/cli email test [options]

Options

--to <email>

Recipient email address (defaults to SES simulator address)

--scenario <type>

Simulator scenario: bounce, complaint, or success

--json

Output result as JSON

What It Does

Sends a test email via the AWS SES mailbox simulator
Shows the delivery result and message ID
Supports different scenarios to test bounce and complaint handling

wraps email check

Run a comprehensive deliverability audit on your domain. Checks all critical email authentication records and provides an overall deliverability score.

Usage

terminal.sh

npx @wraps.dev/cli email check [options]

Options

--domain <domain>

Domain to audit

-q, --quick

Quick mode: check fewer DKIM selectors and only top blacklists

--verbose

Show all checks including passing ones (e.g., full SPF lookup tree)

--dkimSelector <selector>

Check a specific DKIM selector instead of scanning common ones. If omitted and a Wraps deployment exists, SES DKIM tokens are used automatically.

--skipBlacklists

Skip all blacklist checks entirely

--skipTls

Skip MX server TLS (STARTTLS) checks

--timeout <ms>

DNS timeout in milliseconds

--json

Output result as JSON

What It Checks

DKIM records and signing configuration
SPF alignment and record validity
DMARC policy strength and configuration
MX record TLS support
Blacklist presence across major providers
Overall deliverability score with recommendations

wraps email templates

Manage email templates as code. Initialize a templates directory, preview with hot-reload, and push compiled templates to SES and the Wraps dashboard.

wraps email templates init

Initialize a templates-as-code directory with an example template, configuration file, and brand file.

Usage

terminal.sh

npx @wraps.dev/cli email templates init

wraps email templates preview

Start a local preview server with hot-reload for developing email templates. Defaults to port 3333.

Usage

terminal.sh

npx @wraps.dev/cli email templates preview

wraps email templates push

Compile and push templates to AWS SES and the Wraps dashboard.

Usage

terminal.sh

npx @wraps.dev/cli email templates push [options]

Options

--template <name> Push a specific template by name
--force Overwrite existing templates without confirmation
--dry-run Preview what would be pushed without making changes
--json Output result as JSON

wraps email workflows

Validate and push email workflow definitions to the Wraps Platform.

wraps email workflows validate

Validate workflow definitions against the Wraps workflow schema. Catches errors before pushing to production.

Usage

terminal.sh

npx @wraps.dev/cli email workflows validate

wraps email workflows push

Push workflow definitions to the Wraps Platform.

Usage

terminal.sh

npx @wraps.dev/cli email workflows push

wraps workflow init

Scaffold a workflows-as-code project with example workflow files and a configuration file. Creates a wraps/workflows/ directory in your current project with ready-to-edit examples.

Usage

terminal.sh

npx @wraps.dev/cli workflow init [options]

Options

-y, --yes

Overwrite existing example files without prompting

What It Creates

wraps/wraps.config.ts — Project configuration (org, from address, region)
wraps/workflows/cart-recovery.ts — Cross-channel cascade example (email then SMS)
wraps/workflows/welcome-sequence.ts — Welcome series with conditional branching

wraps email config

Apply CLI configuration updates to deployed infrastructure. Syncs local configuration changes with your deployed AWS resources.

Usage

terminal.sh

npx @wraps.dev/cli email config

What It Does

Reads local configuration and compares with deployed infrastructure
Applies any pending configuration changes to AWS resources
Updates IAM policies, Lambda functions, and EventBridge rules as needed

Back to CLI Reference CDN Commands