campadrenalin / ejmail Goto Github PK

To, from, etc. This exists to some degree already.

When EJTP 0.9.0 comes out, take advantage of the EJForward module to replace EJMail store and forward semantics. This will reduce the EJMail protocol to one simple message type, ejmail-message.

Set up the bit of code that actually supports network access over EJTP. Two mailboxes should be able to send and receive basic data.

Write a first draft of the basic classes necessary for the project: Mailbox, Message, and Conversation. Network communication does not need to work for this, but all properties and linkages must be set up, and all unit tests must pass.

Currently, libcps is only used for its interface as a placeholder - its persistent storage abilities are not set up at all. This is a necessity for storing an EJMail mailbox.

This ticket is basically just a block on the libcps ticket for anydbm support.

No greater test of backend quality than a nice graphical interface, eh? For ours, we'll be using PyKDE4, which is old enough to import properly in Debian Stable (I wasn't sure, so I checked). This ticket will probably have a lot of subtickets involving designing the look, building the KApplication, etc. I'll be learning PyKDE4 for this, so it should be "exciting", in the "dammit I have to learn stuff" sense.

EJMail is going to come in two components, much like DoctestAll. A library portion, where most of the code is located for modularity, and a client script for the command line (and eventually a Qt-based client as well).

This ticket involves the design of the EJMail API. From the point of view of another library, program, or system using EJMail, what grain of control do we want? What kind of interface will be friendly, and make it easy to integrate things like EJForward and EJIdent when they come out? That's exactly what I'm trying to determine now.

Few changes I'd like to make.

1. Conversations should not be first class citizens. They should be like a label. No class necessary.
2. Protocol should have two message types: ejmail-message and ejmail-mark. ejmail-mark marks specific messages as read, as well as functioning as an implicit request for any messages that are unread.