Connecting Quin to an Email Provider That Isn't Gmail or Outlook

A wealth management office running its own mail server, or a small business owner paying for email through a regional ISP, hits the same wall the moment they try to add Quin. The integrations list is full of Gmail and Outlook icons, and neither applies. The mail server works fine for statements and client calls. It just isn't one of the two platforms every software company assumes everyone uses, so the assistant that was supposed to handle email prep sits unused, with no obvious button to connect it.

What Tends to Get Missed

• The provider gets treated as a dead end. Once someone sees Gmail and Outlook as the only two icons on an integrations page, they assume their own domain-hosted email simply isn't supported, and stop looking further.
• IT staff get looped in for something that doesn't need them. A solo advisor or office manager will sometimes ask a contractor about a custom connection, when the mailbox may already support a standard protocol that needs none.
• The mailbox stays disconnected from meeting prep. Without an active connection, none of the email context makes it into meeting notes or follow-ups.
• App-specific passwords get overlooked. Many self-hosted or regional providers require a separate app password rather than the account password, and skipping that step is the most common reason a first attempt fails.
• Teams assume every mailbox needs its own workaround. If one person's provider connects, others on that mail system can follow the same steps.

How Quin Handles It

Quin doesn't require an email provider to be Gmail or Outlook. It offers a direct IMAP/SMTP connection option, the standard protocol most email providers, including self-hosted mail servers and regional ISPs, already support. Instead of building a custom integration for every provider, Quin connects using the credentials most mail systems already expose: an IMAP address for reading mail and an SMTP address for sending it.

Picture an advisor whose firm runs email through a regional provider that has never appeared on a software integrations page. Instead of waiting on a connector that may never come, the office manager enters the IMAP and SMTP details once, and Quin starts reading the mailbox and drafting responses the same way it would with any major provider.

This matters because Quin's value depends on seeing the whole picture, not just the meetings that happen to run through a supported inbox. A firm locked out of that by which company hosts its email loses the same context and follow-up support a competitor on Gmail gets by default.

Best Practices

• Confirm the exact server addresses before starting. Most providers publish IMAP and SMTP hostnames and ports on a settings page, avoiding back-and-forth during setup.
• Use an app-specific password if the provider offers one. This keeps the primary account password untouched.
• Test with one mailbox before rolling out to a team. Confirming the connection works for one person surfaces provider-specific quirks first.
• Keep a record of the server settings used. If a password ever needs rotating, the original configuration makes reconnecting fast.

Setting It Up

Connecting a mailbox this way takes the IMAP and SMTP server details, the mailbox's username, and a password or app-specific password from the provider, entered once during setup. From there, the mailbox can be connected under Settings, then Integrations.