Comment 1 for bug 714694

This appears to be a problem with ejabberdctl passing input on to erl; it is not escaping input correctly, so your passwords were likely created as "0P3N" and "0p3n".

I opened https://support.process-one.net/browse/EJAB-1399 against ejabberd accordingly.

If you want to register a password using ejabberdctl with special shell characters until such time as that bug is resolved, the workaround is to specify a double-escaped character at the command line, e.g.

0P3N\\\\$RF