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

Analyze how to allow from addresses of other domains #259

Open
Tracked by #584
SandGrainOne opened this issue Oct 5, 2023 · 0 comments
Open
Tracked by #584

Analyze how to allow from addresses of other domains #259

SandGrainOne opened this issue Oct 5, 2023 · 0 comments
Labels
area/infrastructure Issue originates as changes to infrastructure kind/analysis

Comments

@SandGrainOne
Copy link
Member

SandGrainOne commented Oct 5, 2023

Description

The notification service should allow the application owner to set their own email address as the sender of an email. To enable this we need a good way to support some of the different mechanisms put in place to prevent misuse of well known domains in spam or phising attempts.

In scope

  • Understand what the different mechanisms means and explain them to the team
  • Find out if there are other things we need to look into
  • Attempt to find a possible solution where we still use Azure Communication Services
  • Perform simple tests of possible solutions where needed
  • Document a possible procedure

Out of scope

  • Avoid looking into other products for now
    • We'll create a new issue to look for alternatives if we're unable to resolve this using Azure Communication Services.
  • Avoid spending too much time implementing a solution
    • Create new issues instead

Additional Information

No response

Analysis

No response

Conclusion

No response

Threat modeling

This is not an implementation issue. It's also a security focused issue in itself, finding out how we can best operate as an email provider in the best possible way.

@SandGrainOne SandGrainOne added status/draft Status: When you create an issue before you have enough info to properly describe the issue. kind/analysis labels Oct 5, 2023
@SandGrainOne SandGrainOne added area/infrastructure Issue originates as changes to infrastructure and removed status/draft Status: When you create an issue before you have enough info to properly describe the issue. labels Oct 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/infrastructure Issue originates as changes to infrastructure kind/analysis
Projects
None yet
Development

No branches or pull requests

2 participants