News for hackers. Stuff that matters.
Re:Using a catch-all domain is a mistake by dzek69 on Wednesday June 01, 2022 @06:48PM (#31589133)
I'm using catch all since forever. I regret nothing.

Two stories:

I don't use mails like facebook@domain uber@domain - that's too obvious. And knowing that may often disclose that I actually have an account registered on given page. I don't want that, so I go full random, using few words I have in mind, current few words from the song I'm listening too, etc. So password manager helps me with e-mails too.

But Sometimes when a website annoys me (stupid rules for passwords, crippled UX for forms, because re-writing a select component in javascript is such a brilliant idea, etc) I tend to insult the company I'm registering with using my e-mail or password, I mean mail: [email protected] and pass: goDieInPain1312323$$$$. Once I registered account for a supermarket loyality card with some very little insult towards the supermarket. Later I got some huge amount of the points collected and their system crashed and I had to contact the support (the bonus was too high for me to give up on that). First via e-mail then via phone, when they were confirming my address. They helped me and said nothing about the name I was using.

Another story:

When I started with catch-all I was actually using mails like companyname@mydomain, and when I once contacted them via phone the person talking with me was not very into tech I think and were accusing me of... I don't really know exactly, but she told me something about me using their stuff without their acceptance, when I tried to explain that's my own domain she told me I cannot use their name, because that's a copyright infringement. Weird.

Re:Using a catch-all domain is a mistake by mixologic on Wednesday June 01, 2022 @07:14PM (#31589355)
I have been using a catchall domain since 2004 and it has been a lifesaver.

The sad part is when your email leaks from big companies, you definitely know. I started getting viagra spam delivered to [email protected] back in 2007, long before their "big data breach", so it was only a matter of time before that companies pattern of poor security caught up with them.

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.

Re:Using a catch-all domain is a mistake by schoen on Wednesday June 01, 2022 @08:44PM (#31589991)
> 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 broad audience to contact you (what, if anything, do you put in advertisements, on your web site, on slides of a conference presentation, in an e-mail signature on mailing lists?).

Re:Using a catch-all domain is a mistake by test6554 on Thursday June 02, 2022 @12:11AM (#31591242)
Phone numbers too. Can you imagine if you could give out a different phone number to each company and you could put a call limit, allowed call times, as well as a date expiration on the phone number you gave out. It could all be linked to specific companies, where if you got a spam call, you could report it and the company you entrusted it with would get a fine, or possibly the call would simply not go through.
Re:Using a catch-all domain is a mistake by efreak on Thursday June 02, 2022 @02:10AM (#31591925)
Google voice allows you to set what times it will forward numbers, so that gives you a second 'group' of contacts you can assign call times to (give them your voice number, allow them through do not disturb if necessary). It rather surprises me that there's no app for granular ringtone settings to allow calls from certain contacts only at certain times or on certain days.

- allow work calls and disallow family calls 9-5 weekdays only - allow family calls but not work calls to bypass do not disturb by ringing a second time - allow annoying acquaintance who wants tech support to only call on weekends, and to only ring on second call - if working two jobs, prevent each workplace from calling during other workplace's scheduled hours - add geofencing. don't allow community/neighbor calls while at work.

Basically, just add rules for each contact/group for when your phone will ring. Android used to have multiple sound profiles available, and IIRC allowed you to change the volume and default ringer, these could be activated automatically on a schedule. Now we only have Do Not Disturb, and that's it.

Re:Using a catch-all domain is a mistake by al_borland on Wednesday June 01, 2022 @11:40PM (#31591048)
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 with it at that point. I probably should have given it more of a chance and maybe they worked that out, but at $99/year for email my tolerance for issues is pretty low. They did (I suppose still do) have a lot of neat ideas around email though.

Re:Using a catch-all domain is a mistake by Dyac on Thursday June 02, 2022 @06:38AM (#31593323)
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 by hunter2_ on Wednesday June 01, 2022 @11:45PM (#31591080)
I think it's simply a hybrid approach: you'd handle those unknown contacts with many:1 addresses (since there's no real alternative, as you imply), and you'd handle most known contacts with 1:1 addresses.

A benefit is that you might let messages to some or all of those 1:1 addresses be sorted one way (e.g., they ping you) while messages to some or all of the many:1 addresses are sorted another way (e.g., you only check for them with a much longer interval). But then again, a diligently-maintained contact list can be leveraged to achieve same...

Re:Using a catch-all domain is a mistake by ben0x539 on Thursday June 02, 2022 @01:10AM (#31591572)
To take the tracking logic further, I think you'd do `businesscard-<date for that particular print run>@example.com`, `<name of conference>-<year>@example.com`, `<name of mailing list>@example.com` etc. Maybe come up with something snazzy yet still unique-ish for the presentation slides.

In practice, I suspect the intention is mostly to use catch-all addresses for situations where the email address is a key in a database and like a login and stuff and not an entry in an individual's contacts list.

Re:Using a catch-all domain is a mistake by EGreg on Wednesday June 01, 2022 @11:58PM (#31591161)
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 for the whole world.

So the problem is that [email protected] or [email protected] is accessible to anyone who can use the SMTP protocol. And a phone number is accessible to anyone who texts it. That’s crazy.

Instead, we shouldn’t have DNS or centralized domains at all. DNS is just a glorified search engine that only really helps you find the root resource at a site, the /index.html thing. The vast majority of URLs on the Web aren’t going to be verbally shared anyway so you may as well store them as non-human-readable strings and let people save some local or hosted index. The titles and other metadata can be taken just like google does.

In this case, sending an email would require the recipient to have given out a capability that was received by you. And if some capability was compromised, they’d just deactivate it. It’s like this dude’s email aliases, but far better

Re:Using a catch-all domain is a mistake by thfuran on Thursday June 02, 2022 @07:24AM (#31593597)
Better except that it completely and fundamentally breaks the internet as a side effect.
Re:Using a catch-all domain is a mistake by vorpalhex on Thursday June 02, 2022 @12:25AM (#31591336)
[email protected]

Or if for a specific forum - [email protected]

Re:Using a catch-all domain is a mistake by MiddleEndian on Wednesday June 01, 2022 @08:42PM (#31589982)
>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.

Ideally, this would also be the case for physical mail. Multiple revokable tokens, not publicly tied to your physical address.

Re:Using a catch-all domain is a mistake by al_borland on Wednesday June 01, 2022 @11:45PM (#31591077)
Not having your mailing address tied to your physical address would also have major benefits when people move. Simply update your address with the post office and you're done.

The whole idea of revokable tokens would pose an issue for any company that sends bills, as I assume revoking address tokens would be common with them. I'm sure there are many situations like this.

Re:Using a catch-all domain is a mistake by r_hoods_ghost on Thursday June 02, 2022 @03:17AM (#31592320)
"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 used one for years when I used to move around a lot for less than £100 a year.

Re:Using a catch-all domain is a mistake by kortilla on Thursday June 02, 2022 @03:41AM (#31592444)
> 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.

Re:Using a catch-all domain is a mistake by r_hoods_ghost on Thursday June 02, 2022 @04:43AM (#31592745)
Hence option 2 - the PO box.
Re:Using a catch-all domain is a mistake by kortilla on Friday June 03, 2022 @03:29AM (#31605294)
Which is rejected as a valid address by many banks, government forms, etc. I want something that the post office guarantees has a real person behind it so I can use it for literally everything that requires an address.
Re:Using a catch-all domain is a mistake by MiddleEndian on Thursday June 02, 2022 @09:41AM (#31594752)
I do this, any bureaucratic organization that I want to be able to reach me (very very few) gets my PO box, which has remained the same across three addresses.
Re:Using a catch-all domain is a mistake by al_borland on Thursday June 02, 2022 @12:06PM (#31596598)
The US has mail forwarding for 1 year, but that doesn't solve the problem, as you still need to update the source information with all the companies. I usually end up spending several hours changing addresses when I move. It's better to do this right away than to rely on the forwarding completely. Some places get the change of address info automatically and update their records, but it's never the ones you actually want (usually catalogs and marketing mail).

A PO box would be fine, but it's not an acceptable address with many businesses, so it's not a universal solution to the problem.

Re:Using a catch-all domain is a mistake by MiddleEndian on Thursday June 02, 2022 @09:51PM (#31603272)
A workaround for some forms that don't accept PO Boxes:

Type something like P0 B0X

Type the address of the post office and then the PO Box number like an apartment number

Re:Using a catch-all domain is a mistake by test6554 on Thursday June 02, 2022 @12:10AM (#31591237)
Dang, you could trade stocks with information like that.
Re:Using a catch-all domain is a mistake by OJFord on Wednesday June 01, 2022 @07:53PM (#31589622)
I have a couple too:

Panicked phone call from a jeweller who wanted to know how and why '[their] domain was in my email address'; think he sort of understood once I explained, but still said something like 'can't be too careful in this business' - well sure ok but what am I going to do with.. oh nevermind!

Password lockout/reset over the phone, reading my 100ch 'memorable phrase' as generated by pass... Gave the guy a good chuckle, and no he was not willing to concede by the umpteenth 'upper case A' or 'backward slash' that I obviously 'knew' the phrase and could surely be relieved from reciting the entire thing... I use shorter ones now.

Re:Using a catch-all domain is a mistake by cortesoft on Wednesday June 01, 2022 @10:17PM (#31590534)
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.

Re:Using a catch-all domain is a mistake by jedberg on Thursday June 02, 2022 @01:08AM (#31591556)
That's why I always put legit but wrong answers in. Can't really guess because they're all different and made up, but also can't say, "Oh I just mashed the keyboard".
Re:Using a catch-all domain is a mistake by brewmarche on Thursday June 02, 2022 @02:48AM (#31592179)
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)
Re:Using a catch-all domain is a mistake by mellavora on Thursday June 02, 2022 @04:25AM (#31592661)
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 by silverhydradev on Wednesday June 01, 2022 @08:11PM (#31589769)
I do the same thing, but for exactly the reasons you described, this type of passphrase can be vulnerable to social engineering.
Re:Using a catch-all domain is a mistake by nicoburns on Wednesday June 01, 2022 @08:28PM (#31589886)
Bitwarden can generate xkcd style English-word pass phrases that can be useful for this kind of scenario.
Re:Using a catch-all domain is a mistake by yellow_postit on Wednesday June 01, 2022 @11:33PM (#31591012)
Same with 1Password. Has been a life saver with a family account.
Re:Using a catch-all domain is a mistake by inetknght on Wednesday June 01, 2022 @07:40PM (#31589527)
> I don't really know exactly, but she told me something about me using their stuff without their acceptance, when I tried to explain that's my own domain she told me I cannot use their name, because that's a copyright infringement. Weird.

I can't tell you how many non-techy people think I'm part of their company because I have yourcompany@mydomain. Sigh. Big companies have ruined the internet by having everyone have @gmail or @hotmail or something.

Re:Using a catch-all domain is a mistake by trelane on Wednesday June 01, 2022 @09:56PM (#31590418)
The "best" is when you can't even sign up without having an account at a Large Company e.g. gmail or outlook. I'm not sure what that's supposed to prevent issues with.

Sure, you can add "+thing" after the username portion, but those that know this bog standard trick can still automatically derive your email address and get around your filters. At least with a dedicated username portion a human has to think for a second.

Re:Using a catch-all domain is a mistake by ben0x539 on Thursday June 02, 2022 @01:12AM (#31591587)
> those that know this bog standard trick can still automatically derive your email address and get around your filters

Not if you default the other way around and autodelete all mail that doesn't have a "+thing". :V

Re:Using a catch-all domain is a mistake by thfuran on Thursday June 02, 2022 @07:29AM (#31593622)
Which causes major problems with those sites that refuse to accept an address containing a "+".
Re:Using a catch-all domain is a mistake by justin_oaks on Thursday June 02, 2022 @11:33AM (#31596131)
If you use Gmail then you have a couple of ways besides using the + to make a variation of your email address that will still come to your inbox:

1) Use dots (period or full stop) between letters in the username part of your email address. For example, if your email is [email protected] then [email protected] and [email protected] also get routed to you.

2) Use @googlemail.com instead of @gmail.com in your email address.

I have a Gmail address and I use these other variations whenever a company rejects email addresses with + in them.

Re:Using a catch-all domain is a mistake by Semaphor on Wednesday June 01, 2022 @11:44PM (#31591075)
Which companies are those? Is there a list somewhere? The only time I ever encountered this was with AliExpress.
Re:Using a catch-all domain is a mistake by bpye on Thursday June 02, 2022 @12:04AM (#31591205)
Did that change? My AliExpress account is using [email protected]
Re:Using a catch-all domain is a mistake by Semaphor on Thursday June 02, 2022 @12:14AM (#31591270)
I don’t know, I registered some time last year. Maybe it’s also the TLD? I have .me.
Re:Using a catch-all domain is a mistake by efreak on Thursday June 02, 2022 @02:19AM (#31591977)
I've got a [email protected]. My dentist and several large companies refuse to accept this as a valid email address, so I have to use an email that doesn't identify me personally by name (uses efreak instead of my name). This annoys me every time I deal with them, especially since some of these sites use my email address as a username. I've been locked out from logging in on other devices a couple times for trying too many passwords when the problem was the address, not the password.
Re:Using a catch-all domain is a mistake by Samon on Thursday June 02, 2022 @11:07AM (#31595806)
From memory, AliExpress wouldn't accept [email protected], but [email protected] was fine.
Re:Using a catch-all domain is a mistake by Semaphor on Saturday June 04, 2022 @01:34AM (#31617311)
Interesting, so maybe I should have used a different prefix. Weird design.
Re:Using a catch-all domain is a mistake by trelane on Thursday June 02, 2022 @08:03AM (#31593810)
I don't recall. I've only encountered it once or twice.
Re:Using a catch-all domain is a mistake by Semaphor on Wednesday June 01, 2022 @11:43PM (#31591070)
Another no regrets catch-all user. Looking into my rules, I have 4 "to" addresses that get sent to spam.

Two stories as well:

a) After contacting a company, I got a mail from their legal department asking me to explain why I’m using their trademarked name in my email

b) Using an online-shop that requires emailing the owner for your order (so he can send you a PayPal invoice and then snail-mail you the music CDs you ordered…) I got a personal message attached of him asking why his label’s name is in my email address.

In both cases, a short explanation was sufficient, though.

Re:Using a catch-all domain is a mistake by bambax on Thursday June 02, 2022 @02:53AM (#31592204)
I too have been using a catchall email address since some time in the last century, and it's been cool, although the post is right when they say

> The truth is no one really sells your email

The reason I started doing this was to monitor if someone would transfer my address, and it's never happened. You also get more spam because every firstname@yourdomain works.

But the weird interactions are good! Last year I wanted to get my kid in a somewhat selective middle school (in France) and the fact that the email I was registered with was name_of_school@mydomain helped, because the principal was convinced I was and always had been a huge fan of the school, to have my email named after them...

People simply don't understand you can have more than one email address -- let alone a million. That's kind of fun.

Re:Using a catch-all domain is a mistake by e40 on Thursday June 02, 2022 @12:31AM (#31591370)
I actually got a call from a company I bought something from, direct from their website. I had bought it using the email $company@$mydomain. Got a call (in the days before most of my calls were not spam and I answered the phone!) from a marketing person and the guy tried to bully me into ... not sure what. I couldn't even tell, like you, what he was accusing me of... I'll say, it felt really good to school him about the internet and how it worked.
Re:Using a catch-all domain is a mistake by mulmen on Wednesday June 01, 2022 @09:47PM (#31590378)
> When I started with catch-all I was actually using mails like companyname@mydomain […]

I missed out on a dentist appointment because of this. They thought I was a robot. I blame gmail.

Re:Using a catch-all domain is a mistake by cube00 on Thursday June 02, 2022 @03:16AM (#31592315)
I've missed out on appointments too, the business owner later told me after I finally reached them on a social platform "that address looked weird so I just deleted it"

Regardless, I still regret nothing, seeing my spam free "catch all" mailbox compared to my spam infested decade old web mail is all I need to know it was the right choice.

Re:Using a catch-all domain is a mistake by aendruk on Thursday June 02, 2022 @02:39AM (#31592125)
My ham radio certification was issued to a nonsensical address because the exam coordinator crammed @gmail.com onto the end without me knowing.
Re:Using a catch-all domain is a mistake by m3047 on Thursday June 02, 2022 @01:22PM (#31597836)
The phone thing has veered into outright fraud. Twitter just paid a $150,000,000 fine to the (US) FTC for letting advertisers match on telephone numbers provided for 2FA.

I am really tired of people selling my burner phone to the credit people; and no, I don't own that phone number. Prove I do.

Take my local credit union. Please. Jackasses let someone have access to my checking account. I don't bank online with them either, or I didn't, but last summer was trying to talk to them about a refi and I had to register online and they wanted a phone for 2FA. So of course instead of calling the land line, which is clearly and incontrovertibly mine, they called the burner. Several times.

Eventually I answered it with "fuck you you frauds" and they were "oooh sir, call me back on my direct line" so I tried... from my land line in the same area code, you get the idea... and their system won't route the call to their fraud department. So I ignored them for a couple of weeks.

Seriously they were so incompetent that when the actual fraudsters were probing, the first transaction was a /deposit/. When they were finally trying to clean their mess up, they /credited/ me the same amount. I'm the one who figured it out and told them well you gave me 2x their original deposit, when you really should have debited the amount in the first place.

People like that are not going to safeguard your information.

Ob relevance: I have my own reasons for not wildcarding domains and use this instead: https://github.com/m3047/trualias

Re:Using a catch-all domain is a mistake by lupire on Wednesday June 01, 2022 @07:17PM (#31589374)
Re:Using a catch-all domain is a mistake by EGreg on Wednesday June 01, 2022 @11:52PM (#31591130)
That dude missed the biggest benefit

When someone tries to call into a provider and impersonate you, to take over your account… they would fail because they don’t know your login even!

Whereas, for most people, they’d sweet talk the person on the other line into resetting the password. Happened to me with GoDaddy, they almost rerouted my @mydomain.com email and then it would have been really bad

Re:Using a catch-all domain is a mistake by cube00 on Thursday June 02, 2022 @03:09AM (#31592287)
Another no regrets checking in. I've caught companies either selling (or leaking) my address so for me it's been worth it.

Some businesses freak out that "that's our domain name, we own it, you can't possibly use it".

To placate them I'll spell it backwards or give a related name that I can still work out the source. eg. fleet2022@ if I'm renting a car

Re:Using a catch-all domain is a mistake by stormbrew on Thursday June 02, 2022 @02:35AM (#31592097)
I use myname-shortbusinessname@mydomain and once the delivery person for a pizza place i ordered from fairly regularly asked if i worked for the store somehow. I changed the email i used with them to one that was less obvious after that.

Not as exciting as getting accused of trademark infringement, but it’s interesting how people interpret these things.

Re:Using a catch-all domain is a mistake by justsomehnguy on Thursday June 02, 2022 @03:12AM (#31592298)
With all those similar stories I wonder why people even bothering with changing an email recipient when some random guy asks about it.

Like... delivery guy asked and?..

Re:Using a catch-all domain is a mistake by thfuran on Thursday June 02, 2022 @07:33AM (#31593643)
And they don't want to keep having that conversation, presumably.
Re:Using a catch-all domain is a mistake by justsomehnguy on Thursday June 02, 2022 @01:27PM (#31597895)
Chances are there but slim.

Personally I had a similar conversation only once and only because it was a one-man AliBaba reseller shop, so he personally processed all orders.

Re:Using a catch-all domain is a mistake by stormbrew on Friday June 03, 2022 @12:43AM (#31604382)
Pretty much yeah. Not only is it an annoying conversation, it's also a deeply boring one.
Re:Using a catch-all domain is a mistake by alanh on Thursday June 02, 2022 @12:08PM (#31596631)
regarding 'copyright infringement,' you gotta love it when people get aggressive about IP without knowing what they are talking about; the relevant law would be trademark, not copyright