Run Mail Hosting for your customers

Every Mail Hosting or SMTP Relay service a customer orders from your organization runs as a mail tenant: its own domains, mailboxes, credentials and sending reputation. The Email tab lists your tenants and shows which ones need attention. To work inside a tenant, your staff use the API on this page, which offers the same operations the customer has on their own service.

• Any member of the organization can open the Email tab and call the two list routes.
• Opening or changing a single tenant takes the owner, admin or support_tier3 role. Other roles get 403 Staff access required. Roles and permissions lists who holds which role.

1. Go to Organizations, open your organization and choose Email.
2. Read the four cards at the top:
   • Tenants counts every tenant that has not been terminated.
   • Sending frozen counts the tenants whose outgoing mail we have paused.
   • Domains pending counts the domains still waiting for their MX, SPF or DKIM records to verify.
   • Frozen share is the frozen tenants as a percentage of all tenants.
3. Read the Mail tenants table. Each row is one tenant:
   • Tenant shows its name, its kind and its domains.
   • Customer shows the customer who owns it.
   • Status shows where the service stands, with a Sending frozen or Under review badge when its reputation needs attention.
   • Reputation shows its sending tier with its bounce and complaint rates.
   • Usage shows its mailboxes against the plan's limit, its aliases and its storage.
   • Since shows the date the tenant was created.
4. To find a tenant, type part of a domain or a tenant ID in the search box, or narrow the list by kind. Choose Refresh to load the latest figures.

A tenant that we have flagged or frozen shows the reason under its row.

We check each tenant's bounce and complaint rates over a recent window of its sending:

• A tenant whose rates cross the review threshold is flagged, and the table shows Under review. It keeps sending.
• A tenant whose rates cross the freeze threshold stops sending, and the table shows Sending frozen. The note under the row gives the rates that caused it.
• Only Coritan can lift a freeze. Clean up the list the tenant sends to, add the addresses that bounced to its suppression list, then contact support.

The tier decides which pool of sending addresses carries the tenant's mail. New tenants start on probation; the other tiers are established and dedicated. Sending reputation and deliverability explains the thresholds and the tiers.

You know which tenants are frozen, under review or waiting on DNS records, and which customer owns each one.

403 Staff access required

Your role can read the tenant list but cannot open a tenant. Ask an owner or an admin to do the work, or to change your role.

404 Mail service not found in this organization

The tenant ID does not belong to this organization. Take the id from the tenant list.

A domain stays in Domains pending

Read the records the domain needs with GET .../domains/{domain_id}/records, publish them at the domain's DNS host, then call POST .../domains/{domain_id}/verify. Mail DNS records explains each record.

• How Mail Hosting works
• How SMTP Relay works
• Mail DNS records
• Customer services
• Let customers use Mail Hosting and SMTP Relay

Every call takes a member's access token as Authorization: Bearer $CORITAN_TOKEN.

curl "https://api.coritan.com/api/v1/orgs/acme/mail/tenants?kind=relay&q=example.com" \
  -H "Authorization: Bearer $CORITAN_TOKEN"

The answer is {"items": [...], "total": n}. Each item carries the tenant's id, kind, status, tier, bounce_rate_pct, complaint_rate_pct, sending_frozen, review_flag, reputation_note and plan limits, plus domains, the owning customer (id, email, name), the linked org_service (id, status, hostname) and counts of mailboxes, aliases, groups, relay credentials and domains.

GET /api/v1/orgs/acme/mail/overview answers the three counts behind the cards: tenants, sending_frozen and domains_pending.

Every route below starts with /api/v1/orgs/acme/mail/tenants/{tenant_id} and needs the owner, admin or support_tier3 role. GET on that path alone answers the tenant's summary.

POST /limits/increase-request exists on this path too, but it answers 400 for staff. A customer asks for a higher hourly limit from their own portal, and only Coritan can raise it; see Pass on a request for a higher limit.

A password reset with no password in the body sets a random password and returns it in the answer. For a mailbox it also turns off two-factor authentication and signs out every webmail session. For example, to add a mailbox:

curl -X POST "https://api.coritan.com/api/v1/orgs/acme/mail/tenants/42/mailboxes" \
  -H "Authorization: Bearer $CORITAN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"domain_id": 7, "local_part": "alex", "display_name": "Alex"}'

Each area behaves as it does for the customer, so the mail pages explain the details: mailboxes, aliases, moving mail in, SMTP credentials, suppressions and webhooks. The full request and response shapes are in the API reference.