New Gmail/Yahoo email requirements

[yaelberger-commits]

Description

We need to understand the new Gmail/Yahoo email security requirements so we can identify any risks, mitigate them and communicate with clients any impact to them or their services.

WHY are we building? Gmail/Yahoo have come out with new email requirements WHAT are we building? Documentation and possibly a communications strategy VALUE created by our solution We will be able to get ahead and mitigate any risks/impact for clients sending emails to recipients using Gmail/Yahoo

Documentation and Artifacts

https://docs.google.com/document/d/1ZmbqdKUIxIxyMS-SFm68JS7SZXIW6aJbsyr9JOVeQac/edit#heading=h.tmav9398xag6

Acceptance Criteria

Given some context, when (X) action occurs, then (Y) outcome is achieved

• [ ] Cypress UI tests if needed.

• [ ] Generate appropriate log messages so that executions of this feature can be tracked

• [ ] Can misuse of this feature cause harm? If yes, create an alert

• [ ] Update the status of related findings, insights, and hypotheses on the Research Airtable

• [ ] Once change/fix/feature is implemented, link relevant Airtable records to design artifacts (Figma)

• A11y

• Bilingualism

• Privacy considerations

• Security controls in place

• Measuring success and metrics

[yaelberger-commits]

Hey team! Please add your planning poker estimate with Zenhub @jzbahrai @yaelberger-commits @andrewleith

[yaelberger-commits]

Jumana scheduled us a meeting for next week

[yaelberger-commits]

Jimmy, Andrew and Yael met and went through more of the requirements. We will continue to document evidence and consider reaching out to clarify how some of these requirements are enforced