Email Management Bean

• There exists no programmatic method to manage email addresses, aliases, and forwards in the registry.

1. Ability to create email account(s) in the registry for specific people
   • email address must meet address requirements
   • email address must end in ”@vt.edu”
   • email address must not contain illegal characters
     • illegal characters match the regular expression:

       \\p{Alpha}\\p{Alnum}*

   • email address must not already exist in the registry
   • email address must be available:
     • in the EMAIL namespace if the requested address is UUPID@vt.edu
     • in the PID namespace otherwise
2. Ability to remove a person's email account (including aliases and forwards)
3. Ability to create an email alias in the registry
   • alias must meet address requirements
   • alias must end in ”@vt.edu”
   • alias must not contain illegal characters
     • illegal characters match the regular expression:

       \\p{Alnum}[a-zA-Z0-9_\\.\\-]*

   • alias must be available:
     • in the EMAIL namespace if the requested address is UUPID@vt.edu
     • in the PID namespace otherwise
4. Ability to remove a single alias or all a person's aliases
5. Ability to create an email forward in the registry
   • forward must meet address requirements
   • person must not already have a forward
   • forward cannot be set to the person's email address or aliases
6. Ability to remove a person's forward
7. Ability to set a person's preferred address

1. Must be implemented as a clustered stateless session bean.
2. All methods must accept UIDs as input, not UUPIDs.
3. Methods must be exposed as web services.

A well-formed email address will not match any of the following regular expressions:

^\\.|^\\@

[^A-Za-z0-9\\.\\@_\\-~#]+

[\\w-]+\\.[\\w-]+$

\\@

\\@.*\\@

• Javadocs