Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Maildog – Hosting email forwarding service on AWS with GitHub Actions

github.com

Post reply on HN
Print view View original

11–20 of 50 posts

Re: Maildog – Hosting email forwarding service on AWS with GitHub Actions

#12

Post by jtolj »

fiatjaf wrote: post #10
Thev00d00 wrote: post #4

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

Was just about to post this. I've been using it from the beginning for all of my "pre-launch" domains and it has been flawless.

Re: Maildog – Hosting email forwarding service on AWS with GitHub Actions

#14

Post by alisonkisk »

asah wrote: post #2

neat! 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?

Yours isn't a DIY hack for fun.

Re: Maildog – Hosting email forwarding service on AWS with GitHub Actions

#15

Post by OJFord »

Fileformat wrote: post #9
tyingq wrote: post #3

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

But you do get an email warning you, with a button to say 'no, keep going'.

(I maintain docker images for gocryptfs & mergerfs - https://github.com/OJFord/docker-gocryptfs https://github.com/OJFord/docker-mergerfs - that check for updates to those respective projects and push an updated image; if there's no new upstream version for a while then I get that email and have to click it to keep it running.)

Re: Maildog – Hosting email forwarding service on AWS with GitHub Actions

#16

Post by dabeeeenster »

jasongill wrote: post #13
nathancahill wrote: post #8

Earlier quoted context omitted.

https://www.cloudcraft.co

very cool looking but a bit hard to read, at least in the maildog readme

Totally! The isometric view is impossible to read.

Re: Maildog – Hosting email forwarding service on AWS with GitHub Actions

#20

Post by psanford »

kelt wrote: post #18

Taking Amazon SES to production can be a little tricky, I think I am talking to robots with templated messages. Maybe I don't have luck or didn't explain myself well enough.

I didn't have any trouble with getting them to enable production mode SES for my personal email domains. The only thing I can think of that might have helped me (besides making it clear I wasn't using this for marketing emails) was that my AWS account had been open and in good standing for quite a while before enabling SES.
Post reply on HN