I wish I had more time to write more, but I don’t. A few brief notes: user admin is still kind of a mishmash, because you have to create directory users and provision them through one tool, then manage their rights in each application through that application. If a component isn’t installed or running, you can’t provision it. For example, if you don’t start the mail service, when you create a user account, it won’t have any email attributes. (It’s simple to go back to oiddas and add that capability, but it stinks that you have to.)
Second, your first move ought to be to grant the orcladmin user email admin rights, then create a domain. This isn’t well described in Oracle’s documentation– the steps required to complete these tasks are, but not the fact that you have to do them in the first place. If you don’t do this, you’ll have all kinds of hassles.
My copy of the Burleson and Garmany book got here today, but I’ve been too busy to read any of it yet. Perhaps tonight.
Oh, and when you create a new user, don’t put in a FQDN for the email address. If you do, you’ll end up in a catch-22: you can’t create an email domain for the RHS of the address, but you can’t remove the existing email address (or log on to the OCS mail page) because… wait for it… the domain doesn’t exist.
Paul's Down-Home Page 