Not on Gmail? You can send outreach from any mailbox — Hostinger, Outlook, Yandex, Zoho, or your company's own mail server — by connecting it over SMTP (outgoing mail) and IMAP (incoming mail). No migration, no DNS changes: OrbitVibe simply signs in to your existing mailbox the same way a mail app on your phone would.
Why IMAP too? SMTP only sends. Replies, bounces and your CRM conversation view all come from reading the inbox — that's IMAP. Both are required; a send-only connection would leave you blind to answers.
It takes about two minutes. Your password is stored encrypted (AES-256) and is only ever used to talk to your own mail server. Disconnecting the account deletes the stored credentials immediately.
The short version
Go to Settings → Email Accounts → Connect account → Connect SMTP / IMAP.
Enter the email address you'll send from.
Pick your provider — the server settings fill themselves.
Paste the password (for most providers this is an app password, not your normal login — see your provider below).
Click Verify & connect.
OrbitVibe then runs a real end-to-end check: it signs in to both servers, sends a small test email from your mailbox to itself, and waits for that email to show up in your inbox. When it arrives, the account is connected and ready. The whole check usually takes 10–30 seconds.
Step-by-step guides per provider:
What your provider needs
Gmail / Google Workspace
Google does not allow normal passwords over SMTP — you need an app password:
Turn on 2-Step Verification: myaccount.google.com/security.
Create an app password: myaccount.google.com/apppasswords → give it a name (e.g. "OrbitVibe") → copy the 16-character password.
In OrbitVibe, pick Gmail / Google Workspace as the provider and use that app password. Servers are filled automatically (
smtp.gmail.com:587STARTTLS,imap.gmail.com:993).
Notes: IMAP is always enabled on current Gmail accounts. Google caps SMTP sending at roughly 500 emails/day on personal accounts (2,000 on Workspace) — keep your OrbitVibe daily limit below that.
Prefer OAuth? Gmail accounts can also connect with one click via Connect Gmail (no app password at all) — see the Google Cloud setup guide. SMTP is the fallback for when OAuth isn't an option.
Outlook / Microsoft 365
Personal (outlook.com / hotmail.com): turn on two-step verification, then create an app password at account.live.com/proofs/manage.
Microsoft 365 (business): your admin must enable Authenticated SMTP for the mailbox (Microsoft 365 admin center → the user → Mail → Manage email apps → tick Authenticated SMTP). Without it the connection fails with an authentication error even though the password is correct.
Servers are filled automatically (smtp.office365.com:587 STARTTLS, outlook.office365.com:993).
Hostinger
No app password concept — use the mailbox's normal password (the one set in hPanel → Emails). Servers fill automatically (smtp.hostinger.com:587 STARTTLS, imap.hostinger.com:993).
On an older Hostinger plan? Many older Hostinger mailboxes actually run on Titan Email and need different servers — pick the Titan Email preset instead (smtp.titan.email:587, imap.titan.email:993). Quick check: if your webmail lives at app.titan.email, you're on Titan. Details in the Hostinger guide.
Titan Email
Titan powers mailboxes sold through Hostinger (older plans) and several other hosting companies. Use the mailbox's normal password — or an app password if two-factor auth is enabled (Titan webmail → Settings → Third-party app access). Pick the Titan Email preset and the servers fill automatically (smtp.titan.email:587 STARTTLS, imap.titan.email:993).
Yandex Mail
In Yandex Mail: Settings → Email clients → enable access via IMAP.
Create an app password: id.yandex.com → Security → App passwords → type "Mail".
Servers fill automatically (smtp.yandex.com:587 STARTTLS, imap.yandex.com:993).
Zoho Mail
In Zoho Mail: Settings → Mail Accounts → IMAP → enable IMAP access.
If two-factor auth is on, create an application-specific password (Zoho Accounts → Security → App Passwords).
The presets use the global hosts (
smtp.zoho.com/imap.zoho.com). On an EU or India data center, open Server settings and change the hosts to.euor.in.
Any other provider ("Custom / other")
You need four things from your mail host's documentation (usually under "email client setup" or "manual configuration"):
SMTP host + port —
smtp.yourhost.com, 587 (STARTTLS) — preferred — or 465 (SSL/TLS)IMAP host + port —
imap.yourhost.com, 993 (SSL/TLS)Username — usually the full email address
Password — mailbox password, or an app password if 2FA is on
Pick Custom / other as the provider and the server fields open up. Unencrypted connections are not supported — every connection uses SSL/TLS or STARTTLS.
If verification fails
"SMTP connection failed" / "IMAP connection failed" — wrong host, port or password. Double-check you're using an app password where the provider requires one, and that IMAP is enabled in the provider's settings.
Microsoft 365: authentication error with a correct password — Authenticated SMTP is disabled for the mailbox; ask your admin (see above).
"Verification email did not arrive" — the mail was sent, but the IMAP inbox you connected doesn't receive mail for that address. This happens when the SMTP relay and the mailbox belong to different accounts, or when the address is an alias delivered elsewhere. Connect the mailbox that actually receives the address's mail.
Being throttled? The connect endpoint allows a handful of attempts per 10 minutes — wait briefly and retry.
After connecting
The account starts with a conservative daily limit (50/day). If the mailbox is brand new, keep it low for 2–3 weeks and raise it gradually — that warm-up is what keeps you out of spam folders.
Check the domain badge on the account card: SPF, DKIM and DMARC on your sending domain are what decide whether your mail lands in inboxes. OrbitVibe verifies them for you and shows exactly what's missing.
Everything you send through OrbitVibe is also filed into the mailbox's own Sent folder, and replies land in your OrbitVibe inbox within a few minutes.