Unsendbox logo
Get started
← Return to root

Forwarding email

Use forwarding to keep Google Workspace as your mailbox layer while giving Unsendbox selective visibility and control for AI operations.

Open user guide

Forwarding patterns

Use route-level and address-level controls intentionally.

Pattern A
Inbound copy to Unsendbox + deliverable route to Google aliases.
Pattern B
Google-first MX with selective Unsendbox catch-all for AI-only identities.
Pattern C
Temporary migration forwarding with mirrored delivery for audit and fallback.
Pattern D: Workspace-first + Unsendbox processing
Keep Google MX and IMAP, forward specific identities to Unsendbox for AI-assisted actions.

Workspace-first operational model

Recommended for teams that need Google-native mailbox UX and still want AI workflow control.

Mailbox ownership
Google Workspace remains primary for end-user UX, IMAP, labels, and shared mailbox behavior.
AI operations ownership
Unsendbox handles selected route handling, mirror rules, suppression, and MCP-driven workflow orchestration.
Forwarding boundaries
Forward only explicit identities or tags to Unsendbox, and avoid broad wildcard re-entry to avoid loops.
Loop prevention
Only one-way forwarding should be configured for a given recipient path unless explicitly reviewed in test.

AI-first setup sequence

Use MCP to reduce misconfiguration drift.

  1. 01Confirm domain model with `connect_domain` and `get_domain_health`.
  2. 02Choose a model: Unsendbox-first routing or Google-first routing.
  3. 03Create route destination logic from MCP: alias/forward targets and mirror destinations.
  4. 04Create mapped addresses in Unsendbox for each AI-managed identity.
  5. 05Validate each forwarding change with one known test email first.
  6. 06Use UI route screens to inspect fallback behavior and health indicators.

Workspace-first setup checklist

Use this sequence when Google remains the primary domain mail host.

  1. 01Keep Google MX and DKIM/SPF/DMARC settings active and verified.
  2. 02Create Google alias/forwarding rules only for selected AI identities.
  3. 03Create matching Unsendbox addresses mapped to those forwarded identities.
  4. 04Send a seed message to each mapped identity and verify arrival in Google and Unsendbox.
  5. 05Send one test reply from Unsendbox and verify no relay loop occurs.
  6. 06Enable suppression checks before any production outbound volume.