Skip to main content
SAP SuccessFactors

How to set up DMARC for SAP SuccessFactors in Valimail

Updated over 5 months ago
SPF(supported) / (dedicated subdomain)
DKIM(recommended)

This article covers the SPF and DKIM authentication processes for SAP SuccessFactors and how they are managed in Valimail. While only one of the two authentication methods is required for an email to pass DMARC, our recommendation is to configure both whenever possible.

Configuring DKIM authentication for your SAP SuccessFactors emails

SPF is enabled by default & you can contact your internal mail administrator to enable SPF record (See KBA 2087468).

For DKIM, Please reach out to SAP Cloud Support team (under component LOD-SF-PLT-SEC) with the following information provided:

  • Company ID

  • Datacenter

  • Your mail domain details;

(Provide a full list of the email domains used by users - there may be more than one).

e.g. @testcompany.com and @testcompany.org.

Note: The DKIM or SPF enablement is done on a data center level. This means that separate requests would only be needed for instances using different domains or same domain on an instance which is hosted on a different data center. Also, the domain is checked by the operations team before being added to SPF/DKIM, to ensure that it is from the respective customer and that the domain of one customer cannot be used by another customer.

You can also find the instructions on how to set up DKIM and SPF for SAP SuccessFactors, here.

Add a SAP SuccessFactors DKIM key in Valimail

You can find more detailed information on how to add a DKIM key in Valimail, here:

Configuring SPF authentication for your SAP SuccessFactors emails

Once you establish that SAP SuccessFactors is an authorized sender for your domain, you will need to add the service in your Enabled Senders.

You will find more detailed information on how to add a service for your domain in Valimail, here:

Note: We encourage you to use the comment section for any useful information about your sending service, such as the name of the service owner, change request ticket numbers, etc.

Did this answer your question?