Third-Eye-Final-Year-Project VS 0x4447_product_s3_email

1. Download the Source Code from the Repo (https://github.com/imakashsahu/Third-Eye-Final-Year-Project) 2. Download and Install the Java JDK 8 (https://www.oracle.com/in/java/technologies/javase/javase-jdk8-downloads.html) 3. Download the latest NetBeans Installer (https://netbeans.apache.org/download/index.html) 3. Install and Open NetBeans 4. GoTo Tools > Plugin > Available Plugin 5. Search for "Java FX" and check "Gluon Plugin" & "JavaFx implementation for Windows" then click on Install 6. Now search for "Maven" and check "Gradle" then click on Install 7. Restart NetBeans

Here is something on GitHub that roughly follows this paradigm, and was made to use SES as the "email server".

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

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

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.

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

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

```