SMTP proxy or secure mail API credentials so instances can send email

[benallfree]

Can SES make a mail user and can we restrict sending from the pockethost.io domain only?

[benallfree]

SES does not do per-user quotas for IAM users. Instead, we need to implement an smtp proxy https://nodemailer.com/extras/smtp-server/

This is good though, because we can properly enforce:

• Sending from the instance's subdomain
• Sending ONLY to email addresses present in the users collection
• Limiting sending size and frequency
• Creating upgrade plans (100/day, 1k/day, etc)

[benallfree]

This one does feel important. Setting up email is a PITA. For the instances to really be viable, people need confirmation emails and pw resets. The only reason we haven't seen this yet is because nobody is in production.

[benallfree]

Another note: might be a good idea to proxy pockethost-central emails through an smtp proxy because if a verification email is sent and causes a hard bounce, SES will block it permanently. We need a way to un-block hard bounces in SES before resending verification emails. At least 10 times or something.

A user had an issue where his email address was not activated and then SES blocked it so he was stuck unable to verify his account.

[benallfree]

moved to roadmap