This article covers the SPF authentication process for NICE inContact and how is that managed in Valimail Enforce.

At present time, we have yet to see any evidence that NICE inContact supports actual DKIM implementation.

Although NICE inContact's current documentation states that they have a process of setting up DKIM for your domain, we have yet to see any DKIM implementation for any domain which is using this sending service.

If you are on the verge of setting up DKIM in NICE inContact for your domain and you are managing DKIM in Valimail, please contact us at [email protected] and let us know about your DKIM implementation with NICE inContact.

You can also find the instructions on how to set up SPF alignment on NICE inContact, 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 NICE InContact emails are not authenticated via SPF, even after you have added NICE InContact to your domain's configuration. This is likely caused by NICE InContact not sending SPF aligned-mail and can be corrected by making sure the return path of the NICE InContact emails is changed to match your domain.

To that end, please contact your NICE InContact service administrator and make sure they are turning on SPF alignment in NICE InContact, for your domain.