Make it possible to use this as a library.

[Yawning]

It occurs to me that this could be used as a library instead of as a daemon by bolting on a different external facing interface to let people send/receive messages.

This will probably save a lot of people, a lot of pain and suffering (#9).

[david415]

• send message
• notification when receive queue transitions to non-empty
• possibly expose pop3 session objects for message retreival
• stuff for adding/removing/querying recipients public keys

[Yawning]

I totally put in the wrong bug for the commit that added the receive side support, because I'm dumb, here it is: 80a099367456f6faab4bdda862e02f93301e36ad

Out of what planned for the first path, the main thing left to do is some sort of flexible event notification system so that callers know when to call the receive APIs. But if people are ok with polling periodically for now, it should be possible to send, receive, and add/remove/query recipients, which is probably the bare minimum for doing development against this.

[Yawning]

I'm calling this done now, because people are using this as a library. Improvements will be tracked under #23.