---
schema_version: "1"
id: 37fc287cacc1c2a3052e6dab57507cb82331fe9adc17b8ed666dc70d0c479daf
title: Enable Forward Reply Header Rewrite
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_es_enable_forward_reply_header_rewrite.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_es_enable_forward_reply_header_rewrite.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 1bd0831a043b53afbf925b79f4dc5ae17ecd670be2127a7eac407cc24d6891f3
description: Use Forward Reply Header Rewrite with Enterprise Reply Mail Management in Marketing Cloud Setup to specify a reply-to header value that complies with DMARC requirements. These requirements mandate that email messages originate from the expected destination for a domain. This feature uses those values to ensure that while Reply Mail Management processes all replies, those messages use the correct domain. This process facilitates communication between you and your subscribers.
products:
  - Marketing
  - Marketing Cloud Engagement
release: "264"
---
# Enable Forward Reply Header Rewrite

Use Forward Reply Header Rewrite with Enterprise Reply Mail Management in Marketing Cloud Setup to specify a reply-to header value that complies with DMARC requirements. These requirements mandate that email messages originate from the expected destination for a domain. This feature uses those values to ensure that while Reply Mail Management processes all replies, those messages use the correct domain. This process facilitates communication between you and your subscribers.

For example, you can forward an email address, such as example@example.com, to a personal account, such as Gmail or Yahoo. This feature ensures that all communications include a reply-to header that includes the personal email address in any replies to example@example.com. Including the domain helps ensure that the email meets DMARC requirements.