aws-lambda-ses-forwarder

> 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 pric

SES for outgoing works pretty nicely, I don't think I ran into any gotchas. You can use SES for inbound email receipt as well, but unfortunately there's no POP3/IMAP service (emails just get stored in an S3 bucket). However you can use a Lambda to forward inbound email to a personal email account: https://github.com/arithmetric/aws-lambda-ses-forwarder

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 ``` For example, if an email sent by Jane Example <jane@example.com> to info@example.com is processed by this script, the From and Reply-To headers will be set to: From: Jane Example at jane@example.com <info@example.com> Reply-To: jane@example.com To override this behavior, set a verified fromEmail address (e.g., noreply@example.com) in the config object and the header will look lik

Another alternative is https://github.com/arithmetric/aws-lambda-ses-forwarder which is purely AWS lambda based. I used to use it before now. Now, I run my own email forwarding service at https://hanami.run to expose a nice UI and a Rest API so I can `curl` my emails.

I have this set up couple years ago via this lambda function: https://github.com/arithmetric/aws-lambda-ses-forwarder It may look outdated, but it still functions well for me

Here is the script I've been using [1]. [1] https://github.com/arithmetric/aws-lambda-ses-forwarder