Existing inbox

Receive And Reply In The Inbox You Already Use

LiteMX forwards accepted mail to a verified destination such as Gmail, Fastmail, iCloud, or an account already open in Thunderbird. Reply there normally; the correspondent sees the custom-domain address, not your private destination.

Private-Build Availability

The forwarding and reverse-reply legs are deployed. The first production text-only round trip passed from a public correspondent, through the founder's existing inbox, and back to the correspondent from the custom address without exposing the private destination.

Self-serve destination verification is not available yet. Exact founder addresses on the server allowlist can be verified automatically; every other destination remains pending until LiteMX can deliver a one-time verification challenge. Request access before moving production mail.

Create The Address

addresses create composes domain registration, address creation, destination creation, mailbox binding, provider provisioning, and DNS planning. Add the returned records at the DNS provider you already use, then verify the domain.

create-address.sh

litemx addresses create support@project.dev --forward-to owner@example.com
litemx domains dns-plan project.dev
litemx domains verify project.dev --timeout 120 --interval 5

Verify The Destination

Forwarding is enabled only for a verified destination. Inspect both the destination and its mailbox binding; a pending destination may be bound, but it remains disabled.

inspect-forwarding.sh

litemx forwarding-destinations list
litemx mailboxes forwarding support@project.dev

Once a genuine one-time challenge has been delivered out of band, submit it and enable the binding. The API never returns raw verification or reverse-reply tokens.

enable-forwarding.sh

litemx forwarding-destinations verify <destination-id> --token <one-time-token>
litemx mailboxes forwarding support@project.dev \
  --destination <destination-id> --enable

Reply Normally

LiteMX stores accepted inbound mail before it queues the forwarded copy. That copy uses a signed, unguessable Reply-To address tied to the account, custom-domain address, verified destination, correspondent, source message, and thread.

Click Reply in your usual email client. LiteMX accepts the reply only through trusted mail ingress, then sends it to the original correspondent from the custom-domain address. New conversations remain CLI-, API-, or MCP-first during the private build.

inspect-conversation.sh

litemx messages list --mailbox support@project.dev
litemx threads list --mailbox support@project.dev
litemx audit list --mailbox support@project.dev

Why The Reply Address Is Safe

Reverse replies fail closed unless every check passes:

The message arrived through the authenticated AWS SES ingress path.
SES reports a DMARC verdict of PASS.
The sender exactly matches the verified destination bound to the address.
The destination and mailbox binding are still enabled.
The signed reply capability is valid, unexpired, unrevoked, and bound to the original thread.

LiteMX stores only the capability hash. Disabling the binding or deleting the destination revokes the related reply addresses.

Current Limitations

Arbitrary destination verification cannot complete until challenge delivery ships.
Inbound attachment bytes are stored by LiteMX but omitted from the forwarded copy.
A reverse reply containing an attachment is rejected instead of being relayed.
Two additional founder-domain dogfood passes remain before the three-domain acceptance gate is complete.

Use text- or HTML-only messages for private-build testing.

Disable Forwarding

Stop forwarding without deleting the address, or disable the destination and its reverse-reply aliases.

disable-forwarding.sh

litemx mailboxes forwarding support@project.dev --disable
litemx forwarding-destinations delete <destination-id>