Known issues

This page tracks known gaps in the current MailGate web app. It is intentionally narrower than the feature matrix: these are things you may see in the UI today that are unfinished, only partially wired, or likely to behave incorrectly.

UI present, logic not wired yet

• Reply staking toggle. Settings -> Fees includes a "Require Stake for Reply" switch, but it only changes local UI state. It does not save a preference or enforce reply staking yet.

• Outbox fee confirmation modal. The outbox payment dialog can show a successful confirmation, but the confirm action only closes the local modal path and shows a success toast. It does not submit a real payment transaction from that dialog yet.

Buggy or partially wired

• Group fees may fail to save or delete. Settings -> Fees can load existing sender fee overrides with an auth header, but the save and delete calls use raw /api/... requests without the same authorization plumbing. In authenticated sessions this can still fail with an API auth error.

• Analytics failures can look like empty data. If the analytics requests fail, the page falls back to empty charts and tables instead of showing a clear error state.

• Starred mail is assembled client-side. The Starred folder currently aggregates messages from other folders in the frontend because there is no dedicated backend endpoint yet. It can be slower and may not behave like a first-class mailbox view.

Still expected limitations

These are not bugs, but they are still unfinished product areas:

• No native mobile app.
• No IMAP or POP3 support.
• No calendar product.
• Contacts are a simple whitelist/blacklist-oriented list, not a full address book.
• Custom domains and full DKIM/SPF/DMARC management are still incomplete.