The most important fact about email in Revogent: we do not operate an email sending service. Every outreach message is sent by the user's own mailbox, through the same infrastructure as mail they write by hand.
This page explains the send path, what that means for SPF, DKIM, and DMARC, and the human controls on outbound messaging.
How sending works
- Microsoft 365: messages are sent with a Microsoft Graph call as the signed-in user, from their own mailbox. Sent messages are saved to the user's Sent Items, exactly like mail sent from Outlook.
- Google Workspace: messages are sent through the Gmail API as the signed-in user, from their own mailbox.
- What does not exist: there is no SMTP relay, no shared IP pool, no third-party email service provider, and no "via" headers. Revogent infrastructure never transmits mail on behalf of your domain.
SPF, DKIM, and DMARC
Because messages originate inside Exchange Online or Gmail as the authenticated user, they are authenticated by your existing mail infrastructure:
- SPF: evaluated against Microsoft's or Google's sending infrastructure, exactly as for any mail your users send today.
- DKIM: messages are signed with your tenant's existing keys, unchanged.
- DMARC: alignment holds because the mail genuinely is your domain's mail, sent by your own tenant. A strict enforcement policy (p=quarantine or p=reject) requires no changes to accommodate Revogent.
Human control over outbound
- Approval gate: every AI-drafted message lands in a review state, and a person explicitly approves each message before it can send.
- Kill switches: outbound communications can be paused platform-wide instantly, and also paused for individual users.
- Automatic protective pauses: sequences pause automatically on bounces, out-of-office replies, and complaint signals, and require human review to resume.
- Unsubscribe handling: outreach sequences include unsubscribe handling backed by signed, tamper-resistant links.
Tracking and links
Outreach messages can include lightweight open and click tracking served from Revogent-controlled endpoints. Tracking only affects links and a pixel inside the message body; it has no effect on message authentication or DMARC alignment.
Inbound sync
Connected inboxes sync server-to-server through Microsoft Graph change notifications and delta queries, or Gmail push notifications. Notification payloads are validated against per-subscription secrets before processing. Synced messages power CRM threading and reply detection, and the OAuth tokens involved are encrypted at rest.
Product and account email
Sign-in codes and account emails are delivered by our identity provider from Revogent-controlled domains. Nothing Revogent operates ever sends as your domain.