Outsourcing Email: a case study Ira Winston CIO School of Arts & Sciences University of Pennsylvania. School of Arts & Sciences (SAS). Penn (est. 1740) is an Ivy League university in Philadelphia ranked #5 by US News and World Reports SAS is the largest of the four undergraduate schools at Penn
Q1. What system do you current use for email (exchange, imap/webmail, etc.)?
A1. Those with heavy webmail (IMP, squirrel mail, homebrew) systems
Q2. What are the storage quotas for student email?
A2. Anything under 250mb
Q3. Do you allow forwarding and, if so, what percentage of students forward their email?
A3. Those who already allow forwarding and have a significant percentage of students forwarding.
Q4. How old is your current email system?
A4. Anything older than 2 years
Q5. Which clients do your students use to access your current email system? If the data is available, break the usage down by client?
A5. Heavy webmail – GMY have excellent webmail clients
Q6. Do you support POP, IMAP or both?
A6. POP only – gmail, Windows Live and Yahoo (GMY) do not support IMAP
Q7. Do you have a calendaring system for students?
A7. no calendaring system – GMY provide calendaring
Q8. Do your university administrators want/need access to individual student emails for personal safety and student judicial inquiries?
A8. universities that prefer NOT to have access to individual student emails
Q9. How effective is your current antispam solution?
A9. bad antispam – GMY have good antispam because their large user bases categorize spam
Q10. Do you have a disaster recovery plan for your email service?
A10. no disaster recovery plan – GMY have geographically redundant data centers