Inter-operability

These are the things that we think Higher-Ed are interested. (Beyond the standard Chandler functionality)

• IMAP servers
  • Compatible with all widely deployed IMAP servers
  • IMAP as the canonical store for email
  • Non Double storage of mail in both repository and IMAP
• POP servers
  • Support for all widely deplyed POP3 servers, Fairly easy to support POP3. We may not have to support leave mail on server in first release?
• SMTP servers
  • Easy, we can support encrypted SMTP if necessary
• LDAP servers
  • Read only LDAP.
  • Updating LDAP may or may not be a necessary feature
• Support for security standards (TLS, SASL, Kerberos V5)
  • We will support these, does higher ed need anything more?

Also possibly [a survey is being sent to determine interoperability needs of the following]:

• Oracle Corporate Time
• MAPI/ MS Exchange
• Meeting Maker
• Other important proprietary applications which we need to know about and interact with

Open Questions

What would be an example of an email program that defines the minimum features necessary to be deployable? In other words, help us define our 1.0 mail feature set.

Is LDAP updating a critical feature?

Is Kerberos V5 and plaintext over TLS sufficient authorization for everyone?

Does anyone still use Usenet News? Do we need news support?

Are there any firewall issues specific to Universities?

-- ChaoLam && LouMontulli^? - 14 Feb 2003

-- PieterHartsook - 24 May 2004