this post was submitted on 03 Dec 2023
553 points (86.4% liked)
Technology
59148 readers
2773 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's actually really easy to get past the custom domain issue.
If the domain is send-and-receive, it will need a SPF record to avoid getting blackholed by most mail providers. A TXT lookup for the SPF record would tie the custom domain back to the real provider.
Or even easier, you could look up the MX records to see what domain they point to.
I don't use Simplelogin so I don't know how their service works. The domains used for aliases don't need to originate email so there's no need for an SPF record. The A record for the hostname used for the MX record(s) could technically point at multiple IPs that could be changed often.
I own a significant number of domains and manage my own servers. There's quite literally no way for anyone to prevent me from using an email alias.
My point was that trying to block email aliases is a fool's errand. It's a slight hindrance to only the least technical users. The entire 7c/fakefilter project is an exercise in futility.