How does it handle the scenario where the sender changes the domain they originate from? It may seem a bit unusual, like when a company rebrands (think of like Facebook originally sending from facebook.com, but then sending from meta.com later on).
edpin2000 11 minutes ago [-]
It doesn't right now. I'm thinking about options and so far all seem either "too much work" for the user. A few options:
1) a button to release the lock and allow the next sender to lock it again (only works for renames like you mention, facebook.com -> meta.com but not for apple.com and icloud.com sending together).
2) A button to manually add related domains. This is too much work because users can't guess new domains easily. I had betterstack.com email me as that and also as betterstackhq.com.
3) Allow up to 3-5 domains and let users block them manually. I feel this option is what permanent inboxes are for -- Clova already has an option to block entire senders (the whole domain or just a user).
4) Plugin some logic or AI in the backend to help categorize things together and understand that betterstack.com and betterstackhq.com are the same thing, apple.com, icloud.com etc are related, etc.
Anything else?
popupeyecare 8 minutes ago [-]
I have my personal domain (let's say johndoe.com) and I have set it up so all (catch-all) emails go to one email. chase@johndoe.com, att@johndoe.com. Pretty easy.
structief 1 minutes ago [-]
You must love all the spam you're getting with a catch-all!
drayfield 1 hours ago [-]
For context I'm sleep deprived so sorry if I've missed something obvious, but what differentiates this with something like Fastmail's masked email offering? I use unique emails for every service I use and it works beautifully. This seems... more complicated? I under there's a price difference, but little else.
edpin2000 1 hours ago [-]
It aims to be simpler. It's not a mask. It has forwarding as an option but the idea is that you can use one of the inbox types for different needs. The one I use the most is prefix, because you create it once and then you can tack on any suffix to it. When the first sender reaches you, that suffix become locked to their domain (or account, if it's a gmail, outlook, yahoo, etc). That seems pretty useful for subscriptions. For one-time codes, just create a temporary one every so often. It has the option to delete itself (and optionally take the email with it).
ssivark 1 hours ago [-]
Masked emails are infinitely shareable eg. a spammer can harvest that email address and then reach you. You don't typically have a setting to block anyone else (other than the original intended counter-party) from reaching you -- unless you set up some specific filtering rule (if that's even supported).
tmarice 1 hours ago [-]
I recently found out there is a limit to the number of masked emails you can have on Fastmail (1000, iirc -- definitely not infinite for practical purposes). Also, I miss the option of being able to create masked emails on all the domains I connected to Fastmail -- you can only use the "main" one.
aleksiy123 39 minutes ago [-]
I wanted to build this for phone numbers at some point but it was way outside of my skill level at the time.
I feel like unique address per sender, receiver pair could cut down on so much spam.
And you can see exactly who is leaking your info.
popupeyecare 10 minutes ago [-]
I built https://statphone.com which is one emergency number that dials multiple people and shows up as itself on the caller ID so you know it's urgent.
You can use the same tech to build throwaway accounts like you are envisioning. Problem is that it would be prohibitively expensive.
jlm66 2 hours ago [-]
Email, snail mail, text messages etc. all need, IMO, options for ONLY allowing incoming messages from known sources. This seems like it is really aiming to do that for Email and I applaud the effort. Hopefully, it will take off in a big, big way.
edpin2000 2 hours ago [-]
I hope so too. I hope I have the right set of features so far. Happy to hear thoughts and early feedback.
asdff 2 hours ago [-]
Email at least you can set this up with a rule that checks the sender against your contacts and throws them into some folder.
edpin2000 2 hours ago [-]
True. I find setting up rules and adding to contacts adds work to my day-to-day though. I'm hoping to make something simple and seamless. Prefix inboxes are as simple as I could think so far: make one up, add a suffix on the spot when you handout an email address -- boom, locked to the first one who uses it.
ssivark 1 hours ago [-]
Nice idea! JFYI, in case you ever run into design questions when extending this, you seem to be implementing a version of Object Capabilities (specifically revocable forwarders / caretaker pattern), specialized for the SMTP situation -- as you want to share with someone the capability to send you messages, but you want that capability to not be shared recursively.
Since you're also thinking about a user giving their agent access to their inbox -- any thoughts on what are the right capability primitives for that situation, and how the API & access tokens can represent that?
edpin2000 1 hours ago [-]
Agents can create new inboxes and inboxes can be of 3 types, besides "Permanent" which is just a regular inbox. The other types don't have "rules" that you can customize. Instead the rules are baked-in: Temporary -> expires after some time, One-sender: allows only one sender (the first one to prove its email identity), Prefix: similar to one-sender but creates a new inbox for every suffix (and if spammers catch on to the prefix, you can delete it and create a new one).
LewisOrton 19 minutes ago [-]
a unified solution for both old and new problems! such a nice idea. i liked gmail's "+" variant but yours are way cooler
another-dave 51 minutes ago [-]
this sounds really clever.
One suggestion - external contacts won't know that this address will bounce for anyone they add in CC. Maybe have an option where if I include the original whitelisted domain/person in the chain then it will let the mail through even if it's from a non-whitelisted person.
Just thinking of scenarios like, you give out your email address to <your-neighbour@gmail.com> who then emails you about a 5-a-side game with a few friends but any messages from any of the other friends bounce.
Or you apply for a job at ACME Inc and then you get a message back from `alice@acme.com` saying, please coordinate with `bob@our-recruiter-consultancy.com` who'll arrange the interview but Bob can't contact you
amflare 1 hours ago [-]
You can already do this with any normal email account. Just do myemail+whatever@domain.com. You can put anything you want behind the +, and it still works.
i.e. myemail+chase@domain.com, myemail+huffpost@domain.com, myemail+facebook@domain.com.
This used to be used as some sort of automatic labeling system that was supposed to be part of the spec eons ago, but it works just fine for generating unique emails so that you can see if/when an email has been leaked.
DoctorOW 1 hours ago [-]
I think the benefit is supposed to be the locking feature. Any human that sees myemail+chase@domain.com and wants to circumvent your filters to get to your main inbox (typically for sales purposes) can figure out to email myemail@domain.com. With this product, the email is undeliverable unless they label their emails correctly.
edpin2000 1 hours ago [-]
Exactly. Even bots can strip the "+" and bombard you with junk. With a prefix inbox you can invent any suffix. I have a "service" prefix that I add suffixes to it when I need: "service-netflix", "service$bank", "service.newsletter-1". I don't need to pre-create each one, only "service" is enough and then any suffix locks to the sender. They can't sell your email. And they may never know to invent a new suffix because they don't know where the prefix starts. You can make it "sdfawetr" if you want.
_djo_ 1 hours ago [-]
I assume spammers have become adept at stripping anything between + and @ in email addresses, so this isn't as reliable as properly masked addresses.
bch 1 hours ago [-]
The “x+tag@domain.com” format is also rejected by many validators, sadly. I thought this was a gmail feature, but was corrected[0][1] a while ago.
That's been my experience too. That's why prefix inboxes allow any suffix, including "-", "_", "$", "!" etc.
mkirsten 2 hours ago [-]
Nice and looks helpful. It’s crazy when you think about it - email is so prevalent in our lives, yet the scope of innovation last 20 years is that we can react to an emails with emojis.
mahboi 1 hours ago [-]
If anyone is reacting to my emails, I'm not seeing it, might be some vendor-specific thing. Which is fine, I don't want that.
What I really want is for unauthenticated senders to be reliably blocked. Even Gmail/Gsuite will allow spoofed emails from the same domain, though it may flag them as spam. I get that there are special circumstances where a legitimate sender can't authenticate itself, but that's their problem.
edpin2000 2 hours ago [-]
That's so true. Gmail used to be cool, now it's old and clunky and their "unsubscribe" feature does not do that reliably. I want to tackle that next, look at domains that continue to email people after they unsubscribe.
eosis 24 minutes ago [-]
Very cool.
I've used fastmail similarly for ages. An issue I have found is services that are really hung up on your email being your id, with annoying coupling like assuming you can only access a meeting if the email invite is the same "user" as the VC you're using...
xlii 2 hours ago [-]
I think I'm missing something but I've have an option to use <anything>@<ident>.domain.com for couple years now.
I don't find it that useful though and usually go with standard alias i.e. user+<anything>@domain.com
As for single sender locking - not sure how useful that is. I mean you can get github.com email or notifications.github.com so you miss half of them?
edpin2000 1 hours ago [-]
On the "+" sign comment: I find that many spammers already know the trick. That's why I built a prefix where any suffix will work. If you have "turtle" as a prefix, you can add "turtle$bank", "turtle-barber", etc on the spot, without having to create each suffix.
As for single sender, we attach to the domain, so *.github.com would be allowed. The main problem, to be honest, is when email comes from apple.com, icloud.com, applehq.com, etc. I'm considering a power-feature where you could pre-select a few domains or allow all and then lock it. I feel it would be best for power users only. What do you think?
hmokiguess 2 hours ago [-]
This is amazing, my dream has always been that outlook, gmail, and the likes allowed for setting up bounce rules.
edpin2000 2 hours ago [-]
Yes! And it can bounce/block any sender and entire domains too (across all your inboxes, if you choose).
cloudmanic 3 hours ago [-]
I have used this service since I found it on product hunt. I am loving it! My inbox is way cleaner now.
edpin2000 2 hours ago [-]
Glad to know it's working for you!
jambalaya8 44 minutes ago [-]
We used to do stuff like this for sysadmining scripts monitoring Unix boxes back in the 1990s. It worked great for escalation and automation with our alphapagers the way 'wfh' was back in like the mid90s; less laptop bootups :).
Rendered at 20:33:21 GMT+0000 (Coordinated Universal Time) with Vercel.
1) a button to release the lock and allow the next sender to lock it again (only works for renames like you mention, facebook.com -> meta.com but not for apple.com and icloud.com sending together).
2) A button to manually add related domains. This is too much work because users can't guess new domains easily. I had betterstack.com email me as that and also as betterstackhq.com.
3) Allow up to 3-5 domains and let users block them manually. I feel this option is what permanent inboxes are for -- Clova already has an option to block entire senders (the whole domain or just a user).
4) Plugin some logic or AI in the backend to help categorize things together and understand that betterstack.com and betterstackhq.com are the same thing, apple.com, icloud.com etc are related, etc.
Anything else?
I feel like unique address per sender, receiver pair could cut down on so much spam.
And you can see exactly who is leaking your info.
You can use the same tech to build throwaway accounts like you are envisioning. Problem is that it would be prohibitively expensive.
Since you're also thinking about a user giving their agent access to their inbox -- any thoughts on what are the right capability primitives for that situation, and how the API & access tokens can represent that?
One suggestion - external contacts won't know that this address will bounce for anyone they add in CC. Maybe have an option where if I include the original whitelisted domain/person in the chain then it will let the mail through even if it's from a non-whitelisted person.
Just thinking of scenarios like, you give out your email address to <your-neighbour@gmail.com> who then emails you about a 5-a-side game with a few friends but any messages from any of the other friends bounce.
Or you apply for a job at ACME Inc and then you get a message back from `alice@acme.com` saying, please coordinate with `bob@our-recruiter-consultancy.com` who'll arrange the interview but Bob can't contact you
This used to be used as some sort of automatic labeling system that was supposed to be part of the spec eons ago, but it works just fine for generating unique emails so that you can see if/when an email has been leaked.
[0] https://www.rfc-editor.org/rfc/rfc5233
[1] https://news.ycombinator.com/item?id=43952475
What I really want is for unauthenticated senders to be reliably blocked. Even Gmail/Gsuite will allow spoofed emails from the same domain, though it may flag them as spam. I get that there are special circumstances where a legitimate sender can't authenticate itself, but that's their problem.
I've used fastmail similarly for ages. An issue I have found is services that are really hung up on your email being your id, with annoying coupling like assuming you can only access a meeting if the email invite is the same "user" as the VC you're using...
I don't find it that useful though and usually go with standard alias i.e. user+<anything>@domain.com
As for single sender locking - not sure how useful that is. I mean you can get github.com email or notifications.github.com so you miss half of them?
As for single sender, we attach to the domain, so *.github.com would be allowed. The main problem, to be honest, is when email comes from apple.com, icloud.com, applehq.com, etc. I'm considering a power-feature where you could pre-select a few domains or allow all and then lock it. I feel it would be best for power users only. What do you think?