At a previous job I complained to company leadership that we shouldn't trust email addresses without verification.
I think the company eventually required verification, not because their trusted employee told them, but because a security review of the product pointed out the lack of email verification.
When it’s a security review and something is on paper, there is now documentation of potential liability.
When it’s just a random staff member complaining they want to do something that makes it harder to onboard customers, there’s no proof of incompetence, and incompetence can still be blamed on the developers.
Yes.
But for what purpose will you be sending it - to cover your ass, or to make yourself feel superior?
Also keep in mind that the company has full access to your work email account therefore they could delete the email if they wanted to. Not likely they would in general but people have been known to do all sorts of things in situations where a written record could hurt them.
To suggest a feature or describe an issue on a product you're working on can be most easily done by just talking to people, for example by bringing it up in a design or planning meeting with the team and management. If it gets picked up it will get added to the schedule in some written form. It does not need to specifically communicated by email or written down, unless explicitly asked for.
Therefore the main purpose of writing the initial suggestion down is so there's a record of it for future use. Either to cover your own ass when management/auditors/lawyers get involved, or to say you were right and management was wrong and make yourself feel superior.
I think the company eventually required verification, not because their trusted employee told them, but because a security review of the product pointed out the lack of email verification.