Choose whether a Google recipient map redirects or also delivers the original message

The original-delivery checkbox changes whether the first mailbox still receives mapped messages.

Governed cloud identity system with connected service and lifecycle nodes.
DSE visual intelligenceIdentity & cloudGuide · 2 min read
Executive summary

What you need to know

The original-delivery checkbox changes whether the first mailbox still receives mapped messages.

Potentially affected

This applies to Google Workspace administrator recipient address maps. It does not grant access to existing mailbox contents, establish a delegate relationship, or determine whether the mapped recipient may send as the original user.

DSE recommendation

DSE recommends recording the business purpose and delivery outcome before creating an address map.

The original-delivery checkbox changes whether the first mailbox still receives mapped messages.

Source facts

Google Workspace recipient address maps can redirect incoming mail or forward it to additional recipients. The Also route to original destination option preserves delivery to the original mailbox; without it, a redirect can send the message only to the mapped destination. The rule can cover all incoming messages, including internal mail, or only external incoming messages. An optional X-Gm-Original-To header preserves the original recipient for header-based processing and diagnostics. Google documents this administrator mapping under Gmail Routing, distinct from Default routing and user-managed automatic forwarding.

Source: Google — Recipient address maps.

Applicability

This applies to Google Workspace administrator recipient address maps. It does not grant access to existing mailbox contents, establish a delegate relationship, or determine whether the mapped recipient may send as the original user.

DSE recommendation

DSE recommends recording the business purpose and delivery outcome before creating an address map. For an absence, decide whether both mailboxes should receive new messages; for a replacement workflow, confirm who owns the destination and how long the map should remain. Review internal and external message scope separately. Preserve original-recipient information when approved downstream processing needs it. Check existing mappings for loops or duplicate delivery paths and assign a removal or review date so temporary forwarding does not become an unowned data-sharing arrangement.

Verification

Send approved synthetic messages from both internal and external test senders. Confirm delivery at every intended mailbox and inspect the optional original-recipient header where enabled. Verify that no unintended duplicate or redirect loop occurs and distinguish new-message routing from access to historical mailbox data.

Official reference

Google — Recipient address maps. Reviewed October 15, 2026.

Primary reference

Review the official source

Google — Recipient address maps · Verified October 15, 2026

Open official reference ↗
Plan the next step

Need help applying this guidance safely?

DSE can help confirm applicability, protect service continuity, and validate the result across physical security and IT systems.

Talk with DSE