GitLab CI/CD
Email checks in your merge request's test widget
A catalog component that sends one real email from your template through your relay. Each of the 42 checks comes back as a test case, so a failed DKIM shows up by name.
42 checks · No key · No account
Include the component
The relay password goes in a CI/CD variable called EST_SMTP_PASSWORD. Mask it if you can.
include: - component: $CI_SERVER_FQDN/stanichev90/email-spam-tester/email-spam-tester@~latest inputs: smtp-host: smtp.example.com smtp-port: 587 smtp-username: billing@example.com from: "Acme Billing <billing@example.com>" subject: Your invoice html-file: templates/invoice.html min-score: 80DMARC alignment can stop holding
without a single bounce.
Where it lives
Questions
Does it need a key?
No key and no account.
Where do results show up?
The job log, the merge request's test widget, and the full report at a link.
What makes the job fail?
A failed SPF, DKIM or DMARC check, or a score under min-score.
Why a real email?
The checks read what your relay adds and what the receiver sees, and a dry run has neither.