New Sending Domain with Shared IP and Reply Handling
A company is launching a new transactional email stream on a shared IP. It wants to send from mail.brand-new.com, but the corporate domain brand-new.com is managed by a separate DNS team and has a strict DMARC policy. The company also wants replies to go to a monitored support inbox, and bounce handling must not expose the new domain. The Marketing Cloud account currently uses a Sender Authentication Package on the parent domain and has one verified send classification. The launch is in 10 business days, and the DNS team needs a precise list of records.
1. Outline the setup sequence for the new sending domain and identify which steps depend on DNS and which can be done in Marketing Cloud first.
Read the worked answer
Start in Marketing Cloud by deciding the BU and creating the SAP request for mail.brand-new.com; the SAP will generate the DNS records you need. Send the DNS team the exact records: the SAP domain verification/DKIM records, the SPF inclusion, and the link-tracking CNAME. DNS-dependent steps are domain verification, DKIM validation, SPF alignment, and link branding. While waiting, create the Sender Profile, Send Classification, Delivery Profile, and RMM configuration in Marketing Cloud. Do not send from the new domain until verification and DKIM are live. Because brand-new.com has strict DMARC, use a subdomain and ensure DKIM aligns; 10 days is feasible only if the DNS team responds within 2-3 days.
2. How should Reply Mail Management be configured so replies go to [email protected] without breaking authentication, and what happens to auto-replies?
Read the worked answer
Configure RMM in the SAP/Account Settings: set the reply-to address to the monitored support inbox or to the RMM address that forwards there, and set forwarding to [email protected]. RMM needs its own DNS records, so include them in the DNS request. Keep the visible From address on the authenticated subdomain; do not set Reply-To to a free-mail domain. For auto-replies, choose forward-and-delete or delete so vacation responders do not loop or flood the support inbox. Test with a real reply and an out-of-office before launch. If RMM is not configured, replies go to the From address and may fail DMARC or go to an unmonitored mailbox.
3. The business wants to reuse the existing send classification for the new stream. What factors determine whether a new send classification and delivery profile are required?
Read the worked answer
A Send Classification bundles a Sender Profile, Delivery Profile, and classification type. Reuse is safe only if the new stream uses the same From identity, same IP pool, same throttling, and same compliance treatment. If transactional mail must omit unsubscribe links while commercial mail must include them, create a separate classification. If the new stream must send on a different IP pool or with different throttling, create a new Delivery Profile and a new Send Classification that references it. Do not silently reuse a commercial classification for transactional mail; that changes unsubscribe and preference behavior. Document the choice so the next admin does not merge them later.