6 ms·
Looks useful. I'm not sure how the catch-all address works for your service, maybe it's the same maybe it's different from what I have. My problem with a catch
by Coding_Cat 9y ago
Looks useful. I'm not sure how the catch-all address works for your service, maybe it's the same maybe it's different from what I have.
My problem with a catch-all was that there is a lot of spam that gets send to various common email addresses such as "admin". Do you maintain a blacklist for your users?
I have a regular expression set as a username in my database of email addresses. (spoilers: it's just somesalt.*."2 or 3 characters" so for example secretsalt.ycombinator.com@mydomain.tld). So I can sign up to any random website by just entering salt.thatwebsite.tld@me as my email. That's the zero-configuration part. Honestly, this is worth paying $9/year for imho :P
The personal and and professional mail together is simply internally forwarding my professional mail to the same imap instance but a different folder :P. It's mostly future-proofing on my part. If I were to get/manage a different domain-name (say a gaming guild or business venture) I could merge those too and not have to set-up 27 different accounts in my email client.
- herbst 9y agoI currently overwork the catch-all/matching part to support way more options. (Gmail style, timestamp invalidation, subdomains, blacklists ...) Right now my approach is to have a [catch-all]@domain.tld enabled, and then build rules for individual domains i want to blacklist. However sounds like you figured out a nice setup that works for you. So you are not the target audience anyway :)
- Coding_Cat 9y agoSounds like a great product, tbh. If I ever break my server I'll consider it.