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

Open-source disposable email service

sorry.idont.date

Post reply on HN
Print view View original

61–69 of 69 posts

Re: Open-source disposable email service

#61

Post by themoonisachees »

solatic wrote: post #48

I imagine this domain will quickly end up on lists like this one: https://knowledge.hubspot.com/forms/what-domains-are-blocked... The real value here is the opening of the source code. Set up a cheap domain, set up a cheap VPS, use Tailscale or similar to keep the web UI private, then you're good.

You don't need such things.

You can simply register a domain on domains.google, and they give you email aliases with each domain. The trick is that while you are limited to 5 aliases, you can define the * alias and it will redirect any mail recieved at that domain. The mail then ends up in your mailbox, but you can easily block adresses that do too much while not breaking the workflow of recieving emails you want.

Re: Open-source disposable email service

#62

Post by 6sp »

themoonisachees wrote: post #61
solatic wrote: post #48

I imagine this domain will quickly end up on lists like this one: https://knowledge.hubspot.com/forms/what-domains-are-blocked... The real value here is the opening of the source code. Set up a cheap domain, set up a cheap VPS, use Tailscale or similar to keep the web UI private, then you're good.

You don't need such things. You can simply register a domain on domains.google, and they give you email aliases with each domain. The trick is that while you are limited to 5 aliases, you can define the * alias and it will redirect any mail recieved at that domain. The mail then ends up in your mailbox, but you can easily block adresses that do too much while not breaking the workflow of recieving emails you want.

Or even simpler register the domain on cloudflare and setup a catch all email address. Free to use the email forwarding service.

Re: Open-source disposable email service

#63

Post by solatic »

themoonisachees wrote: post #61
solatic wrote: post #48

I imagine this domain will quickly end up on lists like this one: https://knowledge.hubspot.com/forms/what-domains-are-blocked... The real value here is the opening of the source code. Set up a cheap domain, set up a cheap VPS, use Tailscale or similar to keep the web UI private, then you're good.

You don't need such things. You can simply register a domain on domains.google, and they give you email aliases with each domain. The trick is that while you are limited to 5 aliases, you can define the * alias and it will redirect any mail recieved at that domain. The mail then ends up in your mailbox, but you can easily block adresses that do too much while not breaking the workflow of recieving emails you want.

> but you can easily block adresses that do too much while not breaking the workflow of recieving emails you want.

Right, so this is a different use-case. You're talking about a usecase where you're not sure if you trust the site, but you may be interested in getting emails from them in the future, should they not violate that trust. You may even be interested in responding to the email. Fastmail also supports this with their masked emails.

OP's use-case is you're sure that you don't trust the site, you're sure that you're not interested in getting emails from them in the future, and you're sure that you will never reply. Therefore, you need an address that is entirely disposable. It's not quite the same thing.

Re: Open-source disposable email service

#65

Post by kevincox »

sigio wrote: post #57
hannob wrote: post #43

There's a security problem with this and many other such services. Writing this here hoping that this increases knowledge about this: I would be able to get a TLS certificate for this host. Why? Some TLS certificate providers allow verifying the domain via access to one of the privileged aliases like postmaster. So I could receive the verification token URL by looking at the postmaster inbox. Every service offering a…

A CAA dns record will most likely prevent tbat, just set it to your preferred CA tgat doesn't do mail-based validation.

This doesn't help if your preferred CA does mail-based validation. The attacker can just use the same CA that you do.

Re: Open-source disposable email service

#68

Post by avinassh »

mdaniel wrote: post #11

this is not "open source," it's source available as the repo is missing any licensing terms. I dunno what the legal standing is of these package management fields https://github.com/psarna/edgemail/blob/master/Cargo.toml#L5 > since I believe at least npm defaults to some very liberal license that almost no one looks at any further and puts a sibling license file in their repo with the actual terms Also, bold move imp…

I believe this comment prompted a discussion on the repo and now it has a valid license. So, that's a win

Re: Open-source disposable email service

#69

Post by mat_epice »

__MatrixMan__ wrote: post #41
mat_epice wrote: post #29

Earlier quoted context omitted.

Under "my email addresses" in settings, I have "*@example.com" as one of the entries. With this arrangement, fastmail properly fills in the appropriate example.com email address when I reply.

Oh I may have overlooked that, thanks.

It seems easy to miss. I've got multiple domains that I manage this way, and upon inspection at least one of them doesn't have this configured properly.
Post reply on HN