Research using SES to see if an email arrives successfully at the recipient's inbox

[allly-b]

Issue description

We use AWS SES to send emails in org model and non org model. When we send emails we log if there is an error, however, SES counts the ".send" command successful if it was sent to the ses system correctly and can be forwarded (ie not flagged as malicious, has all minimum data needed etc). However, if the email bounces because the email is not valid we do not get any indicator with our current setup.

We may eventually want to display if an email failed to send due to a bounce back, or at the very least we should log in Opensearch that a bounce back occurred.

This ticket is simply for investigating how we can get information from AWS ses to see if a particular email bounced or reached the recipient successfully.

Acceptance criteria

• read the aws ses documentation and any relevant documentation
• investigate how we should could modify our code so that we know if an email reached the recipient successfully or if it bounced (and log accordingly)
• write a dev ticket for logging email success/failure and include how this should be done in the "additional context" of that ticket
• have a lead review the ticket and the suggested approach as part of the review
• time box to 2 days, if it takes more than that discuss with a lead

No code/ implementation is needed here.

Additional context

AWS SES monitoring sending activity page could be useful to read as part of this as it discusses the dev requirements for monitoring what happened the email that was sent. There are multiple states it mentions but the most important ones for us to look at is Delivery & Bounce. Note, some of the related links have examples of how to get all the statitics for emails sent, we don't want that, we only care about the success/failure of each email we are sending and would want to be able to easily correlate which emails failed vs succeeded.

@katypies if you have other suggestions you have here. I think you mentioned something regarding "states".

Links to other issues

No response

[allly-b]

Soft loading into sprint 66, since this is just a research ticket, better to do it early then we can plan the follow on activities accordingly. Candidate to move out if we need to lighten the sprint