Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validate that sender's email domain matches the domain verification domain #777

Open
coilysiren opened this issue Nov 8, 2024 · 0 comments
Labels
scope: service Service layer / component

Comments

@coilysiren
Copy link
Contributor

see: navapbc/platform-test#141 (comment)

@lorenyu lorenyu added the scope: service Service layer / component label Nov 8, 2024
coilysiren added a commit that referenced this issue Dec 3, 2024
## Ticket

Resolves navapbc/platform-test#140

## Changes

- Apply defaults to _"sender email"_ and _"reply to email"_
- Propagate `enable_notifications` throughout the configuration as it is
now being used
- Create the following modules:
- `notifications_email_domain`, meant to be deployed from `main`, which
deploys an DNS records in service of validating an email identity
- `existing_notifications_email_domain`, meant be deployed from
temporary environments, which uses data resources to pull from
`notifications_email_domain`
- `notifications`, used in both of the above cases, which deploys an AWS
Pinpoint application capable of sending emails
- Creates notification resources!

## Usage Context

Grants.gov plans to use this for "transactional" emails, eg. password
resets, status updates, etc.

## Context for reviewers

This will be followed up by:

- #789
- #778
- #777

## Testing

See navapbc/platform-test#141, specifically
navapbc/platform-test#141 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: service Service layer / component
Projects
None yet
Development

No branches or pull requests

2 participants