Request a higher hourly limit

Every SMTP Relay service has an hourly limit that rises by itself as the relay sends clean mail, up to a ceiling its plan sets (How the limit rises). When you need more before the daily review gets there, or more than the ceiling, ask for it. The request opens a support conversation, and our staff set the new limit when they grant it.

• You need an SMTP Relay service. Mail Hosting has no request form.
• Ask for a limit higher than the relay's current one, and at most 1,000,000 emails an hour.
• You can send one request a day for each relay. A second request on the same day (UTC) opens no new conversation.
• Have the numbers ready: what the relay sends, and the rate you expect at the busiest time.

1. In the dashboard, go to Email and open the relay.
2. On the Overview tab, find the Hourly limit card and select Request limit increase….
3. In Emails per hour, enter the limit you need. The field starts at the next step up from the current limit.
4. In What the relay sends and why the volume is going up, describe the mail and the reason for more, such as a launch or a seasonal peak, with the rate you expect at peak.
5. Select Send request.

A toast says Requested; limit increases are reviewed within a few business hours. Under Support, a new conversation called Hourly sending limit increase for SMTP relay #4812 holds the number you asked for and your reason. It also holds the figures our staff review: the plan's monthly emails, how many emails the relay has sent this month, and its recent sent count, bounce rate and complaint rate.

We reply in that conversation. When we grant the request, the Hourly limit card shows the new Current limit, and Set reads Set by support. The new limit reaches the mail servers within the hour.

From there, the daily review can still raise the limit one step at a time, up to the plan's ceiling. A limit our staff set can be reset like any other when the relay's rates rise (How the limit rises).

Send request stays off

The number in Emails per hour is not higher than the current limit, which the dialog states.

The relay may already send 250 an hour

The number is not higher than the current limit. Enter a larger one.

Request limit increase… is off

The relay is one of the platform's internal tenants, whose limits only our staff set. See Internal mail tenants.

No new conversation appears

The relay already has a request today. The first conversation keeps its number and reason, so reply in it to change them.

Could not send the request

The request failed, and the message after the title says why.

• How SMTP Relay sending limits work
• Sending reputation and deliverability
• Support conversations
• POST /client/smtp-relay/{service_id}/limits/increase-request in the API reference

curl -X POST https://api.coritan.com/api/v1/client/smtp-relay/4812/limits/increase-request \
  -H "Authorization: Bearer $CORITAN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"requested_per_hour": 1000, "reason": "Order confirmations for a shop launching on 1 October, about 800 an hour at peak"}'

requested_per_hour

Required. The limit you ask for, 10–1,000,000 emails an hour, and higher than the current limit.

reason

Optional, up to 2,000 characters. What the relay sends and why the volume is going up.

The answer is 201:

{
  "ok": true,
  "conversation_id": 7731,
  "current_per_hour": 250,
  "requested_per_hour": 1000,
  "message": "Requested; limit increases are reviewed within a few business hours"
}

conversation_id is the support conversation. Follow it with GET /chat/conversations/{conversation_id}, and reply with POST /chat/conversations/{conversation_id}/messages. A second request on the same day (UTC) answers with the first request's conversation_id, and that conversation keeps its first number and reason.

To see the new limit once we grant it, read limits.rate_per_hour from the usage report.

The same operation is under /client/mail/{service_id}/limits/increase-request, which answers the same way for a relay.