You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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
Out of scope
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.
The text was updated successfully, but these errors were encountered: