You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that these are only user-visible features. The underlying architecture and low level capabilities needed to realize them, are not listed. That is why so few boxes are ticked so far, in spite of months of work.
Features aren't strictly in order of importance, but work will probably progress roughly from top-to-bottom, modulo deviations when I get excited about something.
Basic non-networked features:
Read local (mbox, Maildir) email
Handle attachments
Delete email from local (mbox, Maildir) mailboxes
Move email from one mailbox to another
Notify user that new mail has arrived
Add messages to a search engine
Allow user to search for mail
Handle message threads correctly
Display HTML and text content
Compose
Reply
Forward
Send (local sendmail)
Tag / untag emails manually
Tag / untag emails automatically (manual filters and bayesian)
Networking capabilities:
Read remote (IMAP, POP3) email
Delete email from remote (IMAP, POP3) mailboxes
Send (SMTP/submission)
Once all of the above are ticked, we can call it moggie 1.0 and open up to outside users.
Features Mailpile had:
Build a web interface
The ability to print an e-mail
Internationalized messages/strings
Encrypt/decrypt/sign/verify e-mail using PGP and/or Autocrypt
Optionally encrypt all local data
Offer password recovery using Passcrow
Route most network access over Tor
Take care with TLS certificates (Mailpile's TOFU was quite good!)
Remote access, via. PageKite and/or Tor
Automation: Time-based tag/untag
Read / import data from legacy Mailpile installations (and maybe other mail clients)
Admin-friendly way to configure Moggie for use by multiple (tens, not thousands of) users
If everything above this line works, we can call it Mailpile 2.0
Most likely, mailpile 2.0 will be what we call the web interface, moggie will be the back-end, CLI tools and text client.
New ideas I am excited about:
Send directly to another Moggie user, bypassing all servers?
Grant remote access to a subset of e-mail, to a remote user
Understand mail-delivery failures, explain clearly to user
This is what passes for a roadmap, for now!
Note that these are only user-visible features. The underlying architecture and low level capabilities needed to realize them, are not listed. That is why so few boxes are ticked so far, in spite of months of work.
Features aren't strictly in order of importance, but work will probably progress roughly from top-to-bottom, modulo deviations when I get excited about something.
Basic non-networked features:
Networking capabilities:
Once all of the above are ticked, we can call it moggie 1.0 and open up to outside users.
Features Mailpile had:
If everything above this line works, we can call it Mailpile 2.0
Most likely, mailpile 2.0 will be what we call the web interface, moggie will be the back-end, CLI tools and text client.
New ideas I am excited about:
The text was updated successfully, but these errors were encountered: