2023-08-23: accidentally sent out emails to some SaaS users from a test email
Customer Impact
About 300 emails sent out from fatjuiceofficial@gmail.com test email.
Current Status
The incident is added in retrospect for documentation purposes, the impact had lasted between 10:00 and 10:38 UTC.
We were testing a feature that would allow us to send emails using a custom email configuration. That configuration accidentally remained persistent on a one of the background processing node, and instead of being used for a single email message, other notification emails were sent using that test configuration.
The content of those emails was unchanged and correct, the only difference being, instead of gitlab@mg.gitlab.com, the sender address (From header) was set to fatjuiceofficial@gmail.com.
📚 References and helpful links
Recent Events (available internally only):
- Feature Flag Log - Chatops to toggle Feature Flags Documentation
- Infrastructure Configurations
- GCP Events (e.g. host failure)
Deployment Guidance
- Deployments Log | Gitlab.com Latest Updates
- Reach out to Release Managers for S1/S2 incidents to discuss Rollbacks, Hot Patching or speeding up deployments. | Rollback Runbook | Hot Patch Runbook
Use the following links to create related issues to this incident if additional work needs to be completed after it is resolved:
- Corrective action ❙ Infradev
- Incident Review ❙ Infra investigation followup
- Confidential Support contact ❙ QA investigation
Note: In some cases we need to redact information from public view. We only do this in a limited number of documented cases. This might include the summary, timeline or any other bits of information, laid out in our handbook page. Any of this confidential data will be in a linked issue, only visible internally. By default, all information we can share, will be public, in accordance to our transparency value.