Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Be an e-mail client #1

Open
9 of 43 tasks
BjarniRunar opened this issue May 13, 2022 · 0 comments
Open
9 of 43 tasks

Be an e-mail client #1

BjarniRunar opened this issue May 13, 2022 · 0 comments

Comments

@BjarniRunar
Copy link
Member

BjarniRunar commented May 13, 2022

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:

  • 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
  • Secure context - enforce mandatory security settings (always encrypt etc.)
  • Collaborative e-mail composition
  • Moderated outbox
  • Automation: Snooze
  • Automation: Scheduled send
  • Automation: Auto-reply to certain messages (out of office, etc.)
  • Automation: Webhooks or running external commands
  • Block a sender (generate bounces and send to junk?)
  • Calendar integration of some sort
  • Mailing list functionality (combined with the calendar and remote access, this can become an event planner)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant