Analytics

We should have usage analytics. At the very least the number of emails the bot reads, but at most the properties of each email that was sent. That way we can say x people sent us plaintext emails, y people sent is perfect encrypted and signed emails.

0.2 probably? Though just keeping logs (in an analytics-friendly format) shouldn't be too much work to implement.

Start by locating the email-processing and logging entry points referenced by the issue. Before implementation, clarify whether the scope is aggregate counts or per-email properties, and define the privacy requirements and metrics that would indicate the work is complete.

Written by the indexing model from the issue text.