back to home

linagora / tmail-flutter

A multi-platform (Flutter) application for reading your emails, with your favorite devices, using the JMAP protocol!

View on GitHub
594 stars
118 forks
506 issues

AI Architecture Analysis

This repository is indexed by RepoMind. By analyzing linagora/tmail-flutter in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.

Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.

Source files are only loaded when you start an analysis to optimize performance.

Embed this Badge

Showcase RepoMind's analysis directly in your repository's README.

[![Analyzed by RepoMind](https://img.shields.io/badge/Analyzed%20by-RepoMind-4F46E5?style=for-the-badge)](https://repomind.in/repo/linagora/tmail-flutter)
Preview:Analyzed by RepoMind

Repository Overview (README excerpt)

Crawler view

Twake Mail Client Website • Report Bug --- This project aims at providing a multi-platform mobile email application, running the JMAP protocol and will also deliver additional features to the Twake Mail back-end. Twake Mail is developed with love by Linagora. Here is how Twake Mail looks like on a phone: Here is how Twake Mail looks like on a tablet: Build app • Go to root folder of project • Run script • Build • iOS: • Android: • Web: change in with your JMAP server then run: or you can find our images in: https://hub.docker.com/r/linagora/tmail-web FAQ **Why did you choose JMAP?** Read more... That is a good question! **IMAP** is THE ubiquitous protocol people use to read their emails, THE norm. 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 and standards. Not only does it make applications easier to develop, we also strongly believes it results in an improved experience for the end user. **Can I use Twake Mail with *any* JMAP server?** Yes, you can use the Twake Mail application with any JMAP server and benefits from **Twake Mail**'s ease of use. **I don't understand your app... I need help using it! HELP MEEEEEE...** Read more... Don't worry, we are here! 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). **What platforms do you (plan to) target?** Read more... First, we target Android, iOS mobiles. We also take care of tablets and large rendering space early on in the development process. Then, we plan on introducing a desktop application. This versatility is enabled by the use of the Flutter framework. **What would your roadmap look like?** Read more... Now that we plan having a simple JMAP email client supporting Android, IOS, and a webmail, we are working on some extra features on top of the TeamMail backend, including: • 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. **Any chance to support JMAP extension for calendar, contacts?** No we do not plan to support such extensions, that are currently not standardized as RFCs, nor implemented on the Twake Mail backend. **Do you have a web application for Twake Mail?** Read more... Yes! It is still in early development but we do have one. It's easy for you to use locally, as you can just build a Docker image locally from the sources of this repository, or even use our official Docker image . The web-app needs to include an environment file though (here you can see the dummy at the root of the project), with a 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 by replacing the default value of to the one pointing to your JMAP backend server. Then build your docker image: Then you can just simply run your web-app like this: 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 or just build the docker image locally without any prior changes: From then, create at the root of the project an environment file (like ) where you put the you want to connect to. Then, to mount it and override the default one while running the container: 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: • Generate JWT keys for : • Edit the and set to (with the trailing slash) • Run to bring up both the frontend and the backend. • Run to provision some demo accounts (you don't have to let it run all the way). • The TMail web-app should be available at . The credentials for demo accoun…