# LiteMX Sending Policy

LiteMX is for human-scale mailbox email across many domains. It is not a bulk sender, newsletter platform, marketing automation product, or cold outbound tool.

## Plan Limits

| Plan | Per mailbox/day | Per account/day | Per account/month | Recipients/message |
| --- | ---: | ---: | ---: | ---: |
| Free | 100 | 100 | 500 | 10 |
| Starter | 300 | 300 | 3,000 | 10 |
| Scale | 1,000 | 1,000 | 15,000 | 10 |

## Allowed Sending

Allowed examples:

- Replies from a mailbox to people who contacted that mailbox.
- Account, domain, billing, and operational notifications.
- Low-volume support and customer conversations.
- Agent-drafted replies where the user or scoped token explicitly permits sending.

Not allowed:

- Cold outbound campaigns.
- Purchased, scraped, rented, or harvested recipient lists.
- Newsletters or marketing blasts.
- Lead generation automation.
- Sending that attempts to evade provider limits or complaint handling.

## Abuse Controls

LiteMX should enforce verified sender domains, explicit send scopes, recipient caps, daily and monthly send caps, mailbox-level caps, audit logs, provider bounce/complaint suppression, and fast disablement for abusive domains, mailboxes, tokens, or accounts.

Related policy pages: [anti-spam](/anti-spam), [acceptable use](/acceptable-use), [abuse reporting](/abuse), and [bounce/complaint handling](/bounce-complaint-handling).

## Provider Reality

Low-cost outbound providers can require production sending approval. That approval is separate from verifying a domain and separate from having a valid cloud account. If a provider keeps an account in sandbox or denies production sending, LiteMX can still receive mail, but public-internet outbound remains blocked until the provider approves production access or the account uses another approved outbound provider.

Running LiteMX on Vercel does not replace a mail provider. Vercel is suitable for web apps and API calls to an email provider; it is not an SMTP reputation stack with stable MX/SMTP service, reverse DNS, IP warmup, bounce/complaint processing, and mail queue operations.