i use -sub@mydomain.ext. makes it clear what it's supposed to be for.
Using a catch-all domain is a mistake
261–270 of 304 posts
Re: Using a catch-all domain is a mistake
#262Earlier quoted context omitted.
> 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.
You can search by email in most password managers.
Yes but I'm talking about incoming email classification.
Re: Using a catch-all domain is a mistake
#263lmao when u cant remember the email used, you should probably consider using a password safe
Re: Using a catch-all domain is a mistake
#264Earlier quoted context omitted.
That is a major downside with putting gibberish in for answers to security questions… let’s hackers socially engineer support into letting you get access by saying something like, “oh man, I just mashed on my keyboard for that I don’t remember!” You would hope it wouldn’t work, but it probably will.
That’s a good point. It’s better to use wrong but plausible answers or random sentences (some password managers can generate phrases from a word list)
or even better, use some random non-words. There was a post here a few months back about a service which generated non-existent but plausible sounding words.
So, your "favorite city" could be i.e. HorsecrackBay Griennstone.
Re: Using a catch-all domain is a mistake
#265I also use a catch-all e-mail address, and I have no regrets.
I should say, though, that I've not yet caught any database leaks, yet.
Re: Using a catch-all domain is a mistake
#266I've been using a catch-all email routing setup for many years. I use unique breach canaries to maintain this list of companies that have sold or leaked my personal data to unauthorized parties: https://gist.github.com/eligrey/5084991
Re: Using a catch-all domain is a mistake
#267Earlier quoted context omitted.
"Simply update your address with the post office and you're done." Welcome to the 19th century! Which is when mail redirection to a new address was introduced in the UK. I'd be amazed if it wasn't around then or earlier in the USA as well. Simply fill out a form and your mail will be redirected for up to two years (albeit at a cost). Or use a PO box and a mail forwarding service which offers filtering of junk mail. I…
> Welcome to the 19th century! Which is when mail redirection to a new address was introduced in the UK. That’s not the same thing. Everyone still has your old address and you need to update it with them. Not terribly painful if you move once every 5 years. Pretty annoying and error prone if you move every 6 months.
Hence option 2 - the PO box.
Re: Using a catch-all domain is a mistake
#268I do this and it keeps my main inbox nice and clean.
In the case where I have to reply, Google allow you to set up a from email which you can use from your spam trap account. So if you need to send an email as banana@domain.com it's a few clicks away
Re: Using a catch-all domain is a mistake
#269Earlier quoted context omitted.
> Email should have always been a bidirectional address, representing the relationship between the sender and receiver, and not a wide open receiver for anybody who happens to have your address. That does seem beneficial for the most part, but do you have ideas about how to handle the use cases like establishing new relationships (what, if anything, do you put on business cards?) or allowing the general public or a b…
The email service Hey (from the makers of Basecamp) has a feature where the first time someone emails you it goes into a screening bucket. You can then approve those senders who are allowed to email you. If you don't approve, you don't see the emails anymore. I initially signed up for the trail when the service launched. The first or second time I went to check the site/app it wasn't working. I was pretty much done w…
I effectively do this manually in Thunderbird. I have a saved search folder I treat as my "actual inbox" and I only add email addresses I want to receive mail from to the filter rule list.
Re: Using a catch-all domain is a mistake
#270Earlier quoted context omitted.
> Email should have always been a bidirectional address, representing the relationship between the sender and receiver, and not a wide open receiver for anybody who happens to have your address. That does seem beneficial for the most part, but do you have ideas about how to handle the use cases like establishing new relationships (what, if anything, do you put on business cards?) or allowing the general public or a b…
Actually, centralized databases like DNS are a symptom of a larger problem: society is so used to the idea that you can centralize power, votes, money etc. in one place. It is why we have celebrities and state governments, and privately owned social networks. It is also why smart contracts are still based around blockchains and they allow weird things like flash loans, because only one transactiom can run at a time f…
Better except that it completely and fundamentally breaks the internet as a side effect.