aws-lambda-ses-forwarder VS MJML

If they cannot use cloudflare(since we need to use its nameserver), you can self hosted a tool like https://github.com/arithmetric/aws-lambda-ses-forwarder It's powered by AWS Lambda so work flawlessly.

> Could there be a serverless alternative where the service wakes up only to receive emails and will be charged only when emails are processed, filtered and served & rest of the time no charge - avoiding $3 to $5 charged by behemoths per inbox?

I love ideas as much as the next guy and serverless email is kind of floating out there:

https://medium.com/schibsted-engineering/building-a-serverle...

https://github.com/arithmetric/aws-lambda-ses-forwarder

https://github.com/0x4447/0x4447_product_s3_email

It's possible to build it, but the problem is that you still have the same problem of deliverability. Obviously it works fine/great for receving emails though.

> Idea is how cheap can it go for personal inbox with all the features denied by the superlative pricing plans

It could get really cheap, but would people buy it? I always wonder if price is really the limiting factor for self hosted emails.

Zoho is already QUITE cheap: https://www.zoho.com/mail/zohomail-pricing.html

Maybe this would work as a business, but it's a bit questionable to me.

When using SES, you cannot set FROM header to anything. The FROM has to be either an whitelisted email address or a domain that you own and verified with SES.

When forwarding email, we are receiving email from unknow domains. If we rewrite the FROM headers then the DKIM will invalid, so service will have to rewrite the FROM and clear out DKIM.

This is a well-known SES issue and project has to work around https://github.com/arithmetric/aws-lambda-ses-forwarder

```

If you are willing to mess around with code https://github.com/arithmetric/aws-lambda-ses-forwarder use this. It's essentially use AWS SES to process inbound email and lambda to forward email out.

It is unmaintained https://github.com/arithmetric/aws-lambda-ses-forwarder/issues/119 and written in godawful JS promise syntax. So while it may work, I didn't feel like trying it.

Thanks to Joe Turgeon for inspiration of the tutorial: https://github.com/arithmetric/aws-lambda-ses-forwarder

I am using MJML and it’s relatively easy to build your described layout with snippets from the docs.

https://mjml.io/

Last time I had to deal with emails, I've used https://mjml.io/ and was very happy with it. You can version the templates, compile them as part of your build pipeline and it seems to do produce very _adequate_ HTML full of tables that looks good on all clients that we tested.

I suggest you look at https://mjml.io and see if their code holds better after forwards.

I use mjml https://mjml.io/ and like it pretty much

Yes, but email is a disaster to build from scratch. I ONLY build email using MJML. If you know html and css you will catch on quickly!

But why use React to do that when you can achieve the same thing on the backend?

https://mjml.io/

I use a foundation framework for emails to build Newsletters. https://mjml.io/