Several e-mail verification schemes like SPF, DKIM, DMARC exist to help prevent e-mail abuse such as spam or phishing. These schemes verify that e-mails from a given domain
mycompany.com are sent from an authorized set of SMTP servers.
Problems arise as Jenkins can be configured to send e-mails as a developer/committer e-mail like
However, if you have activated SPF, DKIM, or DMARC these e-mails may be classified as spam or blocked completely because they aren’t sent from a SMTP server authorized by your domain but from our DEV@cloud platform.
To allow e-mails sent from SendGrid with SPF you have to add/update your DNS entry for SPF by adding
include:sendgrid.net in it. For example, if you are already authorizing e-mails from
mycompany.com to be sent from Google and your MX servers you will have something like:
mycompany.com. TXT "v=spf1 mx include:aspmx.googlemail.com include:sendgrid.net ~all"
To allow e-mails sent from SendGrid with DKIM you have to add a CNAME entry in your DNS configuration to find the domain key on our side
s1._domainkey.mycompany.com. 3600 IN CNAME s1._domainkey.cloudbees.com.
DMARC is based on result of SPF and DKIM and adds more controls like the ability to reject emails which didn’t pass these controls. You have no additional setup to do, you just need to ensure that SPF and DKIM controls are passing.