61–70 of 76 posts
This is ummm... news? I thought since the spam floods of the early 2000s everyone knew not to put their real email to get that 5€ off coupon. Of course tracking is a thing now too. But most people I know, even non techies are aware of that and very reluctant to give any information.
Currently I use Fastmail to host my own domain, and then for every new service I save the account in 1Password using service@service.mydomain.com It's a bit extreme, but surprisingly little extra effort. That said, most of the accounts I create are throwaway. For phone numbers I have an old, unused Google voice number I give out. It's a real number, but never checked, except for once every 90? days, to keep it active…
Currently I use Fastmail to host my own domain, and then for every new service I save the account in 1Password using service@service.mydomain.com It's a bit extreme, but surprisingly little extra effort. That said, most of the accounts I create are throwaway. For phone numbers I have an old, unused Google voice number I give out. It's a real number, but never checked, except for once every 90? days, to keep it active…
I've been thinking of running a setup like this specifically to rat out who's been selling my e-mail addresses, since the spam would be directed at the service@service.mydomain.com. Did you find any interesting results from your setup? Some surprising services who sold your address?
Earlier quoted context omitted.
I've been thinking of running a setup like this specifically to rat out who's been selling my e-mail addresses, since the spam would be directed at the service@service.mydomain.com. Did you find any interesting results from your setup? Some surprising services who sold your address?
name+service@email.com is also a good way to find out. It’s standard and accepted by most sites and most email providers. I use it, didn’t find any proof of service selling my adress except some random Ali express vendor the one and only time I bought here an item I couldn’t find anywhere.
Earlier quoted context omitted.
name+service@email.com is also a good way to find out. It’s standard and accepted by most sites and most email providers. I use it, didn’t find any proof of service selling my adress except some random Ali express vendor the one and only time I bought here an item I couldn’t find anywhere.
That mechanism is so well known, it’s trivial to undo by removing the +service part. Is it really effective? How would you even find out if it is?
I’ve been using addy.io for quite some time now. I have a burner tld and every time I sign up for something new I input servicename@mytld.com. Addy forwards that email to the email I have chosen. Works doubly better if you don’t use gmail as your inbox.
Currently I use Fastmail to host my own domain, and then for every new service I save the account in 1Password using service@service.mydomain.com It's a bit extreme, but surprisingly little extra effort. That said, most of the accounts I create are throwaway. For phone numbers I have an old, unused Google voice number I give out. It's a real number, but never checked, except for once every 90? days, to keep it active…
How do you set your domain on fast mail to use @ .domain.com? I only know @.
It even works multi-level, like x.y.domain.com will use the MX records of domain.com (provided there are none for x & y).
This is worth mentioning as x.y.domain.com does not work if you have a *.domain.com SSL certificate.
Also the Bitwarden password manager has an integration for SimpleLogin.
Earlier quoted context omitted.
How do you set your domain on fast mail to use @ .domain.com? I only know @.
(I'm using wrong terminology) It works because if there is no entry for *.domain.com the system will go one level up, to domain.com for the MX records. It even works multi-level, like x.y.domain.com will use the MX records of domain.com (provided there are none for x & y). This is worth mentioning as x.y.domain.com does not work if you have a *.domain.com SSL certificate.
Earlier quoted context omitted.
(I'm using wrong terminology) It works because if there is no entry for *.domain.com the system will go one level up, to domain.com for the MX records. It even works multi-level, like x.y.domain.com will use the MX records of domain.com (provided there are none for x & y). This is worth mentioning as x.y.domain.com does not work if you have a *.domain.com SSL certificate.
Really? Cool. Would you be comfortable sharing your dns settings and or fastmail domain settings? Cool if no but I wanna give this a go!
It seems that fastmail only does *.domain.com and not *.*.domain.com: https://www.fastmail.help/hc/en-us/articles/360060591053-Plu...
Hope that helps