My hoster introduced a web firewall, which thought my password was a SQL injection and gave me a plain 403 but was disabled when authenticated so allowed me to change my password to something offending again. Had a funny conversation with them where they insisted that this was beneficial, because SQL injections can happen as humans make mistakes.
A few days before that another hoster updated its password policy and sent me a less secure password by mail. He also insisted that since he uses SMTP over SSL, there is nothing wrong with that.
And on a not related note: The technical support lead of my dedicated mail hoster does not understand DKIM.
I was trying to be reasonable and not focus on stuff others can do better, but it seems like you have to do everything by yourself if you want it done right.
A few days before that another hoster updated its password policy and sent me a less secure password by mail. He also insisted that since he uses SMTP over SSL, there is nothing wrong with that.
And on a not related note: The technical support lead of my dedicated mail hoster does not understand DKIM.
I was trying to be reasonable and not focus on stuff others can do better, but it seems like you have to do everything by yourself if you want it done right.