> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spitzli.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Mail

> Prepare a sender domain and distinguish outgoing messages from incoming mail.

Open Mail in the intended workspace. Connections, domains, keys and message history are scoped to that workspace's permissions.

| Task | Required service |
| - | - |
| Send transactional messages | Ready sending connection, Mail API key and verified sender domain |
| Receive or forward incoming messages | Explicitly enabled incoming-mail service |
| Use your own sending provider | Activated turboSMTP connection and its separate limits |

Sending-only does not require a mailbox server. Adding a sender domain does not create mailboxes. Incoming mailboxes and forwarding are activated separately and only for eligible workspaces.

## Prepare API sending

**1. Select a connection**

Open Mail in the correct workspace and select the intended ready connection.

**2. Add your domain**

Use a domain you control. Copy the exact verification records shown.

**3. Publish DNS**

Add those records at your DNS provider and request verification. Review existing SPF and other mail records before changing them.

**4. Create a sending key**

Restrict the application key to the intended domain where appropriate. Store it in your application's private environment.

Continue with [your first API message](https://docs.spitzli.cloud/developers/mail-quickstart.md) and the [Mail API overview](https://docs.spitzli.cloud/developers/mail-api.md).

> [!NOTE]
>
> API implementation, production dispatch and provider event callbacks have separate activation checks. Use the readiness shown for your connection and confirm availability with your operator before relying on delivery.

## Manage incoming Mail

Ask your operator to confirm incoming-mail availability before configuring mailboxes or forwarding. Use the DNS records and settings shown for that service. Outgoing API readiness does not establish that incoming delivery or Webmail is ready.

Disabling incoming Mail retains its data. Permanent deletion is a separate action. During service draining, existing resources remain manageable while creation of new accounts, domains and mailboxes is blocked.

For customer-owned sending, follow [Connect your turboSMTP account](https://docs.spitzli.cloud/guides/byok-mail.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.