wtf is email?

This repository is a self-hosted email management tool built for people who juggle many mailboxes at once. It connects to accounts through Outlook and Hotmail's official login system and Microsoft's Graph API, falls back to standard IMAP when needed, and also works with regular providers like Gmail, QQ, 163, 126, Yahoo, and Alibaba Mail, plus custom IMAP servers. It additionally integrates several disposable, temporary email providers for generating throwaway addresses. The tool ships as a web application with a four column layout: a tree of folders for organizing accounts into groups, a list of mailboxes within the selected group, a list of messages in the chosen mailbox, and a detail pane for reading a selected message. Groups and individual accounts can each be routed through their own HTTP or SOCKS5 proxy. Accounts can be tagged, exported, moved between groups in bulk, and deleted individually or in bulk. Beyond reading mail, the tool can automatically forward incoming messages by account, either by email through SMTP or by pushing them to Telegram, with options to limit forwarding to a recent time window and to include or exclude junk mail. It also manages OAuth token refresh for Outlook and Hotmail accounts, supporting scheduled refresh on a cron style timer and bulk actions across many accounts at once. A separate WebDAV backup feature can automatically upload exported account and mailbox data on a schedule. For automation, the project exposes an external API that lets other programs fetch mail directly using an API key instead of logging in through the web interface, with support for alias addresses and combined folder views. You can run it by downloading a prebuilt Windows or macOS app, by pulling a Docker image, or by cloning the Python source and running it directly with pip. A password protected login screen guards the web interface, along with basic security measures like rate limiting and audit logging. The README notes the service should run as a single worker process, since some background tasks rely on short-lived state kept in memory.