mailroom-core
Mailroom's mail layer: accounts and their sealed secrets, IMAP and SMTP, the send gate,
rendering and audit. It is shared by the mailroom-mcp server and the Mailroom web app, and
developed in the mailroom-mcp repository
(packages/core).
Its Postgres tables live in schema core, with their own Alembic history:
mailroom_core.store.migrate(engine) brings it up to date in the host's database.
Its API is synchronous: mailroom_core.mail.MailConnections holds the IMAP connections, and an
async host calls it from a worker thread. Over them, list_messages, search_messages, thread_page,
read_message, read_attachment and html_view read mail and return typed results.
mailroom_core.testing is a pytest plugin, loaded wherever the package is installed: a
no-network guard, the IMAP, SMTP and test-database fixtures, and helpers to seed the IMAP test
server (mailroom_core.testing.imap). Install the testing extra for it.
1 maintainer
Metadata
1 maintainer
Release files for mailroom-core 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mailroom_core-0.1.1.tar.gz | 137.2 kB | With provenance | Details for mailroom_core-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mailroom_core-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for mailroom_core-0.1.1-py3-none-any.whl |
Total release size: 249.8 kB
Release files / mailroom_core-0.1.1.tar.gz
| Download URL | mailroom_core-0.1.1.tar.gz |
|---|---|
| Size | 137.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b9c740954aaa3a78d05d75e9109e9db40827266977e0235ebfdf665015e47374
|
|
BLAKE2b-256 checksum How to use checksums |
5a7e7caedfba7263e3b3204ec3f2775643a56e668893d4861a1ddf7b01a2e355
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logRelease files / mailroom_core-0.1.1-py3-none-any.whl
| Download URL | mailroom_core-0.1.1-py3-none-any.whl |
|---|---|
| Size | 112.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7785595df6627a79c926c2d53b695b00d16152008642ab2dd7d1b45b067bef3c
|
|
BLAKE2b-256 checksum How to use checksums |
dc32452fca0fa48417577f9ac729e6e6576c7f6381d2c9c1a7a54f37ff00f2f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logSecurity for mailroom-core 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for mailroom_core-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
