4 ms·
Title says that using a catch all domain (whatever that is) is a mistake, but the bulk of the article about it being a mistake to use the other party's company
by kazinator 4y ago
Title says that using a catch all domain (whatever that is) is a mistake, but the bulk of the article about it being a mistake to use the other party's company name as the local part of a throwaway e-mail address which you use for communicating with that party. There is nothing about the catch all aspect being a mistake. You don't have to give a Hilton hotel an address like hilton@example.com; it could be bob-2022-05@example.com, right?
I use a throwaway e-mail system whose generated addresses look like this: 539-343-1293@example.com. The dashes can be replaced by underscores or periods: all are recognized, but not mixtures of them: basically three versions of the every alias is installed. (Why? I ran into a situation where I had to enter my e-mail address into a point-of-sale system that didn't accept dashes.)
There is no "catch all" mechanism at play. Each address is explicitly created, using a web-UI application that I wrote. The moment you create it, it goes live, as a local alias recognized by the mail server.
Each such address is associated with its creation date, and a memo field. If the memo field contains URL's, they get rendered into navigable form. They are editable. The memo field is what tells me who/what the address is associated with. I have a regex search box to filter the entries (quite a lot have accumulated).
The UI is like Web 1.5: you can checkbox these items and do bulk operations on them, like bulk delete, move to top, move to bottom and such.
When I delete an address, it immediately stops working. THAT is why "catch all" would be a bad idea; if you have a rule which routes any nonexistent local part to your inbox then you don't have any easy way to turn off an address which is being abused, other than going into the mail server rules and writing a rule to reject that address. That's not a fun UX, compared to a nice throwaway address management dashboard.
This system is called TAMARIND: Throw Away Mail Alias Randomization Is Not Defeatable. :) :)
- bitexploder 4y agoFastmail also has features similar to this. Aliases and randomized masked email. The web ui helps you send email from the masked email as well.
- al_borland 4y agoiCloud+ has something like this as well. So far I've only used it with Sign In with Apple, or whatever it's called. Your comment led me to go check out the iOS Settings and it looks one-off random emails aliases can be made in there. Of course at this point my email is so many places it almost seems like a lost cause. What I wouldn't give to have a reset button for the entire internet. I would be much more careful with my address than I was 20 years ago.
- kazinator 4y agoTamarind is found here: https://www.kylheku.com/cgit/tamarind/tree https://www.kylheku.com/cgit/tamarind/tree It's a CGI application used with Apache. That code you see there does evrerything, using the raw HTTPS stream and environment variables from the server. There are no libraries, no web framework, nothing. - cookie handling / session persistence - generating HTML responding to requests - reading/writing e-mail aliases file - authenticating via IMAP or SASL
- bambax 4y ago> You don't have to give a Hilton hotel an address like hilton@example.com; it could be bob-2022-05@example.com, right? Sure, but then it's impossible to remember, or use for classification of incoming mail. Password managers can help with the first problem but not the second one.
- undefinedzero 4y agoYou can search by email in most password managers.
- bambax 4y agoYes but I'm talking about incoming email classification.
- kazinator 4y agoI don't understand. You can have filtering rules like "when a new message arrives with 12345@mydomain.com in the To: or Cc:, move mail to lists/foo-list folder".
- bambax 4y agoYes, but if you don't do it immediately you won't remember that 12345 means this or that company; and also yes, you can search for 12345 and see that all email coming to that address is from a certain company, but maybe they haven't yet sent any email, etc. Also if you use random strings that are not actually random (you just try to come up with something on the spot) you're very likely to reuse patterns for different third parties. In the end it's more "stateless" to have a simple rule to attach an email to a given company, than maintaining a separate reference list (or lists! one in a password manager, the other in your email client). But it's not very important, and mostly a question of personal preferences.