Sending Policy

LiteMX is for human-scale mailbox email across many domains: replies, support conversations, operational messages, billing/account communication, and agent-drafted replies when the account grants explicit send scope.

LiteMX is not a bulk sender, newsletter platform, marketing automation product, lead-generation sender, list-warming tool, or cold outbound platform.

Outbound limits protect recipients, customer domains, sender reputation, and unit economics.

• Free: 100 sends per day, 500 sends per month, 10 recipients per message.
• Starter: 300 sends per day, 3,000 sends per month, 10 recipients per message.
• Scale: 1,000 sends per day, 15,000 sends per month, 10 recipients per message.

Mailbox-level safety caps also apply so one mailbox cannot consume the whole account or create abuse spikes.

Allowed sending generally includes:

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

LiteMX may block or suspend sending for:

• Cold outbound campaigns.
• Purchased, scraped, rented, generated, guessed, appended, or harvested recipient lists.
• Newsletters, marketing blasts, affiliate campaigns, or lead-generation automation.
• Sending that attempts to evade provider limits, suppressions, complaints, unsubscribe requests, or review.
• Phishing, malware, credential theft, deceptive impersonation, or misleading sender identity.

LiteMX uses or plans to use these controls before broad public launch:

• Verified sender domains before outbound sending.
• Explicit `email:send` scope for API and MCP sends.
• Per-message recipient limits.
• Daily and monthly account limits.
• Mailbox-level send caps.
• Audit logs for send attempts, blocked sends, and successful sends.
• Provider bounce and complaint suppression.
• Fast disablement for abusive domains, mailboxes, tokens, or accounts.

Low-cost outbound providers such as AWS SES 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.

For normal support, contact support@litemx.com. For spam, phishing, malware, impersonation, or sender abuse, contact abuse@litemx.com.