> ## Documentation Index > Fetch the complete documentation index at: https://docs.salesfinity.ai/llms.txt > Use this file to discover all available pages before exploring further. # Mailboxes > Connecting Google Workspace and SMTP mailboxes, the mailbox pool and per-rep assignment, daily limits and warmup, DNS health, test emails and placement tests. Sequences send from mailboxes your team connects under **Sequencer › Mailboxes**. Every email step needs at least one usable mailbox available to the sequence, and every send goes out under the rep who owns the enrollment. ## Connecting a mailbox Click **Connect Google** and sign in with the mailbox that should send. Salesfinity asks for a single Gmail scope, the one that allows sending and reading mail for that mailbox, and nothing else. Google classes this scope as restricted. Until the app clears Google's verification, a Workspace admin must first add Salesfinity as a **trusted app** in the Google Admin console. If the admin has not done that, Google refuses the sign-in with "access denied: admin policy enforced" and the connect dialog explains what to send to the admin. This is a one-time change per Workspace. Google returns a refresh token only on the very first authorisation. If a mailbox was connected before and stops sending after a reconnect, disconnect it fully and connect again. Click **Connect one** and enter: | Field | Notes | | -------------------------- | ------------------------------------------------------------- | | From name, from email | What recipients see. | | Username, password | For most providers, an app password, not your login password. | | SMTP host and port | Outgoing server. | | IMAP host and port | Incoming server, used to read replies and bounces. | | IMAP username and password | Only if different from SMTP. | | Max emails per day | Starting daily limit. | | Signature | Appended to every email from this mailbox. | | Warmup | Whether to start warmup on connect. | Salesfinity sends a test message on connect and refuses the mailbox if SMTP or IMAP fails, with the provider's error. **Import mailboxes** takes a CSV with one mailbox per row and connects them in the background. The import shows each row as pending, connected, rejected (with the reason) or duplicate. ## Pool and assignment Every mailbox is either **assigned to a rep** or in the **shared pool**. * An assigned mailbox sends only that rep's enrollments. Assigning a mailbox moves it out of the pool, so the pool is by construction the mailboxes nobody owns. * A rep with no assigned mailbox sends from the pool. If the pool is empty and the rep has no mailbox, their sequences cannot send and **Enable** on a sequence with email steps is refused. * A sequence can also be limited to specific mailboxes in its settings. Use **assignments preview** to see which rep would send from which mailbox before saving a change. ## Limits, warmup and health | Setting | What it does | | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | | **Daily limit** | Maximum emails per day from this mailbox. Sends beyond it wait for tomorrow. | | **Daily ramp-up** | How many more emails per day the limit grows by while a new mailbox is ramping. | | **Warmup** | Automated warmup traffic between mailboxes to build reputation. Set messages per day, the wait between them, and the reply rate. | | **Custom tracking domain** | Serve open and click tracking from your own domain instead of the shared one. | | **BCC every email to** | Copy every send to an address, for example a CRM logging address. | | **Reply-to** | Where replies should go if not to the mailbox itself. | | **Enabled** | Turn a mailbox off without disconnecting it. **Suspend** does the same from the list. | ### Health Each mailbox shows a health status based on its domain's DNS: | Status | Meaning | | -------------- | --------------------------------------------------------------------------------------------------------------------- | | **Healthy** | SPF, DKIM, DMARC and MX all pass. | | **Needs work** | One record is missing or weak, for example SPF ending in a neutral qualifier or no DMARC policy. | | **Critical** | A record is broken in a way that gets mail rejected or flagged, for example no SPF record at all, or two SPF records. | Open the mailbox and click **DNS** for the exact record, what was found, and the fix. Common ones: * **No SPF record**: receiving servers cannot confirm your domain authorised the send. This is the single most common reason cold email lands in spam. * **Two SPF records**: the standard treats this as an error and checks fail. Merge them into one. * **SPF ends in `?all` or `+all`**: authorises anyone to send as your domain. End it with `~all` or `-all`. * **No DMARC**: publish a `_dmarc` record, starting with `p=none` if you are unsure. * **DKIM not found**: Salesfinity tries the common selectors; if yours is custom, confirm DKIM in your provider's admin console. ## Test emails and placement tests * **Send test email** on a mailbox sends a real message to an address you choose, through the connected account, so you can check the from name, signature and tracking. * **Deliverability › Placement tests** (where available on your plan) send a set of test emails to seed inboxes at the major providers and report, per mailbox and per provider, whether they landed in the inbox, in promotions or in spam. ## Disconnecting **Delete** removes a mailbox. Active enrollments that were sending from it move to the owner's other mailbox or the pool; if there is none, their next email step waits and the enrollment shows a failure reason until a mailbox is available.