1 / 10

Harvard Faculty of Arts and Sciences IMAP Email “Project”

Harvard Faculty of Arts and Sciences IMAP Email “Project”. CSG Meeting September 16, 1998. Guide to Harvard. Faculty of Arts and Sciences Harvard College (undergraduates) Graduate School Division of Continuing Education. Medical School (not including the 7 affiliated hospitals

kristy
Download Presentation

Harvard Faculty of Arts and Sciences IMAP Email “Project”

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Harvard Faculty of Arts and Sciences IMAP Email “Project” CSG Meeting September 16, 1998

  2. Guide to Harvard Faculty of Arts and Sciences Harvard College (undergraduates) Graduate School Division of Continuing Education Medical School (not including the 7 affiliated hospitals with thousands of users) Business School Law School Central Administration Ed School Public Health Design Radcliffe Divinity Government

  3. Systems for Email • Multiple UNIX sendmail servers. • Multiple UNIX login servers for interactive users. • Multiple UNIX core servers accessing disk space and servicing Pop and IMAP. • Redundant copies of all disks, power supplies and servers. • Round Robin assignments, load balancing, clustering. • Email service separate from Coursework, Web, Netnews and other UNIX services.

  4. FAS Email Systems Disk Farm ~750 Gig Core Servers (Pop/IMAP) (Local Director) bus Sendmail servers (round robin) nfs Interactive logon servers (round robin)

  5. Email User Situation to 9/1/98 • Officially supported user software: Pine on Unix; Eudora with Pop3 on Macintosh and Windows officially supported. • No security beyond passwords (no Kerberos, etc) • 6 megabyte home directory limit. • 2.5 megabyte mail spool limit. • 300,000 to 400,000 email messages processed daily.

  6. Student Email Usage • 6200 undergraduates--96% in campus dormitories. • 3000 graduates--most in off campus housing. • 1200 Extension School students with accounts. • (5000 Summer School users). • Pine in use by 90% of all students. • 40% to 50% also use a Pop package, primarily Eudora. • Pop is used in the student rooms; at the same time Pine is used by students the on move around campus. • Eudora option, “leave mail on server” heavily used.

  7. Faculty and Staff Email Usage • 3000 to 5000 Faculty, Staff and others • Approximately 50% Pine; 50% Eudora/Pop3. • Many have multiple offices: Departments, Library, Home. • Many calls for help because of email organization problems.

  8. Preparations Completed • Upgrade of core email servers: Three 600 Mhz Alphas (Digital Unix) using Cisco Local Director to balance load. • Increase of disk space to allow for 50 megabyte default with 100 megabyte available on request. • Installation of the UWash IMAP server.

  9. A Creeping Introduction • Eudora 4.x distributed to all users. • No sweeping formal action to move people to IMAP. If Pine/Eudora-Pop3 works for a user there is no need to change. • “Brown bag” sessions to introduce IMAP features. • Training sessions set up to help users who wish to switch. • Advice from Help Desks and student consulting.

  10. Calendaring in FAS at Harvard • Meeting Maker 5.03 for offices on a voluntary basis. Offices must pay for their own clients. We manage the server. 400 users among 3000 faculty and staff. PalmPilot support. No students. • Harvard College events calendar--student/staff written. Oracle based. Student group local management • Three-tiered classroom scheduler being written to deal with Harvard’s FAS’s local scheduling control issues.

More Related