Sample Email Improvement Project Considerations
March 7, 2010Summary of User, Technical and Institutional Requirements
- Reliable and resilient message delivery (<2 minutes for internal mail)
- Secure (including password, data encryption, enforcement of strong password)
- Open standards (i.e. IMAP, HTTP, HTTPS, SMTP)
- Integrates with current server, directory and workstation environment
- Interoperable with current systems (Exchange, Lotus Notes)
- Single-seat administration
- System and usage monitoring
- Auditing
- Quota management
- New mail notifications
- Address standardization
- Audit trail – to facilitate use e-mail for formal communications with staff and students
- Commercial activities covered
- Digital signatures
- Electronic procurement
- e-mail to mobile phones
- Future proof
- Generic addresses
- Integration with Virtual Learning Environment, Student Management System, authorization systems especially eDir
- Secure, round-the-clock remote access to mailboxes
- Centralized virus detection and disinfecting for all inbound and outbound emails
- Centralized spam detection all inbound emails
- Server-based mailstore separate from mailestore, with ability to capture local cache of emails for use when traveling
- Access to mailboxes from multiple, cross-platform clients
- Server-based, user-specified filtering rules to delete or move mail from Inbox independently of mail client
- Ability to handle large attachments (100MB or more) intelligently
- Calendaring