A program to store mailing list archives
“Modifying” means that the archive is not really an archive, rather it is a living document like a wiki: it can be modified (hopefully improved) by collaborators.
Emails (that are e.g. sent to a mailing list) are downloaded by Heapkeeper. After an email is downloaded, it is called a post. Posts are stored in Heapkeeper’s database, which is called the heap. The heap is stored in a set of text files; each file contains one post. Posts can be changed either from Heapkeeper’s console interface or by directly modifying the text files in which the posts are stored. Posts are organized in threads, as emails in mailing list archives usually are. Posts may have tags as well.
When modifying the heap, the content of the posts can be modified, threads can be restructured, tags can be added; or really anything can be done. If Heapkeeper’s console interface does not support the kind of modification that is to be performed, the user can either write a custom command using Python, or modify directly the files that store the posts. HTML index pages can be generated to display certain views of the heap. One of the most simple indices is just showing all posts in a threaded structure. When the user clicks on a post in an index in the browser, the browser will display the HTML generated from the corresponding post.
- Storing posts in text files. These are human readable files with a format that is similar to the standard email file format (RFC 2822).
- Downloading new emails via the IMAP SSL protocol.
- Console interface with commands to modify the heap. This is actually a Python shell with functions.
- Generating HTML pages from the heap.
In a hurry? Add it to your Download Basket!
What's New in This Release:
- The code was refactored.
- The JsTestDriver unit testing tool is now used.