Sending policy
Shipmail limits sending in three places: a daily limit for the organization, an hourly and daily cap on each mailbox, and a monthly quota of mailbox emails for the organization. The dashboard, API, and authenticated SMTP all apply them, with the differences noted below.
Last updated
Why these limits exist
Every Shipmail mailbox sends through shared infrastructure, so one account that sends spam lowers inbox placement for every customer. The limits stop that before Gmail and Outlook notice it: a free trial cannot send a large burst, and a mailbox cannot mail a purchased list in one hour. Normal business email stays well under them.
Large providers limit sending too. Google Workspace, for example, allows a user 2,000 messages and 3,000 external recipients a day. For cold outreach, use a dedicated outreach tool. For a newsletter, use Newsletters, which has its own monthly quota.
Daily limit
Limits count recipients, not messages. Every To, Cc and Bcc address counts, so a message to 3 people uses 3. The day is UTC and resets at midnight.
During the free trial, your organization can send to 100 recipients a day. This one limit covers everything: the app, scheduled sends, the API, the assistant, mail apps connected over SMTP, and transactional senders. There is no monthly total for these sends during the trial. To send more, end your trial in Settings > Billing. Newsletters keep their own trial limits.
Once you pay, your plan's daily limit applies from the first day. It is your monthly quota divided by 30, rounded up: 667 a day on Solo, 1,334 on Pro and 4,000 on Team. On Scale it is 334 a day for each mailbox. Past the limit, a send is refused with a message that gives your count, and a mail app gets a temporary error. There is no warm-up period to wait through.
On a paid plan, outside a trial, email from a transactional sender does not use the daily limit above. It has its own safety limit, which grows with clean sending.
Newsletter domain warm-up
A newsletter sending domain warms up, starting on the day it is verified. Every newsletter sent from that domain counts toward one limit over the last 24 hours. When a newsletter reaches the limit, it keeps its sending status and waits. The rest goes out as the 24-hour window frees up, with no action from you. The schedule dialog shows how many days a large newsletter will take.
| Domain age | Newsletter emails |
|---|---|
| Day 1 to 3 | 500 / 24 hours |
| Day 4 to 7 | 2,000 / 24 hours |
| Day 8 to 14 | 5,000 / 24 hours |
| Day 15+ | No warm-up limit |
The table gives the lowest limit. When the 24 hours before had under 2% bounces and under 0.1% spam complaints, the limit becomes twice what went out in them, so a domain with clean results passes the table quickly. While the limit holds a newsletter back, the readers who opened, clicked or replied most recently go first.
A domain skips the warm-up when the public domain registry shows its root domain was registered at least 30 days earlier and your organization runs Shipmail mailboxes on that root domain. Shipmail checks when the sending domain is verified, and again at a later send if the registry did not answer. Readers who never got an email from you still go out in two steps.
Per-mailbox rate limits
Each mailbox has its own limit, whatever your plan quota:
- 500 unique recipients an hour.
- 2,000 unique recipients a day.
For the dashboard and the API, the hour and the day are UTC: the hourly count resets at the start of each hour, and the daily count at midnight. Authenticated SMTP counts over the last hour and the last 24 hours instead. Sending again to a recipient already counted does not add to either count, and newsletter recipients do not count. If you hit a limit, wait before retrying.
You can run deliverability tests such as EasyDMARC, GlockApps or mail-tester. Shipmail does not treat a test sent to their seed list as spam. A seed list of up to 100 addresses fits in one mailbox's limit. For a larger one, send the rest later or from a second mailbox.
Monthly quota
Your plan sets how many mailbox emails your organization can send per billing cycle. All mailboxes in the organization share this quota. Newsletters and transactional email are counted apart. An organization created before these prices were published keeps its current rule until its owner allows extra sending: transactional email shares the plan's monthly sends.
| Plan | Mailbox emails a month | Daily limit |
|---|---|---|
| Solo | 20,000 / mo | 667 / day |
| Pro | 40,000 / mo | 1,334 / day |
| Team | 120,000 / mo | 4,000 / day |
| Scale | 10,000 per mailbox / mo | 334 per mailbox / day |
The Scale plan covers 13 to 300 mailboxes and its quota grows with the number of mailboxes you run. Past 300 mailboxes, email hi@shipmail.to.
Delivery and retries
Shipmail stores every message in a queue before delivery. If the receiving server is down or answers with a temporary error, Shipmail retries. A message that still fails when the retries run out bounces.
- Temporary failures are retried. Greylisting, a full mailbox and rate limits are temporary.
- Hard bounces are permanent and are not retried. The address is added to your suppression list.
- An address that soft-bounces 3 times in 14 days because its mailbox is full or its server keeps failing is paused for 30 days.
- An address that marks your email as spam is added to your suppression list too.
- When Gmail refuses an email as likely unsolicited, the address is not suppressed. The address works, and the refusal is about the email. A refusal reported as a permanent failure still counts toward your bounce rate.
When an email you sent from a mailbox hard-bounces, Shipmail puts a short notice in that mailbox's Inbox, in the same conversation. It names the address, gives the reason and links to your suppression list. Email sent through the API reports bounces through webhooks instead.
A message starts as sent, then becomes delivered, bounced or complained. While a receiving server defers it, you get a message.delayed webhook that says when retries stop. See webhooks for every delivery event and its payload.
Shipmail adds no tracking pixels and rewrites no links in regular or API email. Each newsletter can turn on open and click stats.
Bounce and complaint monitoring
Shipmail looks at the last 7 days of your organization's sending, counted per recipient. The bounce rate is the share of recipients whose address no longer exists or refused your email for good. The complaint rate is the share of recipients who reported your email as spam. A message to 3 people counts as 3 recipients.
A few failed recipients change nothing: each one is added to your suppression list and your sending stays as it is. Both a minimum number and a rate must be reached in the same 7 days before Shipmail acts, so 25 failed recipients out of 1,000 (2.5%) do not slow down your sending.
| Status | Bounces | Complaints |
|---|---|---|
| Slowed down | At least 25 failed recipients and 5% or more | At least 3 complaints and 0.1% or more |
| Paused | At least 50 failed recipients and 10% or more, or at least 25 and 20% or more | At least 5 complaints and 0.3% or more |
For organizations up to 7 days old, complaints act sooner: sending is slowed down at 2 complaints and paused at 4, at the same rates.
Gmail also reports a spam rate through Postmaster Tools once it sees enough of your email. Shipmail reads it every day and treats it like a complaint rate: sending is slowed down at 0.1% and paused at 0.3%.
When sending is slowed down, your daily limit is halved and newsletters stop. Mail apps connected over SMTP get a temporary error once the smaller limit is reached. Shipmail checks your rates again every 4 hours, and the slow-down lifts by itself once your bounce rate is under 4% and complaints are back under their rule. Clearing your suppression list does not lift it.
When sending is paused, no email goes out until a person at Shipmail turns it back on. Incoming mail keeps working.
If sending is slowed down a second time within 7 days, Shipmail treats it as a sender that kept mailing the same list. During a free trial, sending is paused at once. On a paid plan, sending is not paused automatically: Shipmail's team reviews the account.
Shipmail emails organization owners only when sending changes: when it is slowed down, when it is paused, and when it is back to normal. Owners also get a notification in the app and on their phone.
Suppression list
When an email hard-bounces or a recipient complains, Shipmail adds the address to your organization's suppression list. Any later send to that address is rejected with a 422 recipient_suppressed error. A transactional sender can also refuse temporary email addresses, with a 422 recipient_disposable error.
- A complaint about a newsletter stops newsletters only. Receipts, password resets, replies and other email still reach that person. A complaint about any other email stops everything.
- Hard bounces stop everything, permanently.
- Repeated soft bounces pause an address for 30 days, and sending resumes on its own. If the address keeps soft-bouncing after the pause, the second pause is permanent.
When you send from a mail app such as Outlook or Apple Mail, Shipmail skips a suppressed address and delivers to your other recipients. A notice in your Inbox names the address it skipped. If every recipient is suppressed, the message is refused.
Organization Owners and Admins with access to all mailboxes can view and manage suppressed addresses from Analytics > Suppressions, which shows what each entry blocks and when a pause ends. To remove several at once, tick their selection circles and choose Remove. A newsletter opt-out is never removed this way. You can also manage them through the API:
GET /api/v1/suppressionslists all suppressed addresses with the reason, scope, expiry and timestamp.POST /api/v1/suppressionsadds an address, blocking every send or newsletters only.DELETE /api/v1/suppressions/{email}removes an address from the suppression list so you can send to it again.POST /api/v1/suppressions/batch-removeremoves up to 500 addresses at once and reports what happened to each.
Remove a suppression only when you know the address works and the recipient wants your email. Sending again to an address that bounced or complained raises your bounce and complaint rates.
Never-email list
Some addresses cannot receive a newsletter from anyone, so Shipmail keeps one list of them for every organization. When a newsletter bounces because the address does not exist, the address is listed for 180 days. When it bounces because the address is a spam trap, it is listed until we remove it. The list blocks newsletters only. Replies, receipts and other mailbox mail still go out. It stores a keyed hash of each address, not the address itself.
A listed address is refused when it is imported or signs up, and each newsletter send skips it. Its status in your audience does not change. A newsletter that reaches a spam trap pauses every newsletter your organization is sending or has scheduled, and a person reviews the account. If you believe an address is listed by mistake, contact support.
Content restrictions
Shipmail checks outgoing messages for two common spam patterns:
- Subject line. Subjects longer than 10 characters that are mostly uppercase get a warning before you send. The message still goes out. Rewrite the subject in sentence case to clear the warning.
- Link density. A single message may contain at most 20 unique URLs. Cut some links, or point them to one landing page. Newsletter sends run a preflight check that fails on too many clickable destinations and warns on a high number of remote resources.
Suspension and recovery
If sending is paused because of bounces or complaints, or for a second slow-down within 7 days during a free trial, no email goes out until a person turns it back on. Incoming mail and stored messages remain available. There is no automatic recovery. Reply to the email Shipmail sent you, or contact support@shipmail.to, with the steps you have taken to fix the cause, such as removing the addresses that bounced or complained. A person reviews the account and turns sending back on. The Terms list what use is prohibited. Depending on severity, Shipmail may suspend or terminate an account with or without prior notice.
Best practices
- Clean your list. Remove addresses that have bounced. Check your suppression list regularly.
- Authenticate your domain. Verify SPF, DKIM, and DMARC records in the dashboard before sending.
- Start gradually. Shipmail does not enforce a warm-up, but mailbox providers trust a new sender more when its volume grows over a few weeks. Don't send your full volume on day one.
- Monitor your analytics. Watch bounce and complaint rates in the dashboard, and set up webhooks to hear about bounces as they happen.