Connect a mailbox (Google, Microsoft, any provider)

Every message sent from a connected mailbox goes out through that mailbox's own provider, logged in as that mailbox — never through SendCanyon's mail servers. Go to Sender Accounts → External mailboxes → Add mailbox and pick Google, Microsoft or Any provider. You never type server names or ports for Google or Microsoft.

Google (Gmail and Google Workspace)

Option 1 — Sign in with Google. One click: choose the account and allow access. Best for Google Workspace. If your Workspace admin restricts third-party apps, they need to mark SendCanyon as trusted once (Google Admin → Security → Access and data control → API controls → Manage Third-Party App Access).

Option 2 — App password. For personal Gmail, or when your admin blocks sign-in. You enter only your email and a 16-letter app password:

1. 1

   Turn on 2-Step Verification for the Google account.

2. 2

   Create an app password and copy it. Spaces don't matter.

3. 3

   Paste it in the wizard. IMAP is always on for Gmail, so there is nothing else to switch on.

If Option 1 isn't shown, your account uses Option 2. Changing your Google password revokes app passwords — create a new one and reconnect.

Microsoft 365 and Outlook.com

Sign in with Microsoft. One click. If your organization requires admin approval, the wizard says so — your Microsoft 365 admin approves SendCanyon once, then everyone connects in one click. Outlook.com, Hotmail and Microsoft 365 bought through GoDaddy use the same sign-in; Microsoft no longer accepts passwords for these.

Microsoft also requires Authenticated SMTP to be on for each sending mailbox. If it's off, the wizard shows the fix and a Try again button. An admin turns it on at Microsoft 365 admin center → Users → Active users → the user → Mail → Manage email apps → Authenticated SMTP → Save, or in Exchange Online PowerShell: Set-CASMailbox -Identity [email protected] -SmtpClientAuthenticationDisabled $false. If IMAP is off: Set-CASMailbox -Identity [email protected] -ImapEnabled $true. Changes can take a few minutes to apply. With GoDaddy-hosted Microsoft 365, the switch is in GoDaddy's Email & Office Dashboard → Manage → Advanced Settings → SMTP Authentication.

Any provider

Pick your provider from the list — Zoho Mail, Yahoo Mail, GoDaddy Professional Email, Hostinger, Namecheap Private Email, Fastmail, iCloud Mail or Yandex Mail — and enter your email and password. The server settings are filled in for you. Yahoo, Fastmail, iCloud and Yandex require an app password (the wizard links to where you create one); Zoho requires one when 2-factor sign-in is on. Zoho and Yandex ship with IMAP switched off — turn it on in their mail settings first. Choose Custom for anything else and enter the SMTP host and port (465 with SSL, or 587 without) and, to capture replies, the IMAP host (usually port 993). Amazon SES is in the same list and takes an access key and region.

Bulk import by CSV

Import CSV on the External mailboxes tab connects many app-password or SMTP mailboxes at once. Columns: email, app_password, optional name (or first_name and last_name), and for custom servers smtp_host, smtp_port, imap_host, imap_port. Pick the provider the rows belong to (Google by default); Gmail, Yahoo, iCloud and similar addresses are recognised on their own, and a row with smtp_host is treated as a custom server. Each row goes through the same live login check as the wizard, and you get a result per row — failures say what to fix and don't stop the rest. Sign in with Google and Microsoft connect one account at a time.

What the errors mean

What Test connection checks

1. 1

   For SMTP mailboxes, logs in to the SMTP server with the stored credentials. No email is sent.

2. 2

   For Google and Microsoft mailboxes, signs in to Gmail's or Microsoft's SMTP server with the mailbox's own sign-in. No email is sent.

3. 3

   For Amazon SES mailboxes, confirms the stored credentials are complete. No login is attempted and no email is sent.

Send test email: the real check

Send test email (the send icon on each mailbox row) sends one real message from that mailbox, through its own server and login — the same transport a campaign send uses, including the Google and Microsoft OAuth sign-in. The result shows the server it connected to, whether the recipient was accepted, the server's reply line and the Message-ID. It never falls back to SendCanyon's mail servers: if your mailbox cannot send, the test fails and says why. It is limited to 5 per mailbox per hour. Sender identities have the same action: it sends through SendCanyon's relay with the domain's DKIM signature, exactly as a campaign does, and shows the relay's reply. The Test tab under Sender Accounts runs either kind, or checks a whole domain — its live DNS records plus one real send.

Re-run either check any time from the mailbox's row. If a password rotates or OAuth is revoked, campaign sends from that mailbox fail and the row shows the latest send error until it is fixed.