> 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/get-started/sending-accounts.md).

# Connect a sending account

A **sending account** is how Mailofly delivers mail — your SMTP server, Google mailbox, or verified domain.

Manage them in [**Accounts**](https://www.mailofly.com/user/accounts).

***

## Choose a provider

| Provider   | Best for                                    |
| ---------- | ------------------------------------------- |
| **Google** | Gmail / Google Workspace                    |
| **SMTP**   | SendGrid, Mailgun, SES, cPanel, self-hosted |
| **Domain** | Branded `@yourdomain.com` (needs DNS first) |

After connecting, send a **test email** from the account card.

***

## Account key

Every account has an **account key** (`acc_…`) on the Accounts page. Optional for the [Emails API](https://docs.mailofly.com/api/emails) and SDKs:

```json
{
  "from": "Acme <hello@yourdomain.com>",
  "to": ["you@example.com"],
  "subject": "Hello",
  "html": "<p>Hi</p>",
  "account_key": "acc_xxxxxxxx"
}
```

***

## Daily limits

Mailofly tracks sends per account per day:

* **SMTP** — configurable (default 500/day)
* **Google** — 500/day
* **Domain** — no Mailofly-enforced daily cap

Over-quota recipients are marked `deferred` and retry the next day.

{% hint style="info" %}
New domains: start at 50–100 emails/day and ramp up over 2–4 weeks.
{% endhint %}

***

## Next

* [Domains & DNS](https://docs.mailofly.com/guides/domains) — SPF, DKIM, DMARC
* [Email types](/get-started/email-types.md) — Compose vs Campaigns
* [Sending examples](/get-started/sending-examples.md)


---

# 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/get-started/sending-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.