A serverless email server on AWS using S3 and SES

• 0x4447_product_s3_email

  15 3,012 2.6

  📫 A serverless email server on AWS using S3 and SES

  

• amail

  3 9 8.4 Rust

  AWS-hosted personal email system: sending, receiving, storage, and forwarding (relaying). `notmuch` client. JMAP server WIP.

I do something similar to OP [0] - and currently forward to another provider (single address, but that's only the 'envelope' To; so it doesn't matter, I preserve the original whatever.to.address).

That's mostly an artefact of transitioning from that provider to my own on AWS, but I stopped working on it for some time and never continued. My plan was/still is to write a client that can read 'Just a Bunch of .Eml' format, and then I can point that at S3 (or via S3FS or whatever). Everything that exists for mailbox, maildir, and what-have-you assumes you need it to act as an MTA (I think that's right) and do the actual receiving too; and is difficult/impossible to stop that and say 'no, here's a directory full of email, just be a reader'.

Longer-term plan/idle thought is to have a JMAP server on Lambda. (IMAP isn't possible, because it has to look like/be HTTP to reach the Lambda.)

[0] - https://github.com/OJFord/amail

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• aws-cdk

  264 11,245 9.9 TypeScript

  The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code

  

This is really interesting! Currently trying to solve a similar problem thing myself, so having a look through to learn from your solution.

I'd recommend having a look at AWS CDK to manage the AWS resource creation, is much nicer than raw CloudFormation: https://github.com/aws/aws-cdk/

For my solution to this I've also then got a frontend ontop of my backend to setup view mailboxes, email list per mailbox, email viewer (read/unread status), and email sending. I'm doing the same with S3/SES/Lambda + DynamoDB for email sending/recieving/processing + email metadat in DynamoDB. Mine is currently WIP and needs some real auth (using a URL API key, not the most secure...) + email replying + tidying up. Will definitely open source my solution and post to HN when ready.

• Apache

  82 3,445 9.3 C

  Mirror of Apache HTTP Server. Issues: http://issues.apache.org

  

I'm surprised you need a source for this. Literally half of the server software out there refers to itself as " server".

Apache [1] "The Number One HTTP Server On The Internet". This is not referring to the machine hosting, it's referring to the software that you run to provide a service.

Postfix [2] "mail server"

IIS [3] "Web server"

I could go on...

[1] https://httpd.apache.org/

[2] http://www.postfix.org/

[3] https://www.iis.net/

• node-pop3-emitter

  1 2 3.8 JavaScript

  POP3 server protocol layer for node.js

You could probably cobble together a POP server on top of S3 pretty easily (e.g. using something like https://github.com/femto113/node-pop3-emitter which I threw together a couple years ago for a related purpose). I'm not sure if you can get it to work in Lambda though because the POP3 protocol needs sockets, but you could definitely get it to work in a simple container in Fargate (so still "serverless").

• SaaSHub

  www.saashub.com featured

  SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

  

Suggest a related project