在此頁面上：瞭解如何在頻道設定中設定電子郵件標頭引數，包括[寄件者]、[回覆]、[錯誤]和選用的[寄件者]欄位，以及如何管理回覆處理和電子郵件轉寄。
設定新的電子郵件通道設定時，在 標頭引數 區段中，輸入與該設定所傳送電子郵件型別相關的寄件者名稱和電子郵件地址。
- 輸入 contact 作為寄件者電子郵件前置詞 — 寄件者電子郵件為 contact@marketing.luma.com。
- 輸入 error 作為錯誤電子郵件前置詞 — 錯誤位址為 error@marketing.luma.com。
_、點.和連字型大小-字元。寄件者標頭 sender-header
某些使用案例會要求傳輸郵件的信箱與 來自 的作者不同，例如代表子公司傳送的父級組織、多個品牌的共用行銷團隊，或為多個客戶傳送的代理商。
換句話說，寄件者是郵件的作者（電子郵件的寄件者），而 寄件者 是負責傳輸郵件的代理程式（實際傳送者）。 Sender欄位適用於傳輸實體與作者不同的情況。
在此情況下，您可以使用 寄件者標題 區段中的下列欄位，設定要新增至電子郵件標題的其他 寄件者 名稱和電子郵件地址：
-
寄件者名稱：當訊息與 寄件者 作者不同時，負責傳輸訊息的一方的名稱。
-
寄件者電子郵件：傳送方的電子郵件地址。
設定 寄件者名稱 和 寄件者電子郵件 時，Journey Optimizer會將寄件者 SMTP標頭新增至電子郵件。 支援此功能的電子郵件使用者端可能會顯示例如 代表From 的寄件者或 透過 的指標。
設定 Sender 標頭時，請考量下列事項：
-
如果您將 寄件者名稱 和 寄件者電子郵件 欄位都保留空白，或是解析的 寄件者 與 寄件者 相同，則不會新增 寄件者 標頭。
-
寄件者地址未用於SPF、DKIM或DMARC對齊；僅執行 格式 驗證。 SPF、DKIM和DMARC繼續依賴 From 欄位。 為組態選取的委派子網域仍舊是這些檢查所使用的傳送網域。
-
如果已設定 Sender 標頭，且個人化未解析為收件者的值，則郵件不會傳遞給該收件者。
回覆電子郵件 reply-to-email
定義 回覆電子郵件 地址時，只要電子郵件地址是有效、格式正確且不含任何拼寫錯誤，您就可以指定任何電子郵件地址。
用於回覆的收件匣將將收到所有回覆電子郵件，但休假通知和質詢回覆除外，這些郵件將在 錯誤電子郵件地址收到。
若要確保正確管理回覆，請遵循下列建議：
-
確保專用收件匣有足夠的接收容量，可接收使用電子郵件設定傳送的所有回覆電子郵件。 如果收件匣出現退信，您可能無法收到客戶的一些回覆。
-
處理回覆時必須牢記隱私權與合規義務，因為回覆可能包含個人識別資訊 (PII)。
-
請勿在回覆收件匣中將郵件標示為垃圾訊息，因為這會影響傳送至此地址的所有其他回覆。
此外，在定義 回覆電子郵件 地址時，請務必使用具有有效 MX 記錄設定的子網域，否則電子郵件設定處理將會失敗。
如果在提交電子郵件設定時發生錯誤，表示您輸入之位址的子網域尚未設定 MX 記錄。 請連絡您的管理員以設定對應的 MX 記錄，或使用其他具有有效 MX 記錄設定的位址。
轉寄電子郵件 forward-email
若要將 Journey Optimizer 收到的委派子網域的所有電子郵件轉寄至特定電子郵件地址，請聯絡 Adobe 客戶服務部門。
您需要提供：
- 您選擇的轉寄電子郵件地址。 請注意，轉寄電子郵件地址網域無法與委派給 Adobe 的任何子網域相符。
- 您的沙箱名稱。
- 將使用轉寄電子郵件地址的設定名稱或子網域。
- 每個子網域只能有一個轉寄電子郵件地址 — 如果多個設定使用相同的子網域，則必須對所有設定使用相同的轉寄電子郵件地址。
- 如果未啟用轉寄，則預設會捨棄直接傳送至 寄件者電子郵件 位址的電子郵件。
轉寄電子郵件地址由 Adobe 設定。 這需要 3 至 4 天的時間。
完成後，回覆電子郵件和 錯誤電子郵件 地址收到的所有郵件，以及傳送至 寄件者電子郵件 地址的所有電子郵件，都會轉寄至您提供的特定電子郵件地址。
This section contains structured knowledge intended to support interpretation, retrieval, and question answering related to this topic.
For complete understanding, this information should be combined with the documentation on this page. Neither source is intended to stand alone; the page describes the feature, while this section provides additional context that helps disambiguate terminology, intent, applicability, and constraints.
- TL;DR: This page explains how to set up the email header parameters in a channel configuration — the From, Reply to, Error, and optional Sender fields — and how to manage reply handling and email forwarding.
Intents:
- Configure the From name, From email prefix, Reply to name, Reply to email, and Error email prefix in a channel configuration
- Set optional Sender headers when the transmitting entity differs from the From author
- Manage where reply emails, out-of-office notifications, and challenge responses are received
- Set up an email forward process for the delegated subdomain
- Understand the formatting rules for email prefixes
Glossary:
- From name / From email prefix: The sender name and email address used for communications; the prefix uses the selected delegated subdomain (product-specific)
- Reply to name / Reply to email: The name and address used when the recipient clicks Reply in their email client (product-specific)
- Error email prefix: The address that receives asynchronous bounces (ISP errors after a few days), out-of-office notifications, and challenge responses (product-specific)
- Sender headers (Sender name / Sender email): Optional fields identifying the party responsible for transmitting the message when it differs from the From author; adds a Sender SMTP header (product-specific)
- Delegated subdomain: The subdomain used to send the email and used for SPF, DKIM, and DMARC checks (product-specific)
Guardrails:
- When editing an email configuration, you cannot add new profile attributes to header parameters; you must create a new channel configuration.
- For From email prefix and Error email prefix, values must begin with a letter (A-Z) and can only contain alphanumeric characters, plus underscore
_, dot., and hyphen-. - Sender name and Sender email must be configured together — both filled in or both empty; filling in only one prevents journeys and campaigns from being published with this channel configuration.
- If both Sender fields are empty, or the resolved Sender is identical to From, no Sender header is added.
- The Sender address is not used for SPF, DKIM, or DMARC alignment (only format validation is performed); those checks continue to rely on the From fields and the delegated subdomain.
- If Sender headers are configured and personalization does not resolve to a value for a recipient, the message is not delivered to that recipient.
- The Reply to email must be a valid, correctly formatted address on a subdomain with a valid MX record, otherwise email configuration processing fails.
- Forwarding is set up by Adobe (contact Adobe Customer Care) and can take 3 to 4 days; the forward email address domain cannot match any subdomain delegated to Adobe.
- There can be only one forward email address per subdomain; configurations sharing a subdomain must use the same forward email address.
- If forwarding is not enabled, emails sent directly to the From email address are discarded by default.
Terminology:
- Canonical name: Header parameters — Acronym: n/a — variants: sender headers, header fields
- Synonyms: “From” = “author of the message”; “Sender” = “agent responsible for transmitting the message”
- Do not confuse: “From” (author) ≠ “Sender” (transmitting party) ≠ “Reply to email” (address receiving replies) ≠ “Error email” (address receiving asynchronous bounces, out-of-office notifications, and challenge responses)
FAQ:
- Q: Which address receives asynchronous bounces and out-of-office notifications? — The Error email prefix address; out-of-office notifications and challenge responses are received there rather than on the Reply to email.
- Q: Can I fill in only the Sender name or only the Sender email? — No. Both must be configured together, or both left empty; filling only one prevents publishing journeys and campaigns with the configuration.
- Q: Does the Sender field affect SPF, DKIM, or DMARC? — No. Only format validation is performed on the Sender address; SPF, DKIM, and DMARC continue to rely on the From fields and the delegated subdomain.
- Q: Why did my email configuration fail on submission? — The MX record is likely not configured for the subdomain of the Reply to email address; contact your administrator or use an address with a valid MX record.
- Q: How do I forward emails received for the delegated subdomain? — Contact Adobe Customer Care to set up a forward process, providing the forward email address, sandbox name, and configuration name or subdomain; setup can take 3 to 4 days.