Difference between revisions of "Email Archive"

From Eugene Eric Kim
Eekim>Adsl-68-120-137-231.dsl.snfc21.pacbell.net
 
m (2 revisions: Importing pages from old eekim.com PurpleWiki)
Line 1: Line 1:
A decent email archiving solution has been the Holy Grail for me for sometime.  I'm going to consolidate some of my many notes here and add some new ones. {nid IET}
A decent email archiving solution has been the Holy Grail for me for sometime.  I'm going to consolidate some of my many notes here and add some new ones.


= Brainstorm {nid IEU} =
== Brainstorm ==


* Integration into CRM systems, or CRM-like functionality. {nid IEV}
* Integration into CRM systems, or CRM-like functionality.
* Store everything in mbox, with metadata in database.  Possibly use [http://eyebrowse.tigris.org/ eyebrowse] schema. Also examine [http://search.cpan.org/~simonw/Email-Store-0.24/ Email::Store]. Storing as mbox enables me to read archives in mail clients or via IMAP. Separate into incoming and outgoing mailboxes by month. Messages only archived once. {nid IEW}
* Store everything in mbox, with metadata in database.  Possibly use [http://eyebrowse.tigris.org/ eyebrowse] schema. Also examine [http://search.cpan.org/~simonw/Email-Store-0.24/ Email::Store]. Storing as mbox enables me to read archives in mail clients or via IMAP. Separate into incoming and outgoing mailboxes by month. Messages only archived once.
* Tags. Can be used to define project archives. Can export these as mboxes. {nid IEX}
* Tags. Can be used to define project archives. Can export these as mboxes.
* Archive.  A proper mailing list archiver could be used for personal archives as well. {nid IEY}
* Archive.  A proper mailing list archiver could be used for personal archives as well.
* SocialNetwork analysis. Who's in my social network based on a window of time? {nid IEZ}
* [[Collab:Social Network]] analysis. Who's in my social network based on a window of time?


= Features {nid IF0} =
== Features ==


* Addressability. Every email has an address, possibly based on message-ID. Functionality probably enabled by web archives.  Could potentially use XRI. Addressability lets me annotate, integrate with other PIM apps, etc.  Obviously want granular addressability as well, perhaps via PurpleNumbers. {nid IF1}
* Addressability. Every email has an address, possibly based on message-ID. Functionality probably enabled by web archives.  Could potentially use XRI. Addressability lets me annotate, integrate with other PIM apps, etc.  Obviously want granular addressability as well, perhaps via [[Forge:Purple Numbers]].
* Access control via i-names. Message-by-message access policy, or if I'm really ambitious, granular access control (i.e. paragraphs in emails). Tag policy. Basically, access control is tied to addresses. So threads would have an address, tagged archives would have an address, individual emails would have an address, etc. Hence, all of these things are access controllable. {nid IF2}
* Access control via i-names. Message-by-message access policy, or if I'm really ambitious, granular access control (i.e. paragraphs in emails). Tag policy. Basically, access control is tied to addresses. So threads would have an address, tagged archives would have an address, individual emails would have an address, etc. Hence, all of these things are access controllable.
* Map email addresses to individuals.  A search for EugeneEricKim would turn up emails from hcs.harvard.edu, ddj.com, blueoxen.org, eekim.com, etc. {nid IF3}
* Map email addresses to individuals.  A search for [[Eugene Eric Kim]] would turn up emails from hcs.harvard.edu, ddj.com, blueoxen.org, eekim.com, etc.
* Reporting. How quickly do I respond to individuals? What times do I send email? Some of this stuff may not be appropriate for archives, because I don't archive ''all'' email. {nid IF4}
* Reporting. How quickly do I respond to individuals? What times do I send email? Some of this stuff may not be appropriate for archives, because I don't archive ''all'' email.


= Sorting Mailboxes {nid IF8} =
== Sorting Mailboxes ==


= Tips and Tricks {nid IF9} =
== Tips and Tricks ==


mutt searching: Use 'l' to do 'limit' searches and use ~t, ~f, and ~b in AND combinations to limit on To: From: and body of messages. It's lovely only having to look in one place! {nid IFA}
mutt searching: Use 'l' to do 'limit' searches and use ~t, ~f, and ~b in AND combinations to limit on To: From: and body of messages. It's lovely only having to look in one place!


= Tools {nid IF5} =
== Tools ==


* [http://archivemail.sourceforge.net/ archivemail] {nid IFB}
* [http://archivemail.sourceforge.net/ archivemail]
* [http://www.weirdkid.com/products/emailchemy/index.html Emailchemy] -- converts different formats to RFC2822. {nid IF7}
* [http://www.weirdkid.com/products/emailchemy/index.html Emailchemy] -- converts different formats to RFC2822.
* [http://grepmail.sourceforge.net/ grepmail] {nid IFC}
* [http://grepmail.sourceforge.net/ grepmail]
** [http://www.barsnick.net/sw/grepm.html grepm] {nid IFD}
** [http://www.barsnick.net/sw/grepm.html grepm]
* [http://www.rpcurnow.force9.co.uk/mairix/ mairix] {nid IFE}
* [http://www.rpcurnow.force9.co.uk/mairix/ mairix]
* [http://mbox2mysql.sourceforge.net/ mbox2mysql] {nid IF6}
* [http://mbox2mysql.sourceforge.net/ mbox2mysql]
* [http://zoe.nu/ zoe] {nid IFF}
* [http://zoe.nu/ zoe]
* http://www.emailman.com/conversion/ -- tools for converting between mailbox formats {nid IFG}
* http://www.emailman.com/conversion/ -- tools for converting between mailbox formats


* http://www.transend.com/ConnectorWare/index.html {nid IFH}
* http://www.transend.com/ConnectorWare/index.html
* http://www.gssnet.com/products/prod_mwiz.htm {nid IFI}
* http://www.gssnet.com/products/prod_mwiz.htm
* http://www.compusven.com/products/shuttle.html {nid IFJ}
* http://www.compusven.com/products/shuttle.html
* http://www.comaxis.com/prices.htm {nid IFK}
* http://www.comaxis.com/prices.htm

Revision as of 16:50, 20 May 2010

A decent email archiving solution has been the Holy Grail for me for sometime. I'm going to consolidate some of my many notes here and add some new ones.

Brainstorm

  • Integration into CRM systems, or CRM-like functionality.
  • Store everything in mbox, with metadata in database. Possibly use eyebrowse schema. Also examine Email::Store. Storing as mbox enables me to read archives in mail clients or via IMAP. Separate into incoming and outgoing mailboxes by month. Messages only archived once.
  • Tags. Can be used to define project archives. Can export these as mboxes.
  • Archive. A proper mailing list archiver could be used for personal archives as well.
  • Collab:Social Network analysis. Who's in my social network based on a window of time?

Features

  • Addressability. Every email has an address, possibly based on message-ID. Functionality probably enabled by web archives. Could potentially use XRI. Addressability lets me annotate, integrate with other PIM apps, etc. Obviously want granular addressability as well, perhaps via Forge:Purple Numbers.
  • Access control via i-names. Message-by-message access policy, or if I'm really ambitious, granular access control (i.e. paragraphs in emails). Tag policy. Basically, access control is tied to addresses. So threads would have an address, tagged archives would have an address, individual emails would have an address, etc. Hence, all of these things are access controllable.
  • Map email addresses to individuals. A search for Eugene Eric Kim would turn up emails from hcs.harvard.edu, ddj.com, blueoxen.org, eekim.com, etc.
  • Reporting. How quickly do I respond to individuals? What times do I send email? Some of this stuff may not be appropriate for archives, because I don't archive all email.

Sorting Mailboxes

Tips and Tricks

mutt searching: Use 'l' to do 'limit' searches and use ~t, ~f, and ~b in AND combinations to limit on To: From: and body of messages. It's lovely only having to look in one place!

Tools

Retrieved from "https://wiki.eekim.com/w/index.php?title=Email_Archive&oldid=562"