# Account limits

The sending, receiving, storage, and mailbox limits on every OpenEmail plan, how a new account is vetted, and what happens when you reach one.

Every OpenEmail account has limits on how much mail it sends, receives, and
forwards, how large a message can be, how much it stores, and how many
mailboxes it creates. This page lists them for each plan and explains how a
limit shows up in the API.

## New accounts

Every account starts as a new account, on Free and Pro alike. New accounts run
on the lower limits in the **New accounts** column below until we review them:
a person on our team reads what you intend to use OpenEmail for. That review,
called vetting, is how we keep the platform's sending reputation healthy for
everyone on it. Once your account is vetted, it moves to its plan's full limits.

Paying for Pro does not skip the review. Until a Pro account is vetted, it runs
on new-account limits like any other, and Pro's limits switch on once it is.

### Request vetting

Ask for the review on the **Request vetting** page of the app, at
[app.open.email/billing/vetting](https://app.open.email/billing/vetting). The
app links to it while your account is new, and so does every limit email a new
account gets. Any member of your organization can send the request.

The form asks four things:

- What you will send, and to whom.
- Your website or company (optional).
- How many messages you expect to send a month.
- How your recipients agree to get your mail.

What happens next:

1. We email you a copy of the request. Until it is reviewed, your account keeps
   working on new-account limits, and the page says the request is waiting.
2. A person reviews it.
3. We email the account's owner the decision, and the page shows it too.
   - **Approved:** the account runs on its plan's full limits at once.
     **Activity › Limits** in the app lists them.
   - **Not approved:** the email gives the reason. The account keeps
     new-account limits, and you can ask again from the same page, saying more
     about what you send and to whom.

### Verified recipients

A new account can send and forward mail only to verified recipients. A
verified recipient is either:

- an address on one of your account's own domains, which needs no
  confirmation, or
- an outside address whose owner confirmed it by clicking the link in the
  email we send them.

Add recipients in the console or through the API. A recipient you verify
counts for every domain and mailbox in your account. Once your account is
vetted, you can send and forward to anyone.

## How limits apply by plan

- **Free** limits are hard ceilings. Usage pricing does not apply, so reaching
  one means waiting for the window to reset or upgrading to Pro.
- **Pro** limits are defaults. Usage past what Pro includes is billed at the
  rates on the [pricing page](/pricing), up to these limits, and we can raise
  them per account. Pro send limits in particular are adjusted after signup as
  an account builds a sending history.

A day limit is measured over a rolling 24-hour window, not a calendar day.

You can see each of your account's limits and what it has used in the
console, under **Activity › Limits**, including any limit set for your
account.

## Sends

Counted in messages.

| Period | New accounts | Free | Pro |
| --- | --- | --- | --- |
| Per hour | 5 | 10 | 200 |
| Per day | 50 | 100 | 2,000 |
| Per month | 500 | 1,000 | 20,000 |

## Send recipients

Counted across every recipient of a send, so one message to 10 people uses 10.

| Period | New accounts | Free | Pro |
| --- | --- | --- | --- |
| Per hour | 25 | 50 | 1,000 |
| Per day | 250 | 500 | 10,000 |
| Per month | 2,500 | 5,000 | 100,000 |
| Per message | 20 | 50 | 100 |

## Receives

| Period | New accounts | Free | Pro |
| --- | --- | --- | --- |
| Per hour | 50 | 50 | 1,000 |
| Per day | 500 | 500 | 10,000 |
| Per month | 5,000 | 5,000 | 100,000 |

## Forwards

| Period | New accounts | Free | Pro |
| --- | --- | --- | --- |
| Per hour | 10 | 10 | 200 |
| Per day | 100 | 100 | 2,000 |
| Per month | 1,000 | 1,000 | 20,000 |

## Message size

Attachments count toward the size.

| | New accounts | Free | Pro |
| --- | --- | --- | --- |
| Send | 25 MiB | 25 MiB | 25 MiB |
| Receive | 25 MiB | 25 MiB | 25 MiB |
| Forward | 25 MiB | 25 MiB | 25 MiB |

## Storage

| | New accounts | Free | Pro |
| --- | --- | --- | --- |
| Hosted storage | 3 GB | 3 GB | Unlimited |

Pro includes 30 GB. Storage past that is billed at the usage rate rather than
refused.

## Mailboxes

| | New accounts | Free | Pro |
| --- | --- | --- | --- |
| Mailboxes | 3 | Unlimited | Unlimited |
| Mailboxes created per day | 3 | 50 | 5,000 |

The mailbox count is per account, across all of its domains.

## What is not limited

**API requests are not rate limited** for vetted accounts on either plan. What
an account can do is bounded by the limits on this page.

**IMAP, JMAP, POP3, and webmail have no limits of their own.** They go through
the same counters as the API, so a message sent over any of them counts toward
the same send limits, and nothing else is counted.

Creating mailboxes in bulk is the one case where a high request rate does meet a
limit, because each mailbox counts toward **Mailboxes created per day**. If you
plan to create more than 5,000 a day, [email us](mailto:support@open.email) and we
will work with you to find a limit that meets your requirements.

## When you reach a limit

A rate limit is temporary. Each one says when it clears, so nothing has to be
guessed.

- **Sending over a rate limit** answers `429` with `rate_limited`, a
  `Retry-After` header, and `retryAfterSeconds` in the body. Retry after that
  delay with the same `X-Delivery-Id`, as described in
  [Sending](/docs/guides/sending), and recipients that already received the
  message are not sent it again.
- **A message with more recipients than the per-message limit** answers `403`
  with `too_many_recipients`. This one does not clear with time: split the
  recipients across several sends.
- **Sending to a recipient who is not verified**, from a new account, answers
  `403` with `recipient_not_verified` for that recipient. The message still
  goes to the other recipients of the same send. Verify the address, then send
  to it again.
- **A message over 25 MiB** answers `413`.
- **Receiving or forwarding over a limit** defers the message rather than
  bouncing it. The sending server is told to try again later, and the mail
  arrives once the window has room.
- **Forwarding to a recipient who is not verified**, from a new account, does
  not forward the message to that recipient. Verify the address to start
  forwarding to it.
- **A full mailbox or account** answers `507` with `over_quota` (the mailbox's
  own quota) or `account_over_quota` (the account's storage). Incoming mail is
  deferred, not bounced. An immediate send still goes out; only its Sent copy
  is skipped, reported as `sentCopy: "over_quota"`.
- **Creating mailboxes past the daily limit** answers `429` with
  `rate_limited`.

## Checking usage

Paths are relative to `https://api.open.email/api/v1`, and every request carries
a bearer credential. See [Authentication](/docs/guides/authentication).

- [`GET /accounts/{accountId}/send-usage`](/docs/api/accounts/get_AccountSendUsageGet)
  returns the account's sends, recipients, and mailbox creations over the last
  24 hours.
- [`GET /accounts/{accountId}/receive-usage`](/docs/api/accounts/get_AccountReceiveUsageGet)
  returns the account's received mail over the last 24 hours.
- [`GET /accounts/{accountId}/storage-usage`](/docs/api/accounts/get_AccountStorageUsageGet)
  returns stored bytes across every mailbox against the account's quota.
- [`GET /mailboxes/{mailboxId}/send-usage`](/docs/api/mailboxes/get_SendUsageGet)
  returns one mailbox's send usage and its limits.
- [`GET /domains/{domain}/forward-usage`](/docs/api/domains/get_DomainForwardUsageGet)
  returns a domain's forwarding usage.

## Raising a limit

Need higher limits on Pro? Email
[support@open.email](mailto:support@open.email) with your requirements and we will
work with you to find a plan that fits your needs.
