--- Michael Stauber <bq (at mark) solarspeed.net> wrote:
> Hi Greg,
>
> > Yep - Gotcha about the aliases etc.... but why cant we make the
> > usernames be their full email address to login to get their mail and FTP
> > to the site etc etc... I've seen this done on other platforms.... This
> > approach would guarantee that we will never have a problem with a
> > username already "taken", since they will always be unique in each
> > vsite....
I've seen this too, mainly NetWinsite surgemail software.
> I can see why other plattforms may use this approach and it's a design
> decision that should be made very early on before the coding starts. To
> change it later on can be quite a nightmare. :o)
>
> Well, yeah: Technically that's possible on BlueQuartz, but it would require a
>
> somewhat drastical architectural change of Sausalito and CCE. I think that
> would be a very bumpy ride for very little gain. As you can still work around
>
> the username restrictions by setting email aliasses.
Changing the architecture of BQ is probably not a good idea, but login with a
unique username/email is a good feature. And alias is not really convenient.
For example, a user will need to remember to login to email with "user123"
username while the email address is "dave (at mark) domain.com" and it creates another
barrier for users to remember their login name.
> P.S.: If the email address is used as login ID: What happens when you rename
> a
> domain? In that case the login ID of each user also has to change, because
> the domain name in their login ID is now. That's nasty. :o)
This is a moot point though. I have not had a need to rename a domain. This
is a drastic step for any organization so a new site for the new domain and
migration is warranted.
Regards,
Mike