Thanks for the honest feedback.
You’re right that we had issues with email loading, message rendering, and caching in some webmail cases. We’re not going to pretend otherwise. We’ve been fixing these aggressively and shipping several updates per day, including new optimizations for email loading, caching, and shared mailbox performance.
Our support team is also working extremely hard to turn real user reports into fixes quickly. Bugs, workflow issues, and practical feature requests are not being ignored — they are being handled directly and prioritized based on actual customer pain.
For managing many inboxes, we don’t expect users to log into 100 mailboxes one by one. TrekMail already supports shared mailboxes, forwarding, and aliases, so teams can centralize incoming mail without constantly switching accounts.
TrekMail is also MCP-first: an authorized AI agent can work across the mailboxes it has access to and help read, search, organize, and manage mail from one place. Users can also connect TrekMail mailboxes to external email clients/providers that support IMAP/SMTP, including Gmail, if they prefer to manage everything outside our webmail.
We’re also working on an even smoother multi-mailbox IMAP experience, so multiple TrekMail mailboxes — and eventually external mailboxes too — can be managed through one login.
The platform has had rough edges, but it is improving very quickly, and feedback like this directly shapes what we fix next.