It's not much better than "Your.Full.Name+company@example.com" in practice tho.
lyft@account.example.com
liftcarshare@example.com
email@lyft.com.example.com
example.com@com.lyft.example.com
Generate random email addresses so you can't easily guess what others I might have given out. Then keep track of the mapping.
A service like simplelogin.io makes this easy.
When creating an account somewhere, fastmail automatically generates a new email for the site via an API in one click.
Highly recommend.
E: Ah, I didn't see the schema one of the parent commenters suggested - your question makes a lot more sense now. I still don't really care about the creation date, though, but I do care about the email having a random component, since if someone were to figure out my naming schema, they could check whether I've signed up for any given service.
Sometimes their front-end is not aware of this restriction and will let you register, but then you'll have unresolvable issues. I've spent some time on tech support phone calls with companies that have this issue.
Occasionally a company will implement blocking their own name in a user-provided email after the user is already registered. I've had this happen a few times too. Suddenly the account will disappear without explanation.
The way we don't see most software companies supporting linux desktop users simply because it is not profitable, we can hypothesize that the spammers won't spend time-energy-money on getting the +company filtered out.