83

Error: No Valid Command found

User receives an email with a 'No Valid Command Found' error.

A 'No Valid Command Found' error is sent only when mail is delivered to the MDaemon Server account that does not contain a valid command.

If you are receiving messages with the 'No Valid Command Found' error here are some things you can check:

  1. Click Accounts.
  2. Click Address Aliases. Make sure that you do not have any aliases setup pointing to the MDaemon account. The only aliases that should be pointing to the MDaemon account are the default ones created by MDaemon.

    For example:
    • listserv@$LOCALDOMAIN$ = mdaemon@example.com
    • list-serv@$LOCALDOMAIN$ = mdaemon@example.com
    • listserver@$LOCALDOMAIN$ = mdaemon@example.com
    • mdaemon@$LOCALDOMAIN$ = mdaemon@example.com





  3. Click OK.
  4. Click Setup.
  5. Click DomainPOP.
  6. Click Routing Rules.
    • Make sure that you don’t have any routing rules pointing to the MDaemon account.

  7. Click OK.
  8. Click Lists.
  9. Click Edit Lists.
  10. Select the list.
  11. Click OK.
  12. Click Members.
    • Make sure you don’t have the MDaemon account subscribed to any lists for each list you have.

  13. Click OK.
  14. Click Accounts.
  15. Click Account Manager.
  16. Check the mail storage directory for each user and make sure that no users are sharing a directory with the MDaemon account.
  17. Click OK.