Open kaihendry opened 6 years ago
workaround:
I am no keen to have valid email addresses in the public seed script demo.sql.gz: this can get out of hand if abused or if mistakes are made
This change is to test emailing fuctionality we should not assume that this would be the default reason that people will have to install the Unee-T demo
that being said, the email address we use for the user is stored in the MEFE/Mongo DB so there is no point using the email address recorded in the BZ database.
Also the demo.sql.gz script does not seed anything in the Mongo DB so this would not help...
Mailinator is unreliable. Since I better understand how one can receive email with AWS SES, I think we should have test users that look like:
We can setup a rule on test so that mails are dumped in an indexed directory, e.g.
https://s3-ap-southeast-1.amazonaws.com/demo-email-unee-t/test/2018-08-17/
(or we could do a SNS, or a Webhook etc etc)
And from there we can inspect the emails that for example test+baz@demo.unee-t.com
received on the day of 2018-08-17.
Users should use https://www.mailinator.com/ email addresses, e.g. leonel@example.com -> leonel@mailinator.com so we can check notifications were sent successfully.
Currently if we send emails to example.com, we cannot check they were successful.