The Evolution and Management of Email

1,509 views

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,509
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
11
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

The Evolution and Management of Email

  1. 1. Ri d F tRiccardo Ferrante Smithsonian Institution Archives ACDA 2010 – Mundelein, IL
  2. 2. 1965 – Electronic mail allows users on a single mainframe t t i t ith h th MIT’ CTSS dcomputer to communicate with each other. MIT’s CTSS and SDC’s (System Development Corporation, a spinoff of Rand Corp, that was sold to Unisys in the mid 80’s) Q32 1966 f tibl t “ il” h th1966 – users of compatible systems can “email” each other: BITNET, Unix mail, IBM, DEC 1969 – first electronic mail sent between disparate systems over ARPANET 1971 – “@” address demarcation first used to send email from one DEC system to another DEC system 1982 – Email transmission protocol standard SMTP (RFC 821) and ARPA ITM (RFC 822) published.
  3. 3. 1980’s – Email applications developed for PCs and LANs. P i t t i l d f t t “d d ” thProprietary systems include features to “decode” the mail from competitors’ systems. Cc:Mail, Microsoft Mail, Banyan VINES, Lotus Notes, AppleMail, Groupwise (previously WordPerfect Office)(previously WordPerfect Office) Mid 1990’s – attachments and HTML added as a result of MIME standard (RFC 2045 in 11/1996)standard (RFC 2045 in 11/1996) – web hosted email services 2001 – Email standard RFC 822 superseded by RFC 2822 Mid 2000’ E il d id i liti tiMid 2000’s - Enron emails used as evidence in litigation, posted to the Web 2008 – RFC 2822 superseded by RFC 5322
  4. 4. Messages sent within one computer system
  5. 5. Messages sent between systems that are the same
  6. 6. ARPANET DEC IBM DEC Messages sent between different systems BITNET
  7. 7. ARPANET @Person@company.com BITNET
  8. 8. 1982 -- Standard published for message format – RFC 821, RFC 822 PC and LAN’s support proprietary email apps PC’s & LAN’s
  9. 9. 1982 -- Standard published for message format – RFC 821, RFC 822 PC and LAN’s support proprietary email apps Examples: Microsoft Mail WordPerfect Office (later Novell Groupwise) Cc:Mail Banyan VINES Lotus Notes Banyan VINES
  10. 10. 1982 -- Standard published for message format – RFC 821, RFC 822 PC and LAN’s support proprietary email apps Examples: Microsoft Mail WordPerfect Office (later Novell Groupwise) Cc:Mail Banyan VINES Lotus Notes Banyan VINES
  11. 11. E ilEmail Signature Organization DDocs
  12. 12. Web based email servicesWeb-based email services Email … and others Email Signature Organization Docs Organization
  13. 13. Email data format standard updated 2001 – Email standard RFC 2822 supersedes RFC 822 (1982) 2008 RFC 5322 supersedes RFC 2822 (2001)2008 – RFC 5322 supersedes RFC 2822 (2001) Emails used as evidence in litigation posted toEmails used as evidence in litigation, posted to the Web Legislation passed to include electronic recordsg p in discoverable documents
  14. 14. Email is ubiquitous That means email can be is: Official records O i ti dOrganization records Personal papers
  15. 15. Paper-based recordkeeping systems Electronic recordkeeping systems Adequate and reliable? ERMS systems (DoD 5015.2)y ( ) http://jitc.fhu.disa.mil/recmgt/register.html BothBoth U.S. GAO reports Information Management: The Challenge of Managing Electronic Records June 17 2010Electronic Records. June 17, 2010. Federal Records: Agencies Face Challenges in Managing E- mails. April 23, 2008. NoneNone
  16. 16. Acquiring historic correspondence at very high risk. With records management systems in place, still a hit or miss proposition Tension between minimized vulnerabilities and keeping historic recordshistoric records Also applicable, policies calling for destruction of email based on non-content criteria (age, number in account, etc.) Without a companion Record Management System Catch as catch can – which usually means it doesn’t get captured I di id l il d t di k tt d t d i f ldIndividual emails saved to a diskette and tossed in a folder Printed and filed Nothing
  17. 17. What we get is what we getg g Proactive acquisition Electronic record management systems Email capture systems EMCAP a joint project of North Carolina andEMCAP, a joint project of North Carolina and Kentucky System-configured declaration or user-declared
  18. 18. Under the hood Classification Records Disposition Schedules Working with an ERMS implementation
  19. 19. Relationships Email administration Disaster recovery plans Policy
  20. 20. Reducing liabilities without losing historyg g Thorough application of records management practices Policy directives supporting acquisition & retentionPolicy directives supporting acquisition & retention of historical documents Ability to constrain access based on litigation or other legal activities Consistent, documented procedures and policies
  21. 21. What is the archival object? The lifecycle question Message by message, or in groups What about attachments and nested emails (threads)? Obsolescence
  22. 22. Using ERMS’sUsing ERMS s Using XML Individual or consortial systems approach? Projects to consultProjects to consult EMCAP – Email Capture & Preservation CERP – Collaborative Electronic Records Project PEDALS – Persistent Digital Archives & Library Systems HUL – Harvard University Libraries
  23. 23. Ricc Ferrante IT Archivist and Director of Digital Services Smithsonian Institution Archives 202-633-5906 FerranteR@si.edu

×