# Professional email

Mailboxes on your company domain, with guided DNS (MX, SPF, DKIM, DMARC) and a plan per mailbox.

Source: https://ardumaker.com/en/docs/correo-profesional/

- Category: Communication
- Status: Available
- Requirements: An active company in ArduMaker where you are a member or admin; Your own domain and access to its DNS panel; A payment method or balance for paid mailboxes
- MCP tools (Read only): `listar_dominios_correo`, `ver_dominio_correo`, `ver_stats_dominio_correo`, `listar_cuentas_correo`, `ver_cuenta_correo`
- MCP tools (Write or modify): `crear_dominio_correo`, `verificar_dns_dominio_correo`, `crear_cuenta_correo`, `editar_cuota_cuenta_correo`
- MCP tools (Destructive): `eliminar_dominio_correo`

## What can you do with it?

Use addresses like `name@yourcompany.com` on ArduMaker's mail server. Each company registers its email domains and creates mailboxes on them.

- Register an email domain and get the DNS records to publish.
- Verify MX, SPF, DKIM and DMARC from the panel or through MCP.
- Create mailboxes with a plan that sets the storage quota.
- Move a mailbox to a bigger plan without recreating it.
- See domain statistics and the IMAP/SMTP logins of each mailbox.

## When should you use it?

- The company needs email on its own domain for team members.
- You want to keep people's mailboxes apart from addresses used by programs: that is what [bot accounts](https://ardumaker.com/en/docs/cuentas-bot) are for.
- An AI agent has to set up email for a new domain end to end.

## How does it work in ArduMaker?

1. **Domain registration.** ArduMaker registers it on the mail server and stores the records to publish: MX, SPF (`v=spf1 mx include:arducloud.com ~all`), the DKIM key generated by the server and DMARC with `p=quarantine`.
2. **DNS publication.** The records go into the domain's DNS provider. The exact values are copied from the panel.
3. **Verification.** ArduMaker checks MX, SPF, DKIM and DMARC. The domain is verified only when all four pass.
4. **Mailboxes.** Once the domain is verified you create mailboxes: local part, display name, password and a public plan. The quota comes from the plan.
5. **Billing.** Each mailbox is linked to a company service and billed monthly, or in 6, 12 or 18-month blocks when prepaid.

> **INFO:** Each domain has a mailbox cap. Once reached, new mailboxes are rejected and you need to ask support for more.

## What actually changes?

- On the mail server: the domain, its DKIM key and each mailbox with its quota.
- In ArduMaker: the domain with the state of each DNS record and the date of the last check.
- In billing: one service per mailbox, at its plan price.
- When changing plans, the quota is updated on the server and the service price moves to the new plan.

> **PELIGRO:** Deleting an email domain also deletes all its active mailboxes on the server. In practice it cannot be undone.

## Diagram

**Setting up email on your own domain**

```text
Panel or MCP agent (requests the setup)
  ↓
ArduMaker API (checks access and plan)
  ↓
Mail server (domain, DKIM and mailboxes)
  ↓
Customer DNS (MX, SPF, DKIM, DMARC)
  ↓
DNS verification (enables creating mailboxes)
```

Mailboxes are created only once all four records are verified.

## Expected result

A verified domain and active mailboxes that receive and send email. Each mailbox is used from [webmail](https://ardumaker.com/en/docs/webmail) or from a client over [IMAP and SMTP](https://ardumaker.com/en/docs/smtp-imap), and shows up as a service in the [company usage](https://ardumaker.com/en/docs/consumo-de-servicios).

## Errors and troubleshooting

| Symptom | Cause |
| --- | --- |
| `Domain already registered` | The domain is already registered in ArduMaker. |
| 424 error `mail_server_rejected_domain` | The mail server rejected the registration or did not answer. The reason is in the message. |
| `Domain DNS is not verified...` when creating a mailbox | The domain DNS has not been verified yet. |
| `mailbox_limit_reached` | The domain reached its mailbox cap. |
| `Cannot downgrade to a lower plan...` | You can only upgrade. To downgrade, create another mailbox. |

If verification marks a record as failing, check the copied value and run it again: verifying is safe to retry. Domain and mailbox creation through MCP accept `idempotency_key` to retry without duplicates.

## MCP access

Every tool needs an agent authorized through OAuth and access to the company that owns the domain. The full reference is at [/mcp/docs](https://ardumaker.com/en/mcp/docs) and the domain summary at [/mcp/correo](https://ardumaker.com/en/mcp/correo).

| Type | Tools |
| --- | --- |
| Read | `listar_dominios_correo`, `ver_dominio_correo`, `ver_stats_dominio_correo`, `listar_cuentas_correo`, `ver_cuenta_correo` |
| Modify | `crear_dominio_correo`, `verificar_dns_dominio_correo`, `crear_cuenta_correo`, `editar_cuota_cuenta_correo` |
| Destructive | `eliminar_dominio_correo` |

> **PRECAUCION:** `crear_cuenta_correo` contracts a paid service. `eliminar_dominio_correo` requires `confirmado=true`; without it, it answers 409 with the number of mailboxes that would be lost.

## Related features

- [Webmail](https://ardumaker.com/en/docs/webmail/)
- [SMTP and IMAP](https://ardumaker.com/en/docs/smtp-imap/)
- [Email aliases](https://ardumaker.com/en/docs/alias-de-correo/)
- [Bot accounts](https://ardumaker.com/en/docs/cuentas-bot/)
- [Domains and DNS](https://ardumaker.com/en/docs/dominios-y-dns/)
- [Service usage](https://ardumaker.com/en/docs/consumo-de-servicios/)