0x4447_product_s3_email
amail
0x4447_product_s3_email | amail | |
---|---|---|
15 | 3 | |
3,010 | 9 | |
0.1% | - | |
2.6 | 8.5 | |
4 months ago | 7 days ago | |
Rust | ||
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
0x4447_product_s3_email
-
Free VPS as SMTP Proxy
Here is something on GitHub that roughly follows this paradigm, and was made to use SES as the "email server".
-
Need any open-source alternatives?
- https://github.com/0x4447/0x4447_product_s3_email
-
Self-hosted email is the hardest it's ever been, but also the easiest
> 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.
- Lambda email system
-
Get email attachments directly into S3 bucket?
Based on your description I think this project is for you: https://github.com/0x4447/0x4447_product_s3_email - it dose what you are looking for, I hope this helps.
-
Need Help | Create serverless 'Email Service'
Here is a complete solution that hopefully gives you some ideas for a more simplified approach based on your needs. https://github.com/0x4447/0x4447_product_s3_email
-
Please fix the AWS free tier before somebody gets hurt
> What do you think about this page: https://aws.amazon.com/getting-started/
It is very dangerous. If you select the full-stack tutorial you get: "Time to Complete 30 minutes". It should say: "30 min to ruin your life" ;)
If you want to really learn AWS, then this page should be used as a reference of how to design a stack. If I were you I would read the tutorials to see which services are needed for a solution, but before doing anything, I would read the docs for each of those services to really understand them, then I would go back to the tutorial and actually do it, and - MOST IMPORTANTLY - I would read the pricing page for each service that you are going to use.
> Do you think it's irresponsible for AWS to encourage beginners to try their service when they apparently only intend it to be used by those with a computer science degree and 5-year apprenticeship under an experienced sysadmin?
100% - when I started working with AWS in 2016 I had a very hard time figuring it out, because I was looking for the simplicity the the marketing team was writing about. I really don't like what the marketing team tries to tell you, because it dose not exist.
Regarding an approach to learn about AWS, I would start with all the serverless services that they have, since the pricing for most of them is ideal for beginners (WARNING - read the pricing page for each since not all have a free staring plane, like S3 and DynamoDB) and for simple weekend projects.
For example, I did build this project a while ago: https://github.com/0x4447/0x4447_product_s3_email, if you scroll down to the pricing section you will see this:
```
- A serverless email server on AWS using S3 and SES
amail
-
Inbound MX / Email Relay Service?
https://github.com/OJFord/amail if you want to use it, but to be honest it's pretty simple, easily replicable if you prefer. (It's the 'lambda smtp relay' component.)
- A serverless email server on AWS using S3 and SES
What are some alternatives?
aws-nuke - Nuke a whole AWS account and delete all its resources.
go-localstack - Go Wrapper for using localstack
former2 - Generate CloudFormation / Terraform / Troposphere templates from your existing AWS resources.
node-pop3-emitter - POP3 server protocol layer for node.js
mCaptcha - A no-nonsense CAPTCHA system with seamless UX | Backend component
Apache - Mirror of Apache HTTP Server. Issues: http://issues.apache.org
MoonMail - Email marketing platform for bulk emailing via Amazon SES (Google Cloud Platform and Azure coming soon)
meli - 🐝 experimental terminal mail client, mirror of https://git.meli.delivery/meli/meli.git https://crates.io/crates/meli
aws-cdk - The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code
Listmonk - High performance, self-hosted, newsletter and mailing list manager with a modern dashboard. Single binary app.
himalaya - CLI to manage emails