# Change Mail Hosting settings

> Set the default category for the mail your mailboxes send, set or hold each domain's DMARC stage, and remove a domain from the Settings tab.

Source: https://www.coritan.com/docs/mail/mail-hosting/settings/

In the dashboard:

- /dashboard/mail/…/settings: https://www.coritan.com/dashboard/mail

The **Settings** tab of a Mail Hosting service holds the choices that apply across the service: the **Sending defaults**, the **DMARC** stage of each domain, and the **Danger zone**, where you remove a domain. To cancel the service itself, see [How Mail Hosting and SMTP Relay are billed](/docs/mail/billing/).

## Before you begin

- A Mail Hosting service. The DMARC and **Danger zone** cards appear once the service has a domain.
- For DMARC, read [How the DMARC stage ramp works](/docs/mail/dmarc/) first: it explains what each stage asks of receiving servers.

## Set the default message category

Every message your mailboxes send has a *category*: *transactional* or *marketing*. A message takes its category from its `X-Mail-Category` header, and one without the header takes the service's default. Most mailboxes send person-to-person mail, which is transactional, so keep the default at **Transactional** unless the service's mailboxes send newsletters.

1. In the dashboard, go to [**Email**](https://www.coritan.com/dashboard/mail), open the Mail Hosting service, then the **Settings** tab.
2. In the **Sending defaults** card, choose a **Default message category**.

The toast confirms the new default, such as `Default category is now marketing.` It applies to the next message a mailbox sends.

When a marketing message has exactly one recipient and no `List-Unsubscribe` header of its own, we add the one-click unsubscribe headers that Gmail and Yahoo require on bulk mail. A message to several recipients is left as it is. See [Transactional and marketing mail](/docs/mail/smtp-relay/message-categories/).

> [!IMPORTANT]
> A person who unsubscribes goes on the service's suppression list, and from then on the mail server refuses mail to them from every mailbox on the service. Mail Hosting has no tab for that list, so taking someone off it needs the API. See [Manage the suppression list](/docs/mail/smtp-relay/suppressions/#with-the-api).

## Set or hold a domain's DMARC stage

A domain's DMARC stage starts at `p=none` and moves up by itself as the reports show your mail passes. The **DMARC** card lists each domain with its current stage, how long it has been there, and whether it is **held** or **ramps automatically**.

1. On the **Settings** tab, find the domain in the **DMARC** card.
2. To set a stage now, choose `p=none`, `p=quarantine` or `p=reject` in the list beside it. Choosing a stage also holds it there.
3. To stop the stage moving without changing it, turn on **Hold stage**. To let it move up again, turn **Hold stage** off.

The toast confirms the change, such as `DMARC for example.com set to p=quarantine.` When we publish the domain's records in a DNS zone we host, we update the DMARC record for you. When the zone is elsewhere, the domain's page shows the new record for you to publish; until you do, the domain's DMARC check fails. **Records and verification** opens the **Domains** tab.

## Remove a domain

> [!WARNING]
> Removing a domain stops all mail to and from its addresses, and deletes the records we published for it in a DNS zone we host. You cannot remove a domain that still has mailboxes or aliases, so this never deletes stored mail.

1. Delete the domain's mailboxes and aliases first. See [Create and manage mailboxes](/docs/mail/mail-hosting/mailboxes/#delete-a-mailbox) and [Forward addresses with aliases](/docs/mail/mail-hosting/aliases/#delete-an-alias).
2. On the **Settings** tab, in the **Danger zone** card, select **Remove domain…** beside the domain.
3. Type the domain name to confirm, then select **Remove domain**.

The domain leaves the service, and its place on the plan is free again. Remove the records you published yourself in a zone elsewhere.

## Troubleshooting

`The DMARC record for example.com in your DNS was not added by us. Change its p= value in the zone instead.`
: The domain's zone is hosted here, but its DMARC record was there before we published ours, so we left it alone. Edit that record's `p=` value in the zone.

`Remove the mailboxes and aliases on this domain first`
: The domain still has at least one mailbox or alias. Delete them, then remove the domain.

The stage moved up while the domain's DMARC check shows a problem
: The zone is elsewhere, and the ramp moved the stage without the new record being published. Open the domain on the **Domains** tab and publish the DMARC record it shows, or choose the stage your zone publishes to hold it there.

## Related

- [How the DMARC stage ramp works](/docs/mail/dmarc/)
- [Add a domain to Mail Hosting](/docs/mail/mail-hosting/add-a-domain/)
- [Transactional and marketing mail](/docs/mail/smtp-relay/message-categories/)

## With the API

Set the service's default category:

```bash
curl -X PATCH https://api.coritan.com/api/v1/client/mail/4812/category \
  -H "Authorization: Bearer $CORITAN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"default_category": "transactional"}'
```

`default_category` is `transactional` or `marketing`; any other value answers `422`. The answer is the new default:

```json
{"default_category": "transactional"}
```

`GET /client/mail/{service_id}` returns it as `default_category`. To set a domain's DMARC stage, see [How the DMARC stage ramp works](/docs/mail/dmarc/#with-the-api); to remove a domain, see [Add a domain to Mail Hosting](/docs/mail/mail-hosting/add-a-domain/#with-the-api).

## API

- `PATCH /api/v1/client/mail/{service_id}/category`: Set category (https://www.coritan.com/docs/api/reference/client/mail/mail/#op-patch-api-v1-client-mail-service-id-category)