Sending Policy

LiteMX is for ordinary mailbox email across many domains: new one-to-one messages, replies, forwards, support conversations, transactional messages, billing/account communication, and agent-composed mail when the account grants explicit send scope.

Permission-based marketing is an eventual explicit broadcast mode, not part of the current correspondence workflow. LiteMX is not a list-warming, lead-generation, spam, or cold-outreach 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:

• New one-to-one business or personal messages from a verified mailbox.
• 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-composed messages and replies where the user or scoped token explicitly permits sending.
• Permission-based marketing only after broadcast mode, consent, opt-out, suppression, metering, and isolated routing are enabled.

LiteMX may block or suspend sending for:

• Cold outbound campaigns.
• Purchased, scraped, rented, generated, guessed, appended, or harvested recipient lists.
• Marketing without documented permission or outside the future broadcast mode.
• 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 may require account approval or written permission for downstream customer sending. That is separate from verifying a domain. LiteMX keeps provider adapters separate so live inbound can continue while a verified domain is assigned to another permitted outbound route.

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.