:inbox_tray: An email client that functions like a kanban board.
An email client that functions like a kanban board, for Mac/Windows/Docker. Download the latest release here.
The rest of this readme focuses on the technical details of Kanmail. For user documentation see the Kanmail website.
Before continuing it is important to note that Kanmail is source available but not free. Kanmail is available for free download for evaluation; for continued use of Kanmail a license should be purchased.
We welcome pull requests, but note you will be contributing to a non-free project. You will be required to sign the Oxygem CLA before any contributions can be merged. We offer free license keys to contributors, please email [email protected] for more information.
Python must be configured
--with-framework. See this StackOverflow answer to check whether this is enabled.
To build/release you'll need to intsall GNU tar, which can be done with brew:
brew install gnu-tar
You'll need the Visual Studio build tools.
gtkto install properly you'll need:
apt install build-essential pkg-config git python3-dev libcairo2-dev libgirepository1.0-dev
Kanmail requires Python
3.7. Install the Python requirements with
# Generic development requirements pip install -r requirements/development.txt
Platform specific requirements
pip install -r requirements/[macos|linux|windows].txt
To start the server + webpack-server:
Then go to http://localhost:4420 to view/develop the app in a browser of your choice.
To start the full windowed app, use:
honcho start -f Procfile-app
Note that the webserver does not auto-reload when running in app mode.
Version numbers are generated at build in the date-based format:
Per the pyinstaller documentation, for maximum compatability Kanmail is ideally built on the oldest systems available. MacOS + Linux builds are forward, but not backward, compatible.
Kanmail is currently built on:
Should use the oldest SDK possible. Kanmail will be compatible with the SDK version of any newer versions, but nothing older, so target the oldest realistic SDK, which is currently 10.12 / Sierra. Heavily based on this gist.
export CFLAGS="-isysroot $MACOSXSDK -I$MACOSXSDK/System/Library/Frameworks/Tk.framework/Versions/8.5/Headers -I$BUILD_ENV_PREFIX/include " export LDFLAGS="-isysroot $MACOSXSDK -L$BUILD_ENV_PREFIX/lib " export LD_LIBRARY_PATH="$BUILD_ENV_PREFIX/lib/" export CXXFLAGS="-isysroot $MACOSXSDK -I$BUILD_ENV_PREFIX/include " export CPPFLAGS="-I$MACOSXSDK/usr/include -I$BUILD_ENV_PREFIX/include -I$BUILD_ENV_PREFIX/include/openssl "
Download & untar
./Configure --prefix=$BUILD_ENV_PREFIX \ no-hw no-hw-xxx no-ssl2 no-ssl3 no-zlib zlib-dynamic \ shared enable-cms darwin64-x86_64-cc enable-ec_nistp_64_gcc_128 \ -isysroot$MACOSXSDK \ -mmacosx-version-min=$MACOSX_DEPLOYMENT_TARGET make depend make make install
Download & untar
./configure --prefix=$BUILD_ENV_PREFIX/ \ --enable-ipv6 \ --enable-framework=$BUILD_ENV_PREFIX/Frameworks/ \ --with-openssl=$BUILD_ENV_PREFIX \ MACOSX_DEPLOYMENT_TARGET="$MACOSX_DEPLOYMENT_TARGET" make make install PYTHONAPPSDIR=$BUILD_ENV_PREFIX/Applications
cd $BUILD_ENV_PREFIX/Frameworks/Python.framework/Versions/3.7/bin ln -s python3 python ln -s pip3 pip
Finally install the requirements (from source, no binaries):
pip install pip -U pip install -r requirements/macos.txt
Using this environment should now build apps compatible with MacOS 10.12+. This can be tested by installing a MacOS 10.13 VM.
Should use the oldest libc possible. Currently building using Ubuntu 18 which has libc6 2.27, which is pretty recent.
TBC instructions to build on an older libc.
Currently builds on Windows 10. Unsure if compatible with previous versions.
Building Kanmail should be as simple as running
python -m make.
Kanmail syncs email using the IMAP protocol. Instead of implementing a "complete sync engine" (one which attempts to keep a local copy of the server data), Kanmail uses a cache and loads data on demand. This simplifies the implementation but makes it hard/impossible to behave as an offline email client.
Kanmail keeps in sync with the remote server by checking UID lists. These are cached locally and every "sync" the full list is refreshed, ensuring the local copy is up to date with the server UID list. Email headers are cached against their UIDs.
Currently no actual full email data is cached, only the headers. Meaning when offline Kanmail will load any cached threads into the column view, but it won't be able to open any of these threads.
When Kanmail starts, the UI attempts to get emails for each folder (both columns and "core" folders like archive/drafts) - this API endpoint is always expected to return a valid response, even if empty, and does not require connectivity. If there is a local cache of UIDs and email headers, these will be returned.
Subsequent calls to this API endpoint will load more emails, loading headers from the server as required.
During the lifetime of a running Kanmail app it will periodically request to sync emails with the server. At this time the full UID list is reloaded from the server (failing if offline) and any new email headers are fetched. This endpoint returns new emails and the UIDs of any deleted emails from the UID list.
The Kanmail UI consists of a collection of React apps, one per window "category".
The main Kanmail window, including the column and email thread views. This is where the interesting stuff lives!
Rendering columns can be expensive, so Kanmail uses a few "hacks" to reduce the amount of renders required. For example, when archiving or trashing a thread, it's hidden from the user but the underlying component remains in-place. Only the thread component itself updates and the surrounding column does not re-render.
Kanmail supports navigating between threads and between columns using the keyboard. To achieve this every thread component contains a reference to access the component above/below (other threads same column) and also the adjacent columns left/right. This is achieved using React references.
The send/reply/forward email window and editor.
The settings window. Handles account management as well as general application settings.
The contacts window. Handles add/remove/delete contacts API.
The license window. Add/remove a license key.
The meta/about window, includes license information.