Skip to content
Docs menu

Email from your own mailbox

Connect a mailbox with an app password so Comms and Outreach send email from you. Venom checks the sign-in and the domain's SPF, DKIM and DMARC, paces sends, reads only reply and bounce headers, and puts a one-click unsubscribe in every email.

View .md

The email channel sends from a mailbox you already have, over SMTP, and reads that mailbox's inbox over IMAP for replies and bounces. The email comes from you, and replies land in your normal inbox. Venom adds no tracking pixel and rewrites no links.

Connect a mailbox

  1. Create an app password for the mailbox. This is not your sign-in password:
    • Gmail: turn on 2-Step Verification, then create one at myaccount.google.com/apppasswords.
    • Fastmail: Settings, Privacy & Security, Integrations.
    • iCloud Mail: account.apple.com, Sign-In and Security, App-Specific Passwords.
    • Outlook.com: turn on two-step verification, then create one in your Microsoft account's security settings.
  2. In Settings → Comms → Mailboxes, choose Connect a mailbox, then enter the address and the app password. For Gmail, Fastmail, iCloud Mail and Outlook.com the servers are filled in. For any other host, open Servers and enter its SMTP server (port 465 or 587) and its IMAP server (port 993).
  3. Venom signs in to both servers before it saves anything. If the password is wrong, the dialog says so, for example "The mailbox refused the password (SMTP said 535)", and nothing is stored.

Saving also checks the address's domain in DNS. The card shows the result in plain words:

Check What Venom looks for When it is missing
SPF a v=spf1 TXT record on the domain "SPF missing: … mail may go to spam"
DKIM a key under the usual selectors (google, selector1, fm1, …) a note to check your provider signs for the domain
DMARC a v=DMARC1 TXT record at _dmarc.<domain> "DMARC missing: replies may go to spam"

The password is sealed in the vault (purpose comms) and only its last characters are shown. Use Test sign-in and DNS on a mailbox to run both checks again. Google and Microsoft sign-in (OAuth) are planned; app passwords are the only way to connect for now.

Nothing contacts a mailbox until you save one. A disabled or removed mailbox is never signed in to.

Fields

Field Default Notes
Email address required Sends come from it; replies are read from its inbox
Your name none The display name on the From line
App password required Sealed; leave empty on edit to keep it
Signature none Added under every email
Daily cap 40 At most 500
Username the address Only if your host signs in with something else
SMTP server, port filled in for known hosts 465 is implicit TLS; 587 uses STARTTLS
IMAP server, port filled in for known hosts 993, implicit TLS

Sending

Send on the email channel through /v1/comms/messages, the comms_message_send MCP tool or Outreach. An email needs a subject:

{
  "to": "ana@example.com",
  "channel": "email",
  "body": "Hi Ana, good to meet you at the meetup.",
  "email": { "subject": "Following up" }
}

To reply in a thread, pass the Comms id of an earlier message in that conversation as email.in_reply_to. Venom then sets In-Reply-To and References from that message and adds Re: to the subject. Every email has its own Message-ID, which is how replies are matched later.

Each email has a plain text part and a minimal HTML version of the same text. A body can be up to 4,000 characters. Media and templates are refused on email.

Pacing and warm-up

  • At most one email a minute from a mailbox, spaced randomly 2 to 7 minutes apart. A send that has to wait shows as scheduled and goes out on its own.
  • A new mailbox starts at 10 emails a day and adds 5 a day until it reaches its daily cap (40 unless you change it).
  • Past the day's allowance, sends wait for the next UTC day.

Unsubscribe

Every email ends with "Don't want these? Unsubscribe." The link goes to /u/<token> on your Venom Cloud, and the email also carries the headers mail apps use for their own unsubscribe button:

List-Unsubscribe: <https://cloud.example.com/u/…>, <mailto:you@example.com?subject=unsubscribe>
List-Unsubscribe-Post: List-Unsubscribe=One-Click

The token is signed with a key for your org and names the org, the channel and the recipient. It never expires. Opening the link shows one button. Pressing it, or a mail app's one-click POST (no sign-in, no cookie), adds an opt-out for that address with source keyword and stops their Outreach. Later sends to the address are refused with "The recipient unsubscribed from email." A matched reply does the same when its subject is "unsubscribe" (what the mailto: link sends) or its first line is "stop", "unsubscribe", "remove me" or "opt out".

Links use VENOM_CLOUD_ORIGIN when it is set, so set it to your public cloud address.

Replies and bounces

The sweep cron reads each enabled mailbox's inbox at most every 3 minutes. It opens INBOX read-only and asks only for the headers of mail that arrived since the last read; mail that was there when you connected is never read.

  • A reply is matched by its In-Reply-To or References against the Message-IDs Venom sent, or else by its From address against the email handles of people enrolled in Outreach. Only then is its text read. It becomes a normal Comms inbound message on channel email, so it shows in Conversations and reaches Outreach like any other reply.
  • A bounce (a delivery status notification, or mail from mailer-daemon or postmaster) marks the original message failed with "Bounced: …", marks the person's email handle as bounced, and stops their Outreach.
  • Auto-replies (out of office) are ignored.
  • Everything else is left alone. Venom reads its headers to decide that it is unmatched and stores nothing from it.

If a read fails, the card shows the error, and the next read tries again.