Dear services that refuse email addresses that have the name of the service in the address:
-
Dear services that refuse email addresses that have the name of the service in the address:
We domain owners do that because we do not trust you not to sell that address to others or otherwise use it inappropriately. Your algorithmic refusal of that address is sketchy af.
@alexr I use name+service@Mydomain.com
Some services do not support +word in an email address! It's in the spec!!
-
Dear services that refuse email addresses that have the name of the service in the address:
We domain owners do that because we do not trust you not to sell that address to others or otherwise use it inappropriately. Your algorithmic refusal of that address is sketchy af.
@alexr I bet in a lot of cases you could just munge the address a bit while keeping it recognizable for your tracking. Like if you're registering for "Service", create "s3rvice@mydomain.com" or "fartservice@mydomain.com"
-
@alexr we handle this by rot13ing their name and then undoing the transformation on our mailserver's end
-
Dear services that refuse email addresses that have the name of the service in the address:
We domain owners do that because we do not trust you not to sell that address to others or otherwise use it inappropriately. Your algorithmic refusal of that address is sketchy af.
Agree. Although I use it for to detect data breaches.
I tell the shops its anti spam so we know its from you. Makes em feel special.
The refusal to accept their name in the email probably results more from a over zelous web site designer than anything else.
Reversing their name usually works
$ echo example.com | tac
moc.elpmaxe@..... -
Agree. Although I use it for to detect data breaches.
I tell the shops its anti spam so we know its from you. Makes em feel special.
The refusal to accept their name in the email probably results more from a over zelous web site designer than anything else.
Reversing their name usually works
$ echo example.com | tac
moc.elpmaxe@.....@ken_fallon @alexr I just insert a period (looking at you, ora.cle and ep.ic).
-
@alexr I use name+service@Mydomain.com
Some services do not support +word in an email address! It's in the spec!!
-
@alexr @paul_ipv6 same for ones that dont allow + in the mailbox part. It's in the RFC, even google/Gmail supports it.
I made myself a small script to base64 encode the site + date (in case it's a site that allows you to order stuff but not register), but its not convenient.
@j_angliss @alexr @paul_ipv6 I have a regex alias in my postfix to treat . the same way the + does. Never came across a site which didn't like the dot, although I always use + if possible
-
Dear services that refuse email addresses that have the name of the service in the address:
We domain owners do that because we do not trust you not to sell that address to others or otherwise use it inappropriately. Your algorithmic refusal of that address is sketchy af.
@alexr Some creativity is needed.
Google can become: g.zerozero.le
Git: geyet
Apple: aqqle -
Dear services that refuse email addresses that have the name of the service in the address:
We domain owners do that because we do not trust you not to sell that address to others or otherwise use it inappropriately. Your algorithmic refusal of that address is sketchy af.
@alexr I don’t tend to use the company names anymore after a Schneider comment along the lines of ‘if your email address is my company at your domain, I bet I can guess what your Amazon email is’. I pick a few words that will remind me of the company. For example, for Amazon I might use something like riverinbrazil as the username part. When I read it, it’s obvious to me that this is the email address I gave to Amazon, but if you know that I have an account with Amazon then you’d need a bunch of guesses to find it (and most of the real ones are specific to how my brain works and other people would find it confusing what the connection is). The only ones where I use the company names are accounts I’ve had for well over a decade and there aren’t many of them left.
-
@alexr @paul_ipv6 same for ones that dont allow + in the mailbox part. It's in the RFC, even google/Gmail supports it.
I made myself a small script to base64 encode the site + date (in case it's a site that allows you to order stuff but not register), but its not convenient.
@j_angliss @alexr @paul_ipv6 even exchange/365 supports it.
I have another rule that accepts X as the too lukeXsite, but it’s annoying when + isn’t supported.
-
@jernej__s @shapr @alexr
Consider the + part a form of password. No password, no access. -
S svenja@mstdn.games shared this topic
