Description
I got shut down on a refactoring because we use MailboxPath not only to identifies names of mailboxes (along with their owner) but also as a way to query the various names.
This hurts me back as I was trying to impose stronger validation over MailboxPath mailboxName.
Given the "query" context, I could not make MailboxPath stricter.
For mailbox search within MailboxMapper, we should rely on a more suited object. I propose to rely on raw "MailboxQuery object". At the noticeable difference that we need to make sure the username & namespace is being specified at the mapper layer.