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

# Sending via SMTP

> Connect an SMTP-compatible app or mail client to Qubrics.

Use SMTP when an existing application, plugin, or mail client already supports SMTP delivery.

> [!NOTE]
>
> The SMTP password is your `smx_mbx_` send-only key, mailbox password, or owner-approved Sending-resource `smx_agent_` token.
> Routing still follows that key or mailbox scope.

> [!WARNING]
>
> Managed Amazon SES is for transactional email only. Use your own provider for
> marketing, newsletters, or bulk promotional sends.

## Connection details

| Setting | Value |
| - | - |
| **Host** | `smtp.qubrics.com` |
| **Port** | `587` with STARTTLS, or `2525` with STARTTLS |
| **Username** | Any value, such as `smtpuser` |
| **Password** | Your `smx_mbx_` send-only key, mailbox password, or owner-approved Sending-resource `smx_agent_` token |
| **Authentication** | `LOGIN` or `PLAIN` |

## Test with swaks

```bash theme={null}
swaks --to user@example.com \
  --from hello@example.com \
  --server smtp.qubrics.com:587 \
  --auth LOGIN \
  --auth-user smtpuser \
  --auth-password "smx_mbx_your_key_here" \
  --tls \
  --header "Subject: Test email" \
  --body "Hello from Qubrics"
```

## Select delivery groups

Add one `X-Qubrics-Delivery-Group` header containing comma-separated group public IDs:

```text theme={null}
X-Qubrics-Delivery-Group: dgrp_group_a, dgrp_group_b
```

Replace the example IDs with your groups' public IDs. Qubrics trims surrounding whitespace and deduplicates IDs, with a maximum of 50 groups. Empty entries and repeated occurrences of the header are rejected, including when separate occurrences contain the same value. A folded continuation belongs to the same header.

The hint can only narrow the credential's authorised providers. Shared-domain sending ignores it and retains its forced route. See [Delivery groups](https://sendmux.ai/docs/sending/accounts/delivery-groups.md#restrict-one-message) for the scope rules.

Unless shared-domain routing ignores the hint, invalid, unknown, foreign-team, or disallowed hints receive a permanent `550` response. Temporary service failures remain retryable. Qubrics removes the routing header before delivery.

Use [template variables](https://sendmux.ai/docs/sending/template-variables.md) in subjects and bodies to insert values from the selected account.

## SMTP vs HTTP

| Need | Use |
| - | - |
| Existing SMTP-only tool | SMTP |
| New application integration | HTTP API |
| Batch sending | HTTP API |
| Built-in retry protection | HTTP API |
| Native MIME message handling | SMTP |

## What happens next

Successful SMTP sends appear in **Logs** like HTTP sends. Use the message ID, sender, recipient, status, provider, and timestamp to trace delivery.

## Acceptance during busy periods

When sending capacity is occupied, Qubrics can still accept your direct SMTP submissions using send-only keys or owner-approved Sending-resource tokens after it stores the message and reserves the required credits.

SMTP `250` confirms acceptance for background sending, though delivery can still fail. Check **Logs** for the result.

`452 4.3.1 Insufficient credits.` means the message was not accepted.

## Free daily limit

Free teams can send to 50 accepted recipients per UTC day across SMTP and HTTP. Qubrics reserves capacity before returning `250`, so concurrent SMTP sessions cannot cross the cap.

When no daily capacity remains, SMTP returns `550 5.7.1 Daily sending limit reached. Upgrade to Pro to continue.` The message is not queued. Retry after `00:00 UTC` or upgrade the team to Pro.

## Related guides

> [card] [Send by HTTP](https://sendmux.ai/docs/sending/http.md)
>
> Use the API for new integrations and batch sends.

> [card] [API keys](https://sendmux.ai/docs/account/api-keys.md)
>
> Create the credentials used as SMTP passwords.

> [card] [Delivery logs](https://sendmux.ai/docs/monitoring/dashboard-logs.md)
>
> Search and export SMTP delivery results.


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