PEPS Design Document

This document details PEPS design guidelines. It is important to read for anyone considering deploying PEPS or even more contributing.

Simple things work best

PEPS source is currently close to 30k lines of code. It's quite a bit, but also very little compared to other solutions. Much of PEPS conciseness is due to programming in Opa.

API first

PEPS relies heavily on APIs for extensibility. Therefore, many features that are part of the core source of standard email products should be implemented as standalone applications or services that use the API.

For instance, we don't need core IMAP functionality in PEPS. It's better to adapt existing IMAP servers to use PEPS, through the API, as a provider of messages.