> 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/product-guides/accounts.md). # Sending accounts A **sending account** is the identity Mailofly uses to deliver email on your behalf—similar to the “from” server in a desktop mail client, but wired into campaigns and automation. ## What it is Each account stores connection details for either **SMTP** (your own or provider’s mail server) or **Google** (OAuth to Gmail / Google Workspace). Campaign sends pick one or more accounts according to limits and availability. ## How it helps * **Deliverability control** — use domains and IPs you already trust with your ESP or workspace. * **Quota awareness** — daily send limits per account help avoid sudden blocks; Mailofly tracks usage per day. * **Multi-brand setups** — separate accounts for different “from” domains or teams. ## How to use it in the app Open [Accounts](https://www.mailofly.com/user/accounts) in the app. Add an account with the wizard: choose SMTP or Google, enter host/credentials or complete OAuth, and set a friendly name. You can add several accounts; when sending a campaign you can restrict which accounts are used or let Mailofly choose. ### SMTP vs Google **SMTP** works with almost any provider (transactional SMTP, cPanel, etc.) as long as you have host, port, username, and password. **Google** is ideal if your mail already goes out through Gmail or Workspace; OAuth avoids storing your Google password in Mailofly. ## How this differs from “just using Mailchimp” Many all-in-one tools host sending on their shared infrastructure only. Mailofly lets you **bring your own transport**: you keep contracts, reputation, and compliance boundaries with your provider while still using segments, templates, and campaigns in one place. ## Related * [Campaigns](/product-guides/campaigns.md) — how sends use accounts * [REST API: Accounts](/rest-api/accounts.md) * [Manage accounts in the app](https://www.mailofly.com/user/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/product-guides/accounts.md?ask=&goal= ``` `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.