Connect sender accounts

Connect a Google, Microsoft, or IMAP/SMTP mailbox in Settings → Sender Accounts, then send from Inbox and the Send Email column tool.

In-app path: /settings/sender-accounts.

Google uses Connect Google (OAuth), with an app password as a fallback. Microsoft uses Connect Microsoft (OAuth only). Other providers use IMAP / SMTP with host, port, and password.

Plans

Sender accounts are never shared. Any signed-in user can connect their own, with no mailbox cap.

Unipile (LinkedIn, WhatsApp, and Unipile mail) is separate from sender accounts.

Plan	Unipile	Unipile sharing	Sender accounts
Free	Workspace owner or admin only. 1 LinkedIn and 1 WhatsApp.	Off.	Each signed-in user can connect their own. Unlimited. Not shared.
Starter	Workspace owner or admin only. 1 LinkedIn and 1 WhatsApp.	Off.	Each signed-in user can connect their own. Unlimited. Not shared.
Pro / Scale	Each member connects their own, including more than one per kind.	Off by default. Owners and admins can share an account with any member. Other members can share only with the owner or an admin. The workspace-wide “share all” toggle is optional.	Each signed-in user can connect their own. Unlimited. Not shared.
Lifetime only	Owner or admin only. 1 LinkedIn and 1 WhatsApp. Connecting is allowed.	Off, unless the user also has Pro or Scale.	Each signed-in user can connect their own. Unlimited. Not shared.

Who can connect sender accounts

Any signed-in user can connect their own mailboxes, including Free and Starter members. Sender accounts are never shared. If you cannot see Settings → Sender Accounts, refresh or sign in again.

Connect Google

Click Connect Google.
Sign in on Google and allow access to mail.
You are sent back to Sender Accounts. A toast says Mailbox connected.

Google may show an unverified-app warning until the Kuration Gmail app is verified. That is expected. Choose Continue if you trust this workspace.

App password instead

Google only issues app passwords after 2-Step Verification is on. Official help: Sign in with app passwords.

Open Google 2-Step Verification while signed in as the mailbox you will connect.
Complete the setup (phone, authenticator, or another method Google offers).
Open App passwords, name it Kuration, and copy the 16-character code.
In Gmail: Settings → See all settings → Forwarding and POP/IMAP → Enable IMAP.
In Kuration, under Google, fill in Email and App password, then click Connect with app password.

If this is a Google Workspace account, an admin must allow 2-Step Verification and app passwords. The admin cannot generate the password for you.

If the App passwords page is missing:

2-Step Verification is not on yet
The account uses security keys only
The account is in the Advanced Protection Program
A Workspace admin has blocked app passwords

Do not paste your normal Google sign-in password. Gmail rejects it for IMAP.

Connect Microsoft

Microsoft is OAuth only. App passwords are not accepted.

Click Connect Microsoft.
Sign in on Microsoft and allow access to mail.
You are sent back to Sender Accounts. A toast says Mailbox connected.

Microsoft 365 work or school accounts may ask an admin to approve the app the first time. Personal Outlook, Hotmail, and Microsoft 365 all use the same button.

If a connected mailbox later shows status error, click Reconnect on that row and sign in again. That works for Google (OAuth) and Microsoft.

To drop a mailbox, click Remove. That only disconnects it from Kuration. It does not delete the mailbox at Google or Microsoft. Revoke unused app passwords in Google, or remove the Kuration app from Google / Microsoft account permissions.

Connect IMAP / SMTP

Use this for Zoho, Fastmail, cPanel, or any other mailbox that gives you IMAP and SMTP credentials. Both are required. IMAP is how replies show up in Inbox. SMTP-only services (Amazon SES, SendGrid, Mailgun) are not supported.

Open Settings → Sender Accounts.
Under IMAP / SMTP, fill in email, password, IMAP host, and SMTP host.
Username is optional. Leave it blank if it is the same as the email address.
Ports default to IMAP 993 (implicit TLS) and SMTP 587 (STARTTLS). Use 143 / 465 if your provider says so.
Click Connect mailbox. Status should become ready.

Ask your provider for the IMAP and SMTP hostnames. Enable IMAP on the mailbox before connecting. If connect fails, check host spelling, port, and whether the password is an app password (some hosts reject the normal login password).

To reconnect a failed IMAP/SMTP mailbox, fill the form again with the same email address. OAuth Reconnect is only for Google and Microsoft sign-in.

Use the connected mailbox

Once status is ready:

Inbox — send and reply from that address
Send Email tool — pick the mailbox as the from account when you add or run the column
Sequences — choose it as the sender account

Open a mailbox to set a lower daily send limit or skip sending days. Those settings only affect first-touch email. Volume still follows the messaging rate limits.

If connect fails

What you see	What to try
Google “unverified app” screen	Expected until Google verifies the Gmail app. Continue if you trust this workspace.
Sign-in page does not appear	OAuth is not configured for that provider.
Microsoft asks for admin approval	A Microsoft 365 admin must consent to the Kuration mail app for the tenant.
Email and password are required	Both fields must be non-empty on the app-password form.
IMAP host and SMTP host are required	Custom IMAP/SMTP connect needs both hostnames.
Password incorrect / auth failed (Google)	Use a fresh app password, not the Google sign-in password. Create a new one if you changed the Google account password (Google revokes app passwords when you do).
Password incorrect / auth failed (IMAP/SMTP)	Confirm host, port, username, and whether the provider wants an app password. IMAP must be on.
Cannot find Sender Accounts	Refresh, or sign in again. The page is under Settings → Sender Accounts.
Mailbox listed with an error	Click Reconnect and sign in again (Google OAuth and Microsoft). For app-password or IMAP/SMTP mailboxes, fill the same form again, or Remove and connect again.

Treat an app password like a secret. Do not put it in Slack, a spreadsheet, or a screenshot.