Maildog – Hosting email forwarding service on AWS with GitHub Actions
1–10 of 50 posts
Re: Maildog – Hosting email forwarding service on AWS with GitHub Actions
#2neat!
I usually just use gsuite + aliases/groups, which includes spam filtering, web console and a lot more. Granted, it's ~$6/mon, doesn't scale to 20,000 email addresses and you have to be cool with Google.
There something else I'm missing out on?
Re: Maildog – Hosting email forwarding service on AWS with GitHub Actions
#3This feels like it's pushing the TOS for Github Actions a bit by using it for post deployment, live operations. Like the hourly health check and your dead letter queue scheduler.
It made me curious, so I looked at their TOS[1], and they seem somewhat permissive about things like this. Though vague about where/when you cross the line.
Like, this seems clear:
"should not be used for...any other activity unrelated to the production, testing, deployment, or publication of the software project associated with the repository where GitHub Actions are used."
But then:
"but a low benefit Action could be ok if it’s also low burden"
[1] https://docs.github.com/en/github/site-policy/github-terms-f...
Re: Maildog – Hosting email forwarding service on AWS with GitHub Actions
#4Seems like a lot more hassle than using purelymail[0] for $10 a year, which has full Sieve and SpamAssassin and sub-addressing.
Re: Maildog – Hosting email forwarding service on AWS with GitHub Actions
#5Somewhat off topic but how does one make that cool 3D architecture diagram?
Re: Maildog – Hosting email forwarding service on AWS with GitHub Actions
#6[deleted]
Re: Maildog – Hosting email forwarding service on AWS with GitHub Actions
#7Would be more accurate to say "Hosting your own email forwarding service on AWS", as the README does. The GitHub Actions piece is for managing it.
Re: Maildog – Hosting email forwarding service on AWS with GitHub Actions
#8Somewhat off topic but how does one make that cool 3D architecture diagram?
Re: Maildog – Hosting email forwarding service on AWS with GitHub Actions
#9This feels like it's pushing the TOS for Github Actions a bit by using it for post deployment, live operations. Like the hourly health check and your dead letter queue scheduler. It made me curious, so I looked at their TOS[1], and they seem somewhat permissive about things like this. Though vague about where/when you cross the line. Like, this seems clear: "should not be used for...any other activity unrelated to th…
Also note that Github will deactivate cron actions if there is no activity in the repo for 60 days.
https://github.community/t/do-disabled-scheduled-workflows-r...
Re: Maildog – Hosting email forwarding service on AWS with GitHub Actions
#10Seems like a lot more hassle than using purelymail[0] for $10 a year, which has full Sieve and SpamAssassin and sub-addressing. 0. https://purelymail.com/pricing
This is great! Thank you.
There is also https://forwardemail.net/ which is a different service.