Confirmed users
1,364
edits
ReleaseEngineering/How To/Process release email: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/How To/Process release email (view source)
Revision as of 17:01, 19 December 2016
, 19 December 2016add elease+moc_notifications@mozilla.com
(add elease+moc_notifications@mozilla.com) |
|||
| Line 13: | Line 13: | ||
= Index = | = Index = | ||
''Note:'' The "Wildcard" column gives a suggestion on how to filter for that email. | |||
{| cellpadding="10" cellspacing="0" border="1" class="fullwidth-table sortable" | {| cellpadding="10" cellspacing="0" border="1" class="fullwidth-table sortable" | ||
| Line 59: | Line 59: | ||
|- | |- | ||
|To || release+mozdef@mozilla.com || Security alerts from infosec's Mozdef server. Alert team&infosec if you find suspicious activity. | |To || release+mozdef@mozilla.com || Security alerts from infosec's Mozdef server. Alert team&infosec if you find suspicious activity. | ||
|- | |||
|To || release+moc_notifications@mozilla.com || Something from the MOC. Action depends on content. (Cited in [https://mana.mozilla.org/wiki/display/MOC/MOC+Contact+Groups#MOCContactGroups-Teams mana]). | |||
|} | |} | ||
| Line 232: | Line 234: | ||
== How to best filter these emails == | == How to best filter these emails == | ||
As noted in the table above, these are sent to release+mozdef@mozilla.com | As noted in the table above, these are sent to release+mozdef@mozilla.com | ||
=Mail to release+moc_notifications@mozilla.com= | |||
== Why we get them == | |||
Unsure when MOC will use this address. | |||
== What is sending them == | |||
Humans from MOC will use this address. | |||
== What to do when one is received == | |||
* Read and handle | |||
== How to silence or acknowledge this alert == | |||
* depends on context | |||
== Future plans == | |||
Unknown | |||
== How to best filter these emails == | |||
Filter by "to" address. | |||
=Sample= | =Sample= | ||