Email Server

[thomasdavis]

We will need to send emails on behalf of users.

It will be a node.js server, using mongodb.

When an email gets sent from the site, we need to store it and send out a confirmation email to the user, once they confirm their email, we will send the email they queued up then delete the stored email. We will only store data temporarily, and won't be adding emails to a mailing list.

We could potentially skip the double opt in process

[davidbanham]

Here is a thing I wrote a while ago to fulfil a similar need:

https://github.com/piniontech/formail

Questions, though:

What is the opt-in for? Are you thinking you'll send the email as coming from [email protected] ? Because that is a problem for deliverability. The email will still actually be coming from [email protected] and if you attempt to impersonate a user's address it will get stopped by most spam filters. You could send it on behalf of [email protected], but that isn't quite the same thing.'

The problem I think you'll have with that approach is that it's all too easy for the recipients to set a rule saying (IF sender LIKE *@stopthespies.com THEN send it to /dev/null).

I think we do want them coming from actual people's actual addresses if possible. The happy thing is that it's actually much simpler to do that.

<a href="mailto:[email protected]?subject=Stop%20the%20spies!&body=I%20do%20not%20like%20this%20new%20legislation%20at%20all.%20Please%20stop%20it.">Send email</a>