> For the complete documentation index, see [llms.txt](https://docs.mailofly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mailofly.com/guides/deliverability/accounts.md).

# Sending accounts

A **sending account** is the delivery identity Mailofly uses when handing off mail to your provider — SMTP relay, Gmail API, or SES on a verified domain.

**In the app:** [Accounts](https://www.mailofly.com/user/accounts)

***

## Provider comparison

|                  | SMTP                        | Google          | Domain relay               |
| ---------------- | --------------------------- | --------------- | -------------------------- |
| **Setup**        | Host + credentials          | OAuth connect   | Verified domain required   |
| **From address** | Provider-dependent          | Gmail address   | Custom `@yourdomain.com`   |
| **Daily limit**  | You configure (default 500) | 500/day fixed   | No Mailofly cap            |
| **Best for**     | ESPs, custom servers        | Workspace teams | Branded transactional mail |
| **API create**   | ✓                           | ✓               | App only                   |

***

## Add an account

### SMTP

1. **Accounts → Add account → SMTP**
2. Enter a friendly **name**, **host**, **port**, **username**, **password**
3. Set **daily mail limit** (start low on new infrastructure)
4. Save → **Send test** to verify

```json
POST /api/v1/accounts
{
  "name": "Transactional SMTP",
  "provider_type": "smtp",
  "smtp_host": "smtp.example.com",
  "smtp_port": 587,
  "smtp_username": "apikey",
  "smtp_password": "your-secret",
  "daily_mail_limit": 500
}
```

### Google

1. **Accounts → Add account → Google**
2. Complete OAuth consent
3. Account appears with your Google email as sender

Tokens refresh automatically. Mailofly requests offline access so sends continue without re-auth.

### Domain relay

1. Verify a domain under [**Domains**](/guides/deliverability/domains.md) first
2. **Accounts → Add account → Domain sender**
3. Pick the verified domain, set **From email** and optional display name

Mail sends through Amazon SES with DKIM signing on your domain.

***

## Account key

Each account exposes a public **`acc_…` key** on the Accounts page. Required for [Compose API](https://docs.mailofly.com/api/compose) calls:

```json
{
  "account_key": "acc_d8deb498ca3e43b09d01e6f251ca26ea",
  "subject": "Order confirmed",
  "body": "<p>Thanks for your purchase.</p>",
  "recipients": { "emails": ["buyer@example.com"] }
}
```

***

## Quota & deferral

When a campaign exceeds an account's daily limit:

1. Remaining recipients get `mail_logs.status = deferred`
2. They send automatically the next calendar day
3. Or add another account to increase today's capacity

{% hint style="warning" %}
Google accounts are capped at **500 sends/day**. Plan multi-account rotation for larger blasts.
{% endhint %}

***

## Related

* [Domains & DNS](/guides/deliverability/domains.md)
* [Campaigns](/guides/campaigns-and-content/campaigns.md)
* [API: Accounts](https://docs.mailofly.com/api/accounts)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mailofly.com/guides/deliverability/accounts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.