Mailbench
A desktop email client for Kerio Connect mail servers, built with Python and Qt.
Features
- Multi-account support - Connect to multiple Kerio Connect servers
- 3-pane layout - Folders, message list, and preview pane
- Compose, Reply, Forward - Full email composition with HTML support
- WebEngine-based editor - Rich HTML compose with inline image support
- Attachments - View, download, and attach files
- Address book integration - Autocomplete from Kerio contacts and cached addresses
- Local caching - SQLite database for offline message access
- Drag and drop - Move messages between folders
- Block sender/domain - Drag messages to block folders
- Message flagging - Flag important messages
- Keyboard shortcuts - Efficient navigation and actions
- Zoom support - Ctrl+scroll or shortcuts to adjust preview size
Security Features
- Remote image blocking - Prevents email tracking pixels
- External link warnings - Shows domain before opening links
- Phishing detection - Warns about homograph/lookalike domains
- Dangerous attachment warnings - Alerts for executable files
- HTML sanitization - XSS protection for message display
- Secure credential storage - Uses system keyring for passwords
Requirements
- Python 3.10+
- Kerio Connect mail server with JSON-RPC API access
Installation
# Clone the repository
git clone https://github.com/jpsteil/mailbench.git
cd mailbench
# Create virtual environment
python -m venv venv
source venv/bin/activate # On Windows: venv\Scripts\activate
# Install dependencies
pip install -e .
Usage
mailbench
On first run, go to Accounts > Add Account to configure your Kerio Connect server.
The status bar displays a permanent zoom indicator showing the current preview zoom level.
Keyboard Shortcuts
| Shortcut | Action |
|---|---|
| Ctrl+N | New message |
| Ctrl+R | Reply |
| Ctrl+Shift+R | Reply All |
| Ctrl+F | Forward |
| Ctrl+Scroll | Zoom preview |
| Ctrl++ or Ctrl+= | Zoom in |
| Ctrl+- | Zoom out |
| Ctrl+0 | Reset zoom |
| Ctrl+Enter | Send message (in compose) |
| Delete | Delete message |
| Escape | Clear filter / Discard compose |
License
MIT License - see LICENSE file.
1 maintainer
Metadata
1 maintainer
Release files for mailbench 0.5.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mailbench-0.5.8.tar.gz | 272.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mailbench-0.5.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 552.3 kB
Release files / mailbench-0.5.8.tar.gz
| Download URL | mailbench-0.5.8.tar.gz |
|---|---|
| Size | 272.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6189bdd97afe1ae97c03f033384e0d2172fbdbc3d69b5d74fc25e65b16f1d68a
|
|
BLAKE2b-256 checksum How to use checksums |
b56aec60f0aaedfe6c95c49a5c5ba3fbfc0a67d35b2ccbfb0a6f058cb83335f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 19, 2026.
Transparency logRelease files / mailbench-0.5.8-py3-none-any.whl
| Download URL | mailbench-0.5.8-py3-none-any.whl |
|---|---|
| Size | 280.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
13460396de4fea2f20bff0d83d901ae6c4b69a4eb4c07fc5760e1139cbeb9023
|
|
BLAKE2b-256 checksum How to use checksums |
68a940970d21fa0233793512292a30eb2b7c56f3ca859fb2797aab62851255c7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 19, 2026.
Transparency log
