Page MenuHomePhabricator

Consolidation and tracking of automated email alerts improvements across services
Open, MediumPublic

Description

In our ongoing efforts to enhance the reliability and standards compliance of our automated email alerts, this task serves as a central hub to coordinate, track, and document the progress across multiple related tasks.

The primary purpose of this task is to identify and consolidate automated email alerts, so the different SRE teams ensure compliance with RFC 3834 by adding the 'Auto-Submitted: auto-generated' header on the emails generated by the services they own.

This initiative is in response to observed issues with automated responses, notably the Gmail vacation responder's unnecessary replies to automated emails, indicating a broader need for compliance and improvement.

Objectives:

Track Automated Email Improvements: This task will act as a central point for managing related subtasks to improve automated email standards.
RFC Compliance: We will work to ensure all automated emails include the 'Auto-Submitted: auto-generated' header, preventing unnecessary responses like the Gmail vacation responder issue.
Inventory and Documentation: A comprehensive inventory of automated emails will help track RFC 3834 compliance and prioritize fixes.

Related Tasks:

Inventory:

Non-Compliant Email Subjects:
(List of automated email subjects lacking the header)

  • Fail event on /dev/md1:centrallog1002
  • INFRINGING WEBSITE CONTENT (WASHLET) - Toto Ltd. - https://en.wiktionary.org/wiki/washlet
  • Cron <isaacj@stat1008> sudo -u analytics-privatedata kerberos-run-command analytics-privatedata /home/isaacj/public_se_referrals/update_data.sh
  • WMDE Banner impressions
  • exim paniclog on mw2405.codfw.wmnet has non-zero size
  • Cron <isaacj@stat1008> sudo -u analytics-privatedata kerberos-run-command analytics-privatedata /home/isaacj/plugin/extract_daily_wprov.sh

Event Timeline

I'm removing the observability tag because directly addressing emails generated by services owned by other teams falls outside the scope of the observability team.

The primary purpose of this task is to identify and consolidate automated email alerts, so the different SRE teams ensure compliance with RFC 3834 by adding the 'Auto-Submitted: auto-generated' header on the services they own.

BCornwall added a project: SRE.
BCornwall subscribed.

Which teams should be added?

Which teams should be added?

relevant subtasks should be created for the various system/tools generating the emails and the teams responsible for those should be added to them. generic overarching tasks like this that end up with every team tag getting added to them don't really help and add to the confusion.

taavi subscribed.

This task does not seem to have anything to do with email handling internals in MediaWiki?

I'm re-adding o11y then because the overarching goal is for them while the subtasks are relevant for whichever teams they are destined.

I'm removing the observability tag because directly addressing emails generated by services owned by other teams falls outside the scope of the observability team.

I also don't think that the overarching goal is for o11y but to service owners as that would benefit all of the SRE team. :)