This KB provides the steps necessary to set up custom domain authentication for 3rd party and cloud applications
Configuring Authenticated Email from a 3rd party using the vendor DKIM record;
This KB provides the steps necessary to set up custom domain authentication for 3rd party and cloud applications who;
To improve deliverability of email, SPF and DKIM should both be configured, but do NOT have use matching domains. In this article, you'll learn how to set up DKIM to authenticate email from your desired domain.
NOTE: If you intend to send email ‘as’ @illinois.edu, we cannot add additional include statements to the campus SPF record. This configuration will require that the vendor use their own domain in the ‘mail from’ address of messages, while using ‘illinois.edu’ in the ‘header from’, using the DKIM signature coordinated with Technology Services in the following steps.
To set up domain authentication, you must submit the DNS records provided by SendGrid to your DNS or your domain record with the campus host manager. The CNAME record creates an alias for subdomain.yourdomain.com and points to sendgrid.net. This will be what your messages are signed by, so your recipients will be able to see what you have chosen for your CNAME. You set up the CNAME files that SendGrid provides with your DNS host.
Working within your 3rd party application interface, or with their support;
If you intend to send email from '@illinois.edu', you can request creation of 'domainkey.illinois.edu' records from the Campus Email Relays administrators by submitting to firstname.lastname@example.org. If you are intending to send email from your own subdomain or second-level domain, you can make this request directly to the campus host manager at email@example.com.
Where to escalate the ticket to:
Consultants can use Contacts Database to contact the service admin: https://cdb.cites.illinois.edu/item/3488/