TrekMail Sending Limits by Plan

TrekMail uses plan limits and safety checks to protect delivery quality. A recipient counts toward a sending allowance, so one message sent to three people uses three recipient sends. The dashboard and a domain's SMTP tab show the limits that currently apply to your account.

Base plan limits

Nano does not include Managed TrekMail SMTP. A Nano domain needs a working custom SMTP profile to send. The external provider can have its own limits as well as the TrekMail safeguards described here.

Safety limits before the first paid charge

Accounts that have not completed a paid mail-plan charge can receive lower safety limits. These values help protect a new account while it is being set up.

When the mail subscription becomes active after the first successful charge, the never-paid safety limits are removed. A new domain can still be in its own warm-up period, so do not assume that payment makes a new domain immediately eligible for the base maximum. See Domain Warm-Up Rules.

New-domain warm-up

For the first seven days after a domain is created, TrekMail reduces rate-based limits for that domain:

Warm-up affects the daily and hourly rate limits, not the recipient count in one message. Start with expected recipients and increase volume gradually. The safest approach is to send only mail your recipients expect, monitor bounces and complaints, and investigate unexpected delivery changes before increasing volume.

What counts toward the allowance

The relevant limit depends on the sending route and the number of recipients.

• A message with several To, Cc, or Bcc recipients counts once for each recipient.
• Mail submitted from a mailbox is checked against the mailbox, domain, and account allowances.
• Forwarded messages that leave TrekMail use the account's sending budget. A forwarding burst can pause forwarding until the applicable time window ends.
• A custom SMTP profile adds the external provider's rules; it does not remove TrekMail's sender, account, safety, or rate checks.
• API and MCP sends must pass their own request safeguards as well as the selected sending route and these applicable limits.

For API and MCP automation, one message token allows 60 send requests per minute and up to 500 sends per day, while one mailbox allows 100 API sends per day by default. The lower mailbox cap normally applies first. These safeguards sit on top of the plan, domain, account, and external-provider limits; they do not replace them.

If you use forwarding for high-volume mail, review the Forwarding Addresses guide and test with a small group first.

What happens at a limit

When a daily or hourly limit is reached, TrekMail temporarily defers new sending rather than treating the problem as a permanent recipient failure. The message or mail app can show a temporary SMTP error. Wait for the limit window to renew, reduce the send size, and retry only when the dashboard or mail app indicates that sending is available again.

If the failure continues after the displayed limit has renewed, it may be a different problem such as an inactive domain, an unverified account email, a missing SMTP route, a billing issue, or a mailbox-specific security suspension. Follow Fixing Common Email Sending Errors.

IMAP connection limits

These are connection limits, not sending limits. They control simultaneous IMAP connections for one mailbox.

If a mail app repeatedly opens too many connections, reduce its sync frequency or remove an unused device before adding more connections.

Plan a send safely

1. Check the current limit in the dashboard and SMTP tab.
2. Count recipients, not just messages.
3. For a new domain, use the warm-up percentage rather than the headline plan limit.
4. Start with a small, expected audience and inspect delivery results.
5. Use a dedicated consent-based marketing service for campaigns that exceed normal business correspondence.