Miscellaneous first checks

• I checked that all ports are open and not blocked by my ISP / hosting provider.
• I know that SSL errors are likely the result of a wrong setup on the user side and not caused by DMS itself. I'm confident my setup is correct.

Affected Component(s)

Setup script

What happened and when does this occur?

Running `./setup.sh debug inspect` gives an error message. The command is not recognized. Its output is

The command 'debug inspect' is invalid.
Use `./setup.sh help` to get an overview of all commands.

However /setup.sh help lists the option as available:

COMMAND debug :=
        /usr/local/bin/setup debug fetchmail
        /usr/local/bin/setup debug fail2ban [unban <IP>]
        /usr/local/bin/setup debug show-mail-logs
        /usr/local/bin/setup debug inspect

### What did you expect to happen?

```Markdown
Detailed information about the running instance.

How do we replicate the issue?

1. Run `docker exec mailserver setup debug inspect`

DMS version

v10.5.0

What operating system is DMS running on?

Linux

What instruction set architecture is DMS running on?

x86_64 / AMD64

What container orchestration tool are you using?

Docker Compose

docker-compose.yml

Does not apply

Relevant log output

Does not apply

Other relevant information

No response

What level of experience do you have with Docker and mail servers?

• I am inexperienced with docker
• I am inexperienced with mail servers
• I am uncomfortable with the CLI

Code of conduct

• I have read this project's Code of Conduct and I agree
• I have read the README and the documentation and I searched the issue tracker but could not find a solution

Improvements to this form?

No response