Should my dedicated sending domain be able to receive emails?

Email marketer from Email Geeks guesses that the ESP uses the subdomain for the 5321.From / bounce tracking, so inbound goes to their bounce processor.

Email marketer from Litmus explains that using a subdomain is a way to protect your primary domain’s reputation. The article focuses on sending and does not mention any MX records that are required to receive email.

Email marketer from Email Geeks shares their experience with Braze, where From addresses can't receive replies because during DNS record creation they can only set up the subdomains to send email, but not receive them.

Email marketer from StackExchange suggests that for dedicated sending domains, it's more common to configure them specifically for sending and tracking bounces. Receiving emails on the sending domain isn't usually a priority.

Email marketer from Quora shares that dedicated sending domains are typically used to isolate sending reputation and are not configured to receive inbound emails. Instead, use a separate, more general domain for receiving emails.

Email marketer from Email on Acid explains that a subdomain is often used for email campaigns. The subdomain isolates sending reputation from the main domain. It's not generally used to receive email so that replies go to the main company domain.

Email marketer from Reddit advises that while it's technically possible to set up a dedicated sending domain to receive emails, it's generally not recommended. It's better to keep sending and receiving separate to avoid potential deliverability issues.

Email marketer from Email Geeks clarifies that CNAME records setup MX records so that they can create a bounce address/return path and receive and process them.

Expert from Email Geeks mentions that in Klaviyo, the “sending domain” is used as the domain in the authenticated fields and they’re CNAMED, which is why they can’t receive email.

Expert from Email Geeks states it is imperative that if the hello@send.brand.com can’t accept email then you Absolutely Should Not use it in the From: address and never send mail with a 5322.from a domain that cannot receive mail.

Expert from Email Geeks explains that the from: / reply-to: domains are not as strong an identity as the domains in the authentication string, suggesting not to worry too much about clear separation.

Expert from Word to the Wise answers a question on their forum by explaining the importance of setting up a feedback loop with ESPs, and that this can be a critical step when setting up a dedicated sending domain. To action, you need to be able to receive email, meaning if your sending domain cannot receive email, you will not be able to take advantage of Feedback Loops.

Expert from Email Geeks suggests that the subdomain is being used as the 821.From, so it delivers to the bounce manager, recommending to use hello@brand.com as the 822.From and feed that address into the support ticketing system.

Documentation from SparkPost explains that dedicated IP addresses are not required to receive email. They are primarily used for sending email and building a positive sending reputation. You would typically use your main domain for receiving emails.

Documentation from DMARC.org explains about setting up DMARC policies. It implies that a separate sending domain is created for authentication purposes, suggesting it doesn't need to receive emails for DMARC to function correctly.

Documentation from SendGrid mentions that dedicated IPs are used to build a good sending reputation. While not directly answering if it should receive emails, it implies the focus is on outbound sending rather than inbound receiving.

Documentation from Mailjet shares that dedicated sending domains are typically configured to only send emails and are not set up to receive inbound emails. The MX records, which are essential for receiving emails, are usually not configured for dedicated sending domains.