Hacker News Reader

Comment by the_pwner224 | Hacker News Reader

You can set up a wildcard/catchall alias instead of having to manually create an actual alias for each service. Someone can send email to anything@yourdomain.com and it will go to your inbox.

You can also send with a wildcard - the big desktop email clients, as well as the FastMail web interface, as well as FairEmail on Android all let you type something for the part before the @, so you can send from anything@yourdomain.com.

https://www.fastmail.com/help/receive/alias-catchall.html

View on HN

You can even do more than that.

I have different categories per services: paid services go to @paid.mydomain.tld, social logins go to @social.mydomain.tld etc. So that means something like paypal@paid.mydomain.tld or twitter@social.mydomain.tld.

Edit: using Route53 for DNS subdomain wildcard.

> paid services go to @paid.mydomain.tld, social logins go to @social.mydomain.tld etc

Any specific reason to do this over the usual way (paypal@mydomain.tld, twitter@mydomain.tld)? How are you benefitting from the extra hierarchy?

I imagine it's for easier management of rules used to file email from certain accounts into folders.

Even better if you use their Web interface, you'll reply with the same email alias that received the email.

On top of this, I purchased a `.email` domain. Something about `anything@yourdomain.email` feels clean.

That does seem clean, but I would worry about normal people being confused by it. Having (business's name)@myname.com already gets a lot of questions / confirmations / confused responses.

Yes, doing that certainly does raise a lot of questions from people. They often pause and ask for clarification. Also, I've come to learn that some company's email validators do not accept `.email`. Thankfully this is a rare occurrence. And when it does happen, I've always been successful in bypassing it. I'm too attracted to the appeal of `.email`, so I happily put up with it.

Reply on news.ycombinator.com