I've noticed that I can create new services with logins that match existing
aliases. Will this be prevented in a future build of Emerald? After all,
we don't want to accidentally give a new user a login that's already being
used as an alias within the same domain.
Also, it isn't really clear what Emerald expects with regard to format for
aliases. That is, if alias functionality was all it could be (that is, with
mail servers pulling alias values from the Emerald database), what would
Emerald expect to see - "user" or "email@example.com" ?
Lastly, is there any chance of full integration with IMail on this level? I
understand the problem currently lies with IMail not reading the Emerald
database for aliases and forwards, but are there any future plans for it
that you know of? It's not so much that we want to not enter data
redundantly, but rather that we don't want to inadvertently assign names
that are already in use within other systems.
David V. Brenner - firstname.lastname@example.org
International Services Network Corporation