Earlier quoted context omitted.
I wonder what they'd have said about tobias.luetke@ourdomain.com
"Actually, my name is Sam Hopify..."
Yassir Shopif
Using a catch-all domain is a mistake
191–200 of 304 posts
Re: Using a catch-all domain is a mistake
#192> I also have a bunch that I've misspelled. My GrubHub account is gruhub@. I use a password manager for passwords but I also need to use it to remember the associated emails. I find that to be a strange complaint. What password manager is being used that doesn't support a username alongside a password in an entry?
Usernames are not always similar to email addresses. In fact, if you are "foobar@example.org", you might find that someone has already claimed the username 'foobar' on Amazon. So I believe your parent commenter's point is that he wishes he could associate both a username & an email address (or at least a comment field) with each entry in his password manager.
Re: Using a catch-all domain is a mistake
#193I also used to use catch all domains for all kind of registrations and my form was @mydomain.at (e.g. ycombinator.com@mydomain.at). That most of the time solves the management aspect, except for some special cases where several domains share a unified login (e.g. Google or Stack Exchange).
Anyway, I’ve changed to iCloud’s Hide My Email some months ago, as this is much easier to use and you have easier control on all used emails. You can even add a comment to each address in the moment of creation. Also disabling (blocking) single addresses works like a charm.
Re: Using a catch-all domain is a mistake
#194Using a catch-all domain _was a mistake for me_ would be a more appropriate title here.
I’ve been using a catch all for years now and have had nothing but amusing and fun interactions and discussions with folks about my email addresses. People often understand pretty quickly and think the concept is actually cool (even if they aren’t running out to buy their own domain).
I’m far annoyed by my weird, hard-to-say/spell house street name but that’s harder to change (:
Re: Using a catch-all domain is a mistake
#195For weeks our Shopify app was getting rejected because "you cannot use the Shopify name or trademark in your app". It wasn't... repeated requests for clarification just got back the same form response. After a several frustrating back-and-forths, finally someone at Shopify said "check your email address". The developer contact email address we had submitted, which was only used for shopify us communication and no cus…
You'd think anyone competent in tech would instantly recognise that for what it was. Using an email like that for a specific purpose shouldn't be that uncommon. And they should recognise that it was an internal address. Crazy.
I assume Shopify’s position there is that the email address provided with the app is probably visible to end users somewhere and could cause confusion. The policy itself seems reasonable enough just shitty enforcement.
Re: Using a catch-all domain is a mistake
#196Earlier quoted context omitted.
> you do have to set it up so that you can send email from the addresses Fastmail's webmail allows you to specify the sending email address for a catch-all mailbox in the message composition page, so there is no additional setup there.
Edit: oh god, leaving this in place for posterity but I am completely misrepresenting fastmail here. It is protonmail that I recently tried and had these limitations. Apologies! How embarrassing. Also, I have no idea why the child comment correcting me would be so downvoted. It’s apparently correct. Yes, but fastmail has a couple dealbreaker limitations when doing this: First, you can’t originate mail from that addre…
You can originate emails from anything - it just requires that you set it up as an alias (and you can set custom signature etc...)
You don't need to explicitly setup recipient addresses! I can have as many xxx@myname.mydomain.com addresses, where xxx is anything at all. myname@mydomain.com is my main email address.
Re: Using a catch-all domain is a mistake
#197Earlier quoted context omitted.
You'd think anyone competent in tech would instantly recognise that for what it was. Using an email like that for a specific purpose shouldn't be that uncommon. And they should recognise that it was an internal address. Crazy.
I assume Shopify’s position there is that the email address provided with the app is probably visible to end users somewhere and could cause confusion. The policy itself seems reasonable enough just shitty enforcement.
Not sure in this case and it's definitely possible, but usually you have an email used for the account and interacting with Shopify, and then a public facing one used for customer support.
Re: Using a catch-all domain is a mistake
#198Earlier quoted context omitted.
Really? Wouldn't that catch people with `.co.uk` or similar localized domains?
They use a regex such as /[a-z]+(\.[a-z]{2,3}){1,2}/ There’s a lot of bad email validation regexes floating around on the internet. If it’s an older service it may have been written before gTLDs.
I have an address that ends in .fyi and continue to encounter systems that refuse to accept it as a valid domain. It's really frustrating but at least I have a .com that I can enter into those and just forward it.
Re: Using a catch-all domain is a mistake
#199Earlier quoted context omitted.
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…
Bitwarden can generate xkcd style English-word pass phrases that can be useful for this kind of scenario.
Same with 1Password. Has been a life saver with a family account.
Re: Using a catch-all domain is a mistake
#200Earlier quoted context omitted.
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 equifax@mydomain.com 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 addr…
> 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 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.