You need to think carefully about the question you need an answer to. I'm not sure quite what you mean by the name of the mailbox. By most definitions it is m@root.com. If you're just routing mail, entries like this may work. However I seem to remember that users with more than one uid attribute couldn't login to certain web tools.
Again, Messaging Server (and many other products) expects the UID value to be a single value. Depending on Directory Server to always return one value before another value in a multi-valued attribute is doomed to failure, as there's no gurantee of the order values will be returned.
Messaging Server indeed typically uses "uid" or "uid@domain" to create the path to the mailbox.
You can indeed use a different LDAP attribute to log into the system. That's configurable. Users don't actually need to know the disk path to their mailbox.
It is well to seriously consider your use of UID. Changing the UID of a user across Messaging and Calendar is not trivial. It's really much more than simply the directory name of the user's mailbox.
UID is the most basic identifier of your users. Planning for this to be permanant is a very good practice. Using a name that may get changed is a poor idea.
Yes !
That the reason why we think to change.
Actually the uid are build with the firstname and lastname of the user but we have to take care about the length, the dubbles,...
We think to use an incremental number (preceded by a letter) which is already used in some SQL tables but we are afraid about the reactions of the user. A lot of them doesn't like to be treated as a number !