Hi all,
We've recently introduced customer email sub-domains in our instances. Emails sent from the instance come from a particular sub-domain depending on what type of notification and application is sending it. For example support@businessgroup.ourorg.com We've added SPF and MX records for these domains, but SPF fails due to an existing CNAME entry that is in place for our custom URL which is the same as the new email sub-domain.
The only solution we have is to change the name of the sub-domain, but it seems strange that we can't use the same domain for both the portal URL and the email. Has anyone encountered this issue before and how did you deal with it?
