Yet IMAP had been designed in another age, which resulted in a chatty patchwork of extensions. IMAP lacks decent synchronization primitives to address real-time challenges modern mobile fleet requires, it consumes a lot of bandwidth, requires a lot of round trips which means high latency.

We are not alone to say this! Big players of the field started their own proprietary protocols to address IMAP flaws, and inter-operable standard was yet to be found...

This, is where JMAP comes to play! JMAP builds on decades of experience, and beautifully addresses these challenges using HTTP and JSON standards. Not only does it make applications easier to develop, we also strongly believes it results in an improved experience for the end user.

We plan on writing a user documentation, helping you navigating around the application, and detailing the few configurations you have to perform.

If what you are looking for is not in the user guide then ask us directly in the issues first, we would be glad to help. But also glad to improve our documentation and maybe tweak slightly our UI (user interface).

Then, we plan on introducing a desktop application.

This versatility is enabled by the use of the Flutter framework.

• Better filters, with more actions, and combining conditions
• Restoring deleted messages
• Delegating full access to others for instance your security
• Labels for better sorting your emails across folders
• Automated actions: archiving, emptying your trash, your spam folders
• Running filters against a folder
• Attachment thumbnails

We are also planning active work on drag and drops and other user experience / productivity enhancements.

We do not currently plan working on desktop applications, on websockets for push on top of TeamMail web but such contributions would be appreciated. We also welcome feedback and pull requests regarding Team-Mail portability (running TeamMail on top of third party mail servers).

First, we plan to write a simple, multi-platform JMAP email client. This includes reading your mails and mailboxes, managing them, sending emails, searching your emails. This will likely keep us busy by the end of 2021.

Then, we have plan for multiple features including:

• Support for Twake Mail encrypted mailbox (GPG)
• Interactions with some other software from Linagora including:
  • Sending attachments via TDrive file sharing platform.
  • Transferring some attachments you received to TDrive file sharing platform.
  • Discussing some emails you received via Twake chat.

The web-app needs to include an environment file though (here you can see the dummy env.file at the root of the project), with a SERVER_URL parameter, so it knows to which backend it needs to connect to.

For this to run it locally for example, 2 ways:

Edit the environment file before the build

Edit the env.file by replacing the default value of SERVER_URL to the one pointing to your JMAP backend server. Then build your docker image:

docker build -t tmail-web:latest .

Then you can just simply run your web-app like this:

docker run -d -ti -p 8080:80 --name web tmail-web:latest

Then go to http://localhost:8080 and you should be able to login against your JMAP backend using the Twake Mail web-app.

Mount an environment file when running the container

You can use our official image linagora/tmail-web or just build the docker image locally without any prior changes:

docker build -t tmail-web:latest .

From then, create at the root of the project an environment file (like env.dev.file) where you put the SERVER_URL you want to connect to. Then, to mount it and override the default one while running the container:

docker run -d -ti -p 8080:80 --mount type=bind,source="$(pwd)"/env.dev.file,target=/usr/share/nginx/html/assets/env.file --name web tmail-web:latest

Then go to http://localhost:8080 and you should be able to login against your JMAP backend using the TMail web-app.

Using the docker-compose file

We also include a docker-compose.yaml file so you can get a testing environment up quickly. This use our tmail-backend image for the JMAP server.

Here are the steps to setup:

1. Generate JWT keys for tmail-backend:

openssl genpkey -algorithm rsa -pkeyopt rsa_k