TrekMail Sending Limits by Plan

To maintain high deliverability for everyone, TrekMail enforces the following daily sending limits.

Limits by Plan

• Mailbox Limit: The max emails a single user (e.g., alice@domain.com) can send in 24 hours.
• Account Limit: The total emails all your users combined can send.
• Recipients: The number of people on the "To" + "Cc" + "Bcc" line of a single email.

Safety Limits for New Accounts

To maintain deliverability for all users, new accounts that have not yet made a payment operate under reduced sending limits called Safety Limits. These apply to managed TrekMail SMTP only and are removed automatically once your first payment is processed.

Safety Limits During Trial

If you're on a paid plan trial and haven't completed a payment yet, these limits apply:

Safety Limits After Trial (Pre-Payment)

If your trial has expired or your first payment failed, these reduced limits apply:

Creating mailboxes and domains is not capped during the trial. Safety Limits apply to sending only — you can add mailboxes and domains up to your selected plan's limits before your first payment.

How to remove Safety Limits: Complete your first payment. Limits are upgraded automatically and immediately upon successful payment processing.

Note: Safety Limits only apply when using managed TrekMail SMTP. If a domain sends through a custom SMTP profile (your own provider), these sending restrictions do not apply.

SMTP Hourly Rate Limits

In addition to daily limits, TrekMail enforces per-account hourly caps on SMTP message submissions. This prevents any single account from overwhelming shared infrastructure.

• These limits apply to messages submitted via managed TrekMail SMTP only.
• If a domain uses a custom SMTP profile (your own provider), hourly limits are governed by that external provider.
• You will receive a warning email when you reach 80% of your hourly limit.
• Counters reset at the top of each hour.

Forwarded mail counts too

Mail that leaves TrekMail because you forwarded it is still mail we send for you, so it draws on the same allowances as anything sent from a mailbox. This covers both kinds of forwarding:

• Mailbox forwarding — a copy of a mailbox's mail sent on to another address.
• Forwarding addresses — mailbox-less addresses on your domain that deliver somewhere else.

Two details worth knowing:

• One message to several recipients counts several times. A forwarding address with three recipients uses three of your daily messages per incoming email, because three separate deliveries leave our servers.
• Spam blocked before forwarding is free. When our filters reject an incoming message, nothing is relayed and nothing is counted — inbound junk cannot eat the allowance of the person receiving it.

If an account passes its hourly rate, forwarding pauses on its own and resumes when the hour rolls over. Your addresses and recipients are untouched while it is paused, and the Routing tab shows a line saying when delivery resumes. Mail sent from a mailbox is deferred instead, as described below.

What happens if I hit the limit?

1. Daily Limit: You will receive a "Daily limit exceeded" error. You must wait for the 24-hour rolling window to reset.
2. Hourly SMTP Limit: Your mail client will receive a temporary deferral (4.7.1 Hourly sending limit reached). Messages are not rejected — simply retry after the hour resets.
3. Queueing: Webmail might try to queue the message, but desktop clients (Outlook) will simply fail to send.

Best practices

• Don't Spam: These limits are generous for business use. If you need to send 50,000 emails a day for marketing, use a dedicated marketing service (like Mailchimp or Brevo) instead of business email.
• Warm Up: Even if your plan allows 2,000 emails, don't send them all on Day 1. Start slow.

IMAP Connection Limits

In addition to sending limits, TrekMail enforces concurrent IMAP connection limits to maintain server performance.

• Per IP: Maximum simultaneous IMAP connections from a single IP address.
• Total: Maximum simultaneous IMAP connections across all your devices.

These limits apply to incoming mail connections (IMAP) and help ensure fair resource distribution. If you regularly exceed these limits, consider upgrading to a higher plan.

Custom SMTP Rules

If a domain sends through a custom SMTP profile (your own provider), these limits do not apply. That domain is subject only to the limits of your external provider (Amazon SES, SendGrid, etc.).

Connected accounts and Send As

The visible From address does not decide the limit; the selected sending route does:

For example, a Gmail inbox paired with sales@example.com can send the visible business address through managed TrekMail SMTP or through a saved custom profile. If no separate Send As identity is selected, the message leaves through Gmail and follows Google's limits.

API and MCP sending has an additional abuse-control layer regardless of delivery route: by default, 60 send requests per minute per message token and 100 API sends per day across one mailbox. A secondary token counter defaults to 500 per day, so the lower mailbox cap normally wins. These API counters do not increase the SMTP allowance; both the API safeguard and the selected delivery route must allow the send.

See Send As Addresses via API and MCP for the routing fields and Send From a Business Address Using Gmail for the webmail setup.