Discussed the specs for assignments 1 and 2, broadly. Sanket has done first-level exploration.

On Monday he will give the pseudo-code for Assgmt 1, with actual function calls to Mail::IMAPClient module. After that, he'll write the code for it. Some small spec additions were also discussed.

After Assgmt 1 is done, he'll write pseudo-code for Assgmt 2, where he will use the MIME-tools module in addition to the Mail::IMAPClient module.

Today, I discussed four assignments for Sanket, of which he will do the first two and then we'll see whether we want him to continue with 3 and 4. If not, we'll put him into development for Merce, initially for UI and simpler modules.

The four assignments are:

1. IMAP message expiry: expire messages from a given IMAP folder based on:
   • size (total size of all messages in folder in MB)
   • age (delete the oldest messages)
   • number of messages (put a cap on msg count of mailbox)
2. IMAP message attachment compress: pull out messages which have large attachments, compress attachments, re-construct the message and replace old (larger) message with new (smaller) version.
3. IMAP message search: pull out each message in an IMAP folder, decode attachments, and use Lucene to index and search through each message body and attachment. This module could become very high priority if we begin work on searchable information repository.
4. Two-way IMAP replication: replicate an IMAP message folder between two servers, mirroring all changes done on one server to the other one. Modify IMAPsync to achieve this, not writing code from scratch. User should be able to use any of the replicas and add/delete messages to it, and it'll get mirrored to the other copy when the sync program runs next time.

Next action point: Jignesh and Sanket will return to me on Friday 19 Sep evening and give me their one-page specs for items 1 and 2, which we will then discuss. In the meantime, Sanket will understand the tasks and will begin studying IMAPsync source.