EmailEngine Drops Embeddings and Its Document Store
EmailEngine 2.82.0 removes embeddings generation and the Document Store, and now checks incoming mail in code before its AI features read it.

EmailEngine 2.82.0 removes embeddings generation and the Document Store, according to the Oct. 1 release notes from Postal Systems, the Estonian company behind the self-hosted mailbox API. The same release adds a code-level check on incoming mail before the AI features see it.
Embeddings and the Document Store are gone
The release notes list “remove embeddings generation” and “remove the Document Store” as separate changes. An instance that relied on either feature loses it on upgrade. Read the notes before pulling the new version.
The AI features change shape
The notes say EmailEngine will now “check incoming mail in code before the AI reads it.” The model choice also changes: users pick from a list that says what each model is for, and the model picker’s search now matches term by term and ranks its answers.
The notes say summaries now arrive as the model returned them, with their usage counted. The release also drops the trusted authentication servers setting from the AI page.
Fixes touch IMAP and Outlook
Postal Systems said the release reconnects a primary IMAP connection whose view of the main mailbox stopped moving. It also counts announced literals against the IMAP proxy cap at continuation time. Draft replies on Microsoft Graph accounts now stay threaded. The project updated ImapFlow to 2.2.1.
EmailEngine now uses only FIPS-approved primitives. An instance can now run on a host whose OpenSSL is in FIPS mode.
The previous release, 2.81.2 on Sept. 27, changed bounce handling. According to its notes, bounce detection is now evaluated when a message is fetched instead of stored. Message responses report isBounce and relatedMessageId.
Key takeaways
- EmailEngine 2.82.0, released Oct. 1, removes embeddings generation and the Document Store.
- Incoming mail is now checked in code before the AI features read it.
- Summaries are delivered as the model returned them, with usage counted.
- The release adds FIPS-mode support and IMAP and Outlook fixes.
The take
We think a removal is the most useful kind of release note. It shows where a project has decided not to go. EmailEngine’s job is to give an app reliable access to mailboxes. Embeddings and a document store pull it toward being a search product, which is a different job.
The pre-read check matters for a plain reason. Mail comes from strangers. A model that reads it can be handed instructions by the sender. A check written in ordinary code does not depend on the model’s judgment. It fails in predictable ways.
Teams that run EmailEngine should search their code for any use of embeddings or the Document Store before upgrading. They should also test the new pre-read check against a few hostile messages of their own.