OpenOutreach + Gmail

OpenOutreach does not send email on your behalf from a shared pool of IPs. It sends from your mailbox, over your provider's own SMTP, and reads the replies back over IMAP. For Gmail and Google Workspace that means smtp.gmail.com and imap.gmail.com — the documented default, and the configuration the onboarding wizard assumes.

What connecting Gmail gives you

• Replies land where you already work. The daemon reads INBOX over IMAP, so a reply shows up in Gmail like any other message. There is no separate inbox to check.
• Your sending reputation is yours. Because mail leaves your own mailbox, deliverability is tied to your domain and your history rather than to a shared sending service.
• Opt-outs route back to you. Unsubscribe replies are delivered to the same mailbox the daemon reads, so they are processed without a webhook or a hosted callback.
• You keep the data. Contacts, threads and replies live in the database on the machine you run OpenOutreach on.

What you need

A Gmail or Google Workspace mailbox with SMTP and IMAP access, and credentials for it. Gmail requires an app password rather than your account password once two-factor authentication is on — this is standard for any IMAP/SMTP client.

Sign-in with Google (OAuth) is not shipped yet; today the connection is username plus app password.

Sub-addressed replies

Outbound mail uses +-tagged reply addresses so each thread can be matched back to the right conversation. This depends on the provider routing + tags to the base mailbox — Gmail and Google Workspace both do. If you later connect a non-Gmail mailbox, that is the behaviour worth checking by hand.

Daily limits

Gmail enforces its own per-day sending limits, and they differ between free Gmail and Workspace accounts. OpenOutreach has a configurable daily cap per mailbox — set it at or below what your account actually allows rather than discovering the ceiling by hitting it.

docker run --pull always -it -v ~/.openoutreach/data:/app/data ghcr.io/eracle/openoutreach:latest