{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/google-workspace-recipient-map-original-delivery-header/", "item": { "id": "https://update.dsesecurity.com/updates/google-workspace-recipient-map-original-delivery-header/", "slug": "google-workspace-recipient-map-original-delivery-header", "url": "https://update.dsesecurity.com/updates/google-workspace-recipient-map-original-delivery-header/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/google-workspace-recipient-map-original-delivery-header.md", "json": "https://update.dsesecurity.com/api/v1/posts/google-workspace-recipient-map-original-delivery-header/" }, "title": "Choose whether a Google recipient map redirects or also delivers the original message", "summary": "The original-delivery checkbox changes whether the first mailbox still receives mapped messages.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "identity-cloud", "label": "Identity & cloud", "alt": "Governed cloud identity system with connected service and lifecycle nodes.", "card_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "slug": "microsoft-365-identity", "name": "Microsoft 365 & Identity", "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-10-15T13:33:59+00:00", "modified_at": "2026-10-15T13:36:18+00:00", "reviewed_on": "2026-10-15", "reading_minutes": 2, "word_count": 277, "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.", "primary_source": { "name": "Google — Recipient address maps", "url": "https://knowledge.workspace.google.com/admin/gmail/advanced/redirect-or-forward-gmail-messages-to-another-user?hl=en", "published_on": null, "authority": "knowledge.workspace.google.com" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

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

\n

Source facts

\n

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.

\n

Source: Google — Recipient address maps.

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official reference

\n

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

", "content_text": "The original-delivery checkbox changes whether the first mailbox still receives mapped messages.\nSource facts\nGoogle 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.\nSource: Google — Recipient address maps.\nApplicability\nThis 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.\nDSE recommendation\nDSE 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.\nVerification\nSend 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.\nOfficial reference\nGoogle — Recipient address maps. Reviewed October 15, 2026.", "content_markdown": "The original-delivery checkbox changes whether the first mailbox still receives mapped messages.\n\n## Source facts\n\nGoogle 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.\n\nSource: [Google — Recipient address maps](https://knowledge.workspace.google.com/admin/gmail/advanced/redirect-or-forward-gmail-messages-to-another-user?hl=en).\n\n## Applicability\n\nThis 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.\n\n## DSE recommendation\n\nDSE 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.\n\n## Verification\n\nSend 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.\n\n## Official reference\n\n[Google — Recipient address maps](https://knowledge.workspace.google.com/admin/gmail/advanced/redirect-or-forward-gmail-messages-to-another-user?hl=en). Reviewed October 15, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/google-workspace-recipient-map-original-delivery-header/", "url": "https://update.dsesecurity.com/updates/google-workspace-recipient-map-original-delivery-header/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-15" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/google-workspace-recipient-map-original-delivery-header/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Choose whether a Google recipient map redirects or also delivers the original message", "item": "https://update.dsesecurity.com/updates/google-workspace-recipient-map-original-delivery-header/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/google-workspace-recipient-map-original-delivery-header/#article", "identifier": "https://update.dsesecurity.com/updates/google-workspace-recipient-map-original-delivery-header/", "url": "https://update.dsesecurity.com/updates/google-workspace-recipient-map-original-delivery-header/", "headline": "Choose whether a Google recipient map redirects or also delivers the original message", "description": "The original-delivery checkbox changes whether the first mailbox still receives mapped messages.", "abstract": "The original-delivery checkbox changes whether the first mailbox still receives mapped messages.", "articleBody": "The original-delivery checkbox changes whether the first mailbox still receives mapped messages.\nSource facts\nGoogle 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.\nSource: Google — Recipient address maps.\nApplicability\nThis 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.\nDSE recommendation\nDSE 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.\nVerification\nSend 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.\nOfficial reference\nGoogle — Recipient address maps. Reviewed October 15, 2026.", "datePublished": "2026-10-15T13:33:59+00:00", "dateModified": "2026-10-15T13:36:18+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/google-workspace-recipient-map-original-delivery-header/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/google-workspace-recipient-map-original-delivery-header/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Choose whether a Google recipient map redirects or also delivers the original message" }, "articleSection": [ "IT", "Microsoft 365 & Identity" ], "keywords": [ "IT", "Microsoft 365 & Identity", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Microsoft 365 & Identity", "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/" } ], "wordCount": 277, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Google — Recipient address maps", "url": "https://knowledge.workspace.google.com/admin/gmail/advanced/redirect-or-forward-gmail-messages-to-another-user?hl=en" } } ] } }