OE Email

From Jonathan Gardner's Tech Wiki
Jump to: navigation, search

Overview

An implementation of some of the concepts of Organize Everything.

What it is

It is made of two parts.

  1. An email service. This will send and receive email.
  2. An email client. This will communicate with the service.

What the Service Does

  • Sends email. Does whatever is necessary to inject the email properly in the system. If the email is sent to another OE Email server, then it treats it differently.
  • Receives email. Incoming email is not just stored, but read. It is parsed and everything useful from the email is extracted.
  • Stores user preferences. It remembers which messages you like to read, and when. It keeps track of your behavior depending on the time of day, day of the week, and even date of the year.
  • Stores templates. When you are composing a mail, it will recognize when you are doing something similar like you've done before. Templates are automatic.
  • Archives email. Nothing is ever lost. It no longer has to be.

The email system understands certain concepts such as identity. This is part of the identity service and should be s

Data is stored in some sort of database, probably SQLite or maybe something less harmless. The data storage service may need to be separated out.

What the Client Does

Provides seamless integration with the service.

  • Web client
  • GUI client (Qt, PyQt)