> > Finally, if an owner has set up a personal password for the > > old id in the web interface, and that owner is also a subscriber > > and gets "changed", and then tries to use the password with > > either id in the web interface, it would be nice if that > > would just work. Will the aliases.names entry be enough to > > save us from ourselves here? :) We did this last spring: aliased arches.uga.edu (our old mail system) to uga.edu (our new mail system). Everyone's existing passwords for [log in to unmask] worked and didn't need to be recreated. -- Jean Snow Production Systems Support Enterprise Information Technology Services University of Georgia