This article covers the SPF and DKIM authentication processes for Oracle Eloqua 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.

To use DKIM, your company must acquire a Branding & Deliverability package from Oracle Eloqua and submit a DKIM signing request to them. Depending on the plan you've purchased, you can request a DKIM signature for 3-20 domains.

To use your corporate domain with Eloqua signature rules which sends emails on behalf of your domain, your IT team will need to add the public key to the corporate domain.

As part of the initial setup, you/your IT team will receive a confirmation email as part of this process. This email will include a link that you need to click as part of the setup process.

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

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

Once you establish that Hushmail 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.

You may notice that Oracle Eloqua emails are not authenticated via SPF, even after you have added Oracle Eloqua to your domain's configuration. This is likely caused by Oracle Eloqua not sending SPF aligned-mail and can be corrected by configuring a CNAME record.

More details on how to achieve that are found in the article, here.