<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <id>https://help.inboxmcp.io/en/changelog</id>
    <title>inboxmcp Changelog</title>
    <updated>2026-07-08T00:00:00.000Z</updated>
    <generator>https://github.com/jpmonette/feed</generator>
    <link rel="alternate" href="https://help.inboxmcp.io/en/changelog"/>
    <subtitle>Releases von inboxmcp.io</subtitle>
    <icon>https://help.inboxmcp.io/en/img/favicon.svg</icon>
    <rights>© 2026 SERGO GmbH</rights>
    <entry>
        <title type="html"><![CDATA[Faster search, sent folder, and clearer error messages]]></title>
        <id>https://help.inboxmcp.io/en/changelog/reliability-update-search-sent-errors</id>
        <link href="https://help.inboxmcp.io/en/changelog/reliability-update-search-sent-errors"/>
        <updated>2026-07-08T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Three improvements from the last release that make a real difference day-to-day on]]></summary>
        <content type="html"><![CDATA[<p>Three improvements from the last release that make a real difference day-to-day on
classic IMAP mailboxes.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="search_mails-is-much-faster--and-now-supports-a-date-range"><code>search_mails</code> is much faster — and now supports a date range<a href="https://help.inboxmcp.io/en/changelog/reliability-update-search-sent-errors#search_mails-is-much-faster--and-now-supports-a-date-range" class="hash-link" aria-label="Direct link to search_mails-is-much-faster--and-now-supports-a-date-range" title="Direct link to search_mails-is-much-faster--and-now-supports-a-date-range" translate="no">​</a></h2>
<p>Until now, <code>search_mails</code> always searched both the subject and the message body on
classic IMAP servers. On servers without a full-text index (Strato, Fastmail, most
shared-hosting providers) that turned every query into a linear scan across the
folder — long enough that the Claude client would sometimes hit its timeout and
give up.</p>
<p>Starting now, the default is <strong>subject-only</strong>. For the rare case where you really
do want to search the body, two new parameters:</p>
<ul>
<li class=""><code>includeBody: true</code> — also searches the message body. Can be slow on large
folders without an index.</li>
<li class=""><code>since: "2026-06-01"</code> and <code>before: "2026-07-01"</code> — restricts the search to a date
range. Translated directly to IMAP (<code>SINCE</code> / <code>BEFORE</code>) and combines with
<code>includeBody</code>.</li>
</ul>
<p>Microsoft 365 still uses Graph — the switch is transparent there and <code>includeBody</code>
now toggles between <code>$filter contains(subject,…)</code> (fast, chronological order) and
<code>$search</code> (relevance order, full header + body).</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="sent-messages-now-reliably-end-up-in-the-sent-folder">Sent messages now reliably end up in the Sent folder<a href="https://help.inboxmcp.io/en/changelog/reliability-update-search-sent-errors#sent-messages-now-reliably-end-up-in-the-sent-folder" class="hash-link" aria-label="Direct link to Sent messages now reliably end up in the Sent folder" title="Direct link to Sent messages now reliably end up in the Sent folder" translate="no">​</a></h2>
<p>On classic IMAP/SMTP, sent messages were delivered correctly but not copied into
the mailbox's Sent folder — the mail was only visible on the recipient's side.
Fixed. After the SMTP handover, <code>send_mail</code> now performs a best-effort IMAP APPEND
into the right Sent folder (detected via the <code>\Sent</code> special-use flag or a list of
common names: <code>Sent</code>, <code>Sent Items</code>, <code>INBOX/Sent</code>, <code>INBOX.Sent</code>, <code>INBOX.Sent Items</code>).</p>
<p>Microsoft 365 continues to set <code>saveToSentItems=true</code> on the Graph call — this was
never an issue there.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="clear-errors-instead-of-timeouts-for-mailbox-in-use">Clear errors instead of timeouts for "Mailbox in use"<a href="https://help.inboxmcp.io/en/changelog/reliability-update-search-sent-errors#clear-errors-instead-of-timeouts-for-mailbox-in-use" class="hash-link" aria-label="Direct link to Clear errors instead of timeouts for &quot;Mailbox in use&quot;" title="Direct link to Clear errors instead of timeouts for &quot;Mailbox in use&quot;" translate="no">​</a></h2>
<p>When two sessions open the same IMAP mailbox at the same time, Dovecot (including
the default Plesk configuration) temporarily rejects the second with "Mailbox is
in use". Until now that arrived at the AI assistant as a generic error.</p>
<p>We now retry internally up to three times with a short backoff — the vast majority
of these collisions clear within 250–600 ms. If it doesn't clear, we return a
clear message:</p>
<blockquote>
<p><em>The mailbox "Team Support" is currently open in another session. Please try
again in a few seconds.</em></p>
</blockquote>
<p>Every error now also carries a <strong>correlation ID</strong> so we can find the exact request
in our logs when you contact support.</p>
<hr>
<p>All of the above is active on <strong>every plan</strong> and needs no change in the portal or
the AI assistant. Feedback to
<a href="mailto:support@inboxmcp.io?subject=Reliability%20Update" target="_blank" rel="noopener noreferrer" class="">support@inboxmcp.io</a>.</p>]]></content>
        <author>
            <name>inboxmcp</name>
            <uri>https://inboxmcp.io</uri>
        </author>
        <category label="improvement" term="improvement"/>
        <category label="mcp-tools" term="mcp-tools"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Help center online]]></title>
        <id>https://help.inboxmcp.io/en/changelog/help-center-live</id>
        <link href="https://help.inboxmcp.io/en/changelog/help-center-live"/>
        <updated>2026-05-24T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[The new help center at help.inboxmcp.io is here.]]></summary>
        <content type="html"><![CDATA[<p>The new help center at <a href="https://help.inboxmcp.io/" target="_blank" rel="noopener noreferrer" class="">help.inboxmcp.io</a> is here.</p>
<!-- -->
<p>With help articles, documentation, per-AI-tool guides, this changelog and a roadmap.
Available in English and German.</p>
<p>Feedback at <a href="mailto:support@inboxmcp.io?subject=Help-Center%20Feedback" target="_blank" rel="noopener noreferrer" class="">support@inboxmcp.io</a>.</p>]]></content>
        <author>
            <name>inboxmcp</name>
            <uri>https://inboxmcp.io</uri>
        </author>
        <category label="docs" term="docs"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Microsoft 365 as a mailbox provider]]></title>
        <id>https://help.inboxmcp.io/en/changelog/microsoft-365-provider</id>
        <link href="https://help.inboxmcp.io/en/changelog/microsoft-365-provider"/>
        <updated>2026-05-23T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[inboxmcp now supports Outlook / Exchange Online via OAuth. Authentication runs]]></summary>
        <content type="html"><![CDATA[<p>inboxmcp now supports <strong>Outlook / Exchange Online</strong> via OAuth. Authentication runs
directly with Microsoft; neither a password nor an app password is stored on the
inboxmcp side.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="feature-set">Feature set<a href="https://help.inboxmcp.io/en/changelog/microsoft-365-provider#feature-set" class="hash-link" aria-label="Direct link to Feature set" title="Direct link to Feature set" translate="no">​</a></h2>
<ul>
<li class=""><strong>Own mailbox with Microsoft sign-in</strong> — sign in through the Microsoft OAuth flow,
confirm access. The refresh token is encrypted with an asymmetric envelope scheme
before it's stored.</li>
<li class=""><strong>Shared mailboxes</strong> — add a delegate mailbox of a connected Microsoft account
without a second sign-in. Before saving, inboxmcp verifies access once via Microsoft
Graph; if the check fails, no entry is created.</li>
<li class=""><strong>Folder hierarchy</strong> — nested folders (e.g. <code>Archive/2024/Customers</code>) are correctly
resolved in <code>list_folders</code> and every other tool.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="mcp-tools">MCP tools<a href="https://help.inboxmcp.io/en/changelog/microsoft-365-provider#mcp-tools" class="hash-link" aria-label="Direct link to MCP tools" title="Direct link to MCP tools" translate="no">​</a></h2>
<p>Available immediately — Read: <code>list_mailboxes</code>, <code>list_folders</code>, <code>search_mails</code>,
<code>read_mail</code>, <code>read_mail_chunk</code>, <code>get_attachment</code>. Write (Premium / Business):
<code>draft_mail</code>, <code>edit_draft</code>, <code>create_folder</code>, <code>move_mails</code>. The remaining write tools
<code>send_mail</code>, <code>flag_mail</code> and <code>delete_mail</code> are coming across all providers.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="not-yet-included">Not yet included<a href="https://help.inboxmcp.io/en/changelog/microsoft-365-provider#not-yet-included" class="hash-link" aria-label="Direct link to Not yet included" title="Direct link to Not yet included" translate="no">​</a></h2>
<ul>
<li class="">Self-service tenant admin consent for Microsoft 365 organisations</li>
<li class="">Shared mailboxes with their own sign-in (without a delegate account)</li>
</ul>
<p>Both are scheduled on the <a class="" href="https://help.inboxmcp.io/en/roadmap">roadmap</a>. More under
<a class="" href="https://help.inboxmcp.io/en/docs/mailboxes/microsoft-365">Connect Microsoft 365</a>.</p>]]></content>
        <author>
            <name>inboxmcp</name>
            <uri>https://inboxmcp.io</uri>
        </author>
        <category label="feature" term="feature"/>
        <category label="mailboxes" term="mailboxes"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Public Beta (v0.2)]]></title>
        <id>https://help.inboxmcp.io/en/changelog/public-beta-v0.2</id>
        <link href="https://help.inboxmcp.io/en/changelog/public-beta-v0.2"/>
        <updated>2026-05-22T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[inboxmcp is in public beta as of v0.2.0. The release marks the move into production:]]></summary>
        <content type="html"><![CDATA[<p>inboxmcp is in <strong>public beta</strong> as of v0.2.0. The release marks the move into production:
real customer mailboxes, Stripe billing, audit log, GDPR-compliant hosting on our own
infrastructure in German data centres.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="feature-set">Feature set<a href="https://help.inboxmcp.io/en/changelog/public-beta-v0.2#feature-set" class="hash-link" aria-label="Direct link to Feature set" title="Direct link to Feature set" translate="no">​</a></h2>
<ul>
<li class=""><strong>MCP endpoint</strong> at <code>https://mcp.inboxmcp.io/mcp</code> with OAuth 2.1 and Dynamic Client
Registration (RFC 7591). Compatible with Claude Web and Desktop, plus any
MCP-conformant client.</li>
<li class=""><strong>Mailbox connection</strong> for IMAP/SMTP (every RFC-3501 mail server — mailbox.org, IONOS,
STRATO, Posteo and others) and <strong>Microsoft 365</strong> via OAuth.</li>
<li class=""><strong>Read tools</strong>: <code>list_mailboxes</code>, <code>list_folders</code>, <code>search_mails</code>, <code>read_mail</code>,
<code>read_mail_chunk</code>, <code>get_attachment</code> (attachment URLs are HMAC-signed and short-lived).</li>
<li class=""><strong>Write tools</strong> (Premium / Business): <code>draft_mail</code>, <code>edit_draft</code>, <code>create_folder</code>,
<code>move_mails</code>. More coming.</li>
<li class=""><strong>Stripe billing</strong>: Free (1 mailbox, read-only), Premium (€2.99/mailbox/month),
Business (€4.99/mailbox/month) with DPA, audit-log access and tax-compliant invoice.</li>
<li class=""><strong>Audit log</strong>: every tool call is recorded with timestamp, tool, mailbox, client and
result.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="security">Security<a href="https://help.inboxmcp.io/en/changelog/public-beta-v0.2#security" class="hash-link" aria-label="Direct link to Security" title="Direct link to Security" translate="no">​</a></h2>
<p>Credentials — IMAP/SMTP passwords and OAuth refresh tokens — are encrypted with an
asymmetric envelope scheme before they're stored. Recovery from outside is technically
impossible. Mail content is never persisted. More under
<a class="" href="https://help.inboxmcp.io/en/docs/security">Security &amp; privacy</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="not-yet-included">Not yet included<a href="https://help.inboxmcp.io/en/changelog/public-beta-v0.2#not-yet-included" class="hash-link" aria-label="Direct link to Not yet included" title="Direct link to Not yet included" translate="no">​</a></h2>
<ul>
<li class="">Write tools <code>send_mail</code>, <code>flag_mail</code>, <code>delete_mail</code></li>
<li class="">Audit log export (CSV / JSON)</li>
</ul>
<p>Status on the <a class="" href="https://help.inboxmcp.io/en/roadmap">roadmap</a>. Feedback at
<a href="mailto:support@inboxmcp.io" target="_blank" rel="noopener noreferrer" class="">support@inboxmcp.io</a>.</p>]]></content>
        <author>
            <name>inboxmcp</name>
            <uri>https://inboxmcp.io</uri>
        </author>
        <category label="release" term="release"/>
        <category label="beta" term="beta"/>
    </entry>
</feed>