IMAP/SMTP integration — connect any mailbox to Oneop

Not every team runs Gmail or Microsoft 365. The generic IMAP/SMTP integration is Oneop’s answer for everyone else: any standards-compliant mailbox — a company mail server, a regional provider, a legacy host — connects the same way the big two do.

What it does

Per-rep mailboxes. Each user points Oneop at their mailbox’s IMAP and SMTP servers with their credentials. Outbound one-to-one email and sequence steps send from that mailbox; inbound mail is polled every minute and threads back onto the deal or contact. On by default.

Support mailboxes for email-to-ticket. With the email-to-ticket module enabled, a workspace connects a shared support mailbox over IMAP. Credentials are verified live at connect time — behind an SSRF egress guard, so the connection test cannot be abused to probe internal networks — and inbound mail becomes deduplicated, threaded tickets with genuine two-way replies over the mailbox’s own authenticated SMTP.

DKIM-signed sending domains. Teams sending sequences at volume can verify a custom sending domain; outbound cold email is then DKIM-signed at the SMTP layer with the domain’s stored key, and an unverified domain blocks the send rather than sending unsigned. Off until you ask for it.

What flows, in which direction

• Bi-directional: send over SMTP, receive over IMAP, per user or per support mailbox.
• Credentials are encrypted at rest with AES-256-GCM and never returned by the API.

Setup

Enter host, port and credentials for IMAP and SMTP; Oneop verifies the connection live before saving.

What it does not do

• Sequence reply auto-exit runs on the Postmark inbound path, not the IMAP poll — see Postmark.
• This is CRM/support mail handling, not a full webmail client.

Related module and plan notes

Per-user mailboxes are on for every plan. Email-to-ticket and custom sending domains are both off until you ask for them. See Sequences and Help desk.