Show HN: Heimdall – Self-managed email alias/forwarding service
41–50 of 54 posts
Re: Show HN: Heimdall – Self-managed email alias/forwarding service
#42I’m confused. Why do you want this? You don’t trust a provider to forward your email? Email isn’t a trusted method of communication anyway.
Providers usually don't give you (unlimited number of) aliases.
Re: Show HN: Heimdall – Self-managed email alias/forwarding service
#43I wrote and use a web service called Tamarind for managing throw-away mail aliases: http://www.kylheku.com/cgit/tamarind/tree/README It integrates into Apache as a CGI program serving up a web UI for managing your aliases. It works by managing the content of an alias file read by your mail server. Authentication of the webUI is via IMAP or SASL. Each throw-away alias is associated with a memo in which you can have te…
If you want to Show HN something, make your own post; this is just rude.
Re: Show HN: Heimdall – Self-managed email alias/forwarding service
#44I’m confused. Why do you want this? You don’t trust a provider to forward your email? Email isn’t a trusted method of communication anyway.
Providers usually don't give you (unlimited number of) aliases.
Re: Show HN: Heimdall – Self-managed email alias/forwarding service
#45Earlier quoted context omitted.
We don't run our own infrastructure anymore :(
Yeah and seems like the big providers don't like self hosted emails. I know someone who runs a hosting company using cPanel and his clients email go to spam a bunch even though not spammy emails, his answer is to just pay extra for Google Apps and that running a email server is too complicated. Not sure how true that is... For my own future projects I plan to run everything in containers, Node, etc so not PHP/MySQL s…
Re: Show HN: Heimdall – Self-managed email alias/forwarding service
#46Earlier quoted context omitted.
Yeah and seems like the big providers don't like self hosted emails. I know someone who runs a hosting company using cPanel and his clients email go to spam a bunch even though not spammy emails, his answer is to just pay extra for Google Apps and that running a email server is too complicated. Not sure how true that is... For my own future projects I plan to run everything in containers, Node, etc so not PHP/MySQL s…
I can't even get my PAID Gmail address to hit people's inbox >90% of the time....the state of things is awful, and we need a reset.
I'm far from shipping from what I'm working on though, but before going live want to get email setup for the main company website and product website for me and future staff, then want to be able to send email's for notifications, password resets, etc and then also have scripts receive and parse emails for replies to put into a database for the support portal part of the product domain but getting ahead of myself. Not sure if the product site would have users to people or just be all scripted sending/receiving while the main site is mostly emails hosted for humans.
I think one strategy would just run a mail server and have a script download the emails to the database and delete them, since doubt many solutions support a more of a webhoook type setup.
Re: Show HN: Heimdall – Self-managed email alias/forwarding service
#47> Known Limitations > Currently, attachments are not supported. That's kind of a biggie. What happens when someone sends an attachment? Does it bounce? Are they warned? Do I get a notification? Is it silently dropped? From reading the code it seems like it just doesn't include the attachment and then deletes it from S3?
Right now, silently dropped. Yeah, this is an issue I'm planning to work on. The reason I chose to release it before supporting attachments is that for my use case for receiving marketing emails (this project is primarily for my personal use, rather than as public software), there are almost never attachments.
Re: Show HN: Heimdall – Self-managed email alias/forwarding service
#48This is a really cool project, so I don't mean to be overly negative, but personally this workflow feels quite a bit more laborious than just having a catch-all email address. Before signing up for a service, I need to email myself to get an address to use for the service? I have all emails for my domain route to me, so when I use a service I just do [service-name]@my-domain.com. If a bad actor gets a hold of it I se…
You're going to get an astronomical amount of junk mail with a catchall email address. Google is great at filtering spam, but not perfect. If you're running your own mail server, you're going to have a hard time dealing with it, even if you use SpamAssassin and other tools. It's also going to get worse over time, because every address that accepts delivery is going to get added to a database for future spamming. I us…
Re: Show HN: Heimdall – Self-managed email alias/forwarding service
#49Earlier quoted context omitted.
> Unless you physically own a server you have to put your data somewhere, whether that somewhere is Digital Ocean, some shared hosting provider, AWS, or whatever else. You're still more in control of your data than you would be using a closed third-party product. The claim was not "you are more in control than with a closed third-party product". The claim was "No [...] having to trust a third-party company with your…
No, you're not misunderstanding. I guess I made that statement with the implicit trust of AWS so I didn't think to qualify it. You're absolutely right that if AWS is a bad actor it has access to all the information, but I'm working on the assumption that it's more profitable to AWS to be a good actor than bad.
Re: Show HN: Heimdall – Self-managed email alias/forwarding service
#50Earlier quoted context omitted.
We don't run our own infrastructure anymore :(
Yeah and seems like the big providers don't like self hosted emails. I know someone who runs a hosting company using cPanel and his clients email go to spam a bunch even though not spammy emails, his answer is to just pay extra for Google Apps and that running a email server is too complicated. Not sure how true that is... For my own future projects I plan to run everything in containers, Node, etc so not PHP/MySQL s…
WordPress contact forms are routinely abused - I regularly see forms where enter a victim as "my address" and then it helpfully copies the message to the spam recipient. There's always a web designer who wants it this way for UX reasons, even when I shown how it's abused.