E-mail Scheduler Service

Author Daniel Fisher
Date 2005/11/08

Requirements

Problem Statements

  • There exist no mechanism for deprovisioning e-mail

Functional Requirements

  • E-mail Expiration Task
    1. Ability to notify a user via e-mail that their account will be deleted and provide a grace period for the user to retrieve their e-mail
    2. Ability to keep the e-mail account data in the registry while the account is in a deleted state on the mail server
    3. Ability to delete e-mail account data from the registry when an account is expired

Nonfunctional Requirements

  1. Must be implemented as a clustered JBoss service.

Useful links

Comments

Flow diagram that describes email expiration logic as of 2008-06-17, Email Expiration Flow.

 
middleware/devel/ed/email-scheduler.txt · Last modified: 2009/10/07 17:17 (external edit)
 
Except where otherwise noted, content on this wiki is licensed under the following license:CC Attribution-Noncommercial-Share Alike 3.0 Unported
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki