Start talking about Maildir. It makes sense
This commit is contained in:
@@ -13,13 +13,15 @@ We need:
|
||||
* Serve autodiscovery bumpf
|
||||
* ActiveSync protocol
|
||||
* Storage
|
||||
* Give it a home directory. Stores Maildirs + settings DB + TLS
|
||||
* Accounts
|
||||
* Passwords!
|
||||
* Emails
|
||||
* TLS keys + certificates
|
||||
* Search emails - some sort of inverted index necessary
|
||||
* Emails go into Maildirs
|
||||
* Search emails - some sort of inverted index necessary. One per maildir?
|
||||
* https://github.com/blevesearch/bleve ?
|
||||
* Embedded database best. Ideally we have a single file to work with
|
||||
* Settings DB should be a simple K-V store for accounts, passwords, etc. BoltDB?
|
||||
* https://github.com/coreos/bbolt
|
||||
* https://github.com/asdine/storm
|
||||
|
||||
@@ -52,3 +54,5 @@ The message body is being stored inefficiently (json []byte, so base64-encoded)
|
||||
|
||||
Message username and mailbox are indexed, but is that good enough? Perhaps we
|
||||
should have a bucket per mailbox or something?
|
||||
|
||||
TODO: rewrite this (and the code) to make Maildir into a thing
|
||||
|
Reference in New Issue
Block a user