Feature Ideas

Sorting emails by sender is, own my opinion, a basic function of every email client. It helps to sort through emails quickly and clear unwanted emails or move them to folders. I find it amazing that Canary Mail does not have this feature. It is also noted that Canary Mail's own website promotes sorting emails by sender (https://canarymail.io/blog/manage-and-organize-emails/): 'Group by the sender: Another way to organize your inbox is by grouping messages from specific senders together. This can be particularly useful if you work with a lot of different people and want to quickly find messages from a particular colleague or client.' So, why is this function not there?

To help combat phishing, I would like to have full email address visible all the time, not just the "friendly name". It's too easy to be lulled into a sense of security without seeing the full email address.

It is easy to translate outgoing emails, but there is no option to translate incoming ones. Can you add this function?

You can set it up for mails with the condition that only sends you a reminder if they dont replay or send a reminder even if they replay

Congrats re: integrations. This is game changer. Can we expect an integration with Apple’s Reminder anytime soon? Also, this would be awesome to have integrations options in swipes for quicker access/process. Best

Prevents getting repeated emails that aren't needed

Signing and encrypting e-mails using S/MIME is common practice in the business world. So in order to get useful in a business environment, an e-mail client should support S/MIME.

JMAP brings incredible speed to synch or search for email compared to IMAP. Next generation of email service is using JMAP (Fastmail, stalwart, Thundermail, Twake…). Canary should not miss this train

Just like it's done in Apple mail and Gmail app, can we enable the option to copy OTPs from incoming emails to the keyboard. iOS 26 onwards has opened this code to 3rd party software which was prior limited to only Apple native apps.

Canary's built-in copilot is useful, but it only sees Canary. My work doesn't live in Canary. It lives in a CRM, a database, project docs, spreadsheets, internal scripts, and a set of AI agents I've already built around them. An assistant that can read my mail but nothing else is answering half the question, and an assistant that knows everything except my mail has the same problem in reverse. That gap isn't a feature gap, it's an architecture gap. No mail client is going to integrate my stack for me, and I don't want it to. What I need is an entry point: a standard interface that lets whatever assistant or agent I use reach the mail, alongside everything else it already reaches. MCP (Model Context Protocol) is that interface. It's an open, vendor-neutral standard, already supported by the major assistants and by custom agents, local models included. Canary shipping an MCP server means one implementation on your side and compatibility with the entire ecosystem, present and future, rather than one integration per vendor. The key point: Canary already holds the decrypted mail locally. An MCP server runs locally too. The mail is read on the machine, by a client I chose, without shipping the mailbox to anyone's cloud. That is strictly more private than most of the alternatives people fall back on today, which is pasting mail into a web chat. Read access first, that alone unlocks most of the value: search_messages (query, sender, date range, folder, attachments)get_message / get_thread (headers, body, attachment list)list_accounts / list_folders / list_labelsget_unread_summary Write access as an optional, opt-in second stage: create_draft (drafts only, never send)mark_read / archive / move / label Controls that make this safe to ship: Disabled by default, enabled per accountExplicit scope: read-only vs read + draftNo send capability over MCP, ever. Drafts get reviewed in CanaryPer-account, per-folder and per-sender exclusionsA visible activity log of what was read and what was done What this makes possible, none of which an in-app copilot can do: Cross-reference an incoming thread against the deal record in the CRMPull figures out of supplier emails and reconcile them against the accounting dataFeed mail context into an existing internal agent or reporting pipelineAnswer "what did we commit to this client, and where does the project actually stand" using mail plus the systems that hold the real state Canary is already the mail client for people who care about privacy and want AI to be genuinely useful. MCP is how you serve the users whose data gravity sits outside your app, without becoming an integration platform yourself. The internal copilot stays the easy default. MCP is the door for everyone whose work is bigger than their inbox.

Out of office replies would be very useful when OOO. This is an important feature for those using Canary for work.

Many service provider (including EM Client, Super Human & Outlook) have this feature of creating direct meeting link from calendar. Please integrate the same.

I have multiple accounts that I use mostly for spam and registering for accounts I'm not gonna use much - I don't want to see their emails in my main inbox as they're usually not what I'm interested in, but I'd still like quick access to them (which is why I have them added in Canary)

🤟🏻 Hi Change the possibility of changing the font size to the same system as macOS. This is the same case with font selection.