Skip to main content

MailCue Python SDK

Official Python client for MailCue — the open-source email testing and production server (Postfix + Dovecot + FastAPI + React) packaged as one Docker container.

The SDK is the same in dev and prod: point it at http://localhost:8088 while you build, then swap base_url to your production MailCue deployment when you ship.

Install

pip install mailcue

Requires Python 3.9+.

Quick start: send an email

from mailcue import Mailcue

client = Mailcue(api_key="mc_xxx")  # base_url defaults to http://localhost:8088

result = client.emails.send(
    from_="hello@example.com",
    from_name="Acme Support",
    to=["user@example.com"],
    subject="Welcome",
    html="<h1>Hi there</h1>",
)
print(result.message_id)

from_name is the display name recipients see. Leave it out and the server falls back to the display name set on the mailbox; if that is unset too, the message goes out as a bare address and mail clients show hello@example.com instead of a name.

Need async? Use AsyncMailcue — same surface, all methods become coroutines:

import asyncio
from mailcue import AsyncMailcue


async def main() -> None:
    async with AsyncMailcue(api_key="mc_xxx") as client:
        await client.emails.send(
            from_="hello@example.com",
            to=["user@example.com"],
            subject="Welcome",
            html="<h1>Hi there</h1>",
        )


asyncio.run(main())

Listing an inbox

inbox = client.emails.list(mailbox="user@example.com", page_size=20)
for email in inbox.emails:
    print(email.uid, email.subject, email.from_address)

detail = client.emails.get(inbox.emails[0].uid, mailbox="user@example.com")
print(detail.text_body)

Waiting for an email (CI)

wait_for polls a mailbox until matching messages arrive, or raises mailcue.TimeoutError after timeout seconds. Filters (subject, from_address, to_address) are case-insensitive substrings on top of the server-side search.

found = client.emails.wait_for(
    mailbox="user@test.com",
    subject="Welcome",
    timeout=10,
)
assert len(found) == 1

Email validation and catch-all risk

result = client.emails.validate("person@example.com")
print(result.provider.name, result.mailbox.selective_recipient_validation)
if result.catch_all_risk:
    print(result.catch_all_risk.score, result.catch_all_risk.recommended_action)
    for item in result.catch_all_risk.contributions:
        print(item.label, item.delta, item.detail)

A catch-all domain accepts every recipient at RCPT time, so no probe can prove that a mailbox exists. catch_all_risk.score is therefore a hard-bounce probability rather than a verdict: it starts from the receiving provider's rate, is refined by outcomes seen at that provider and domain, and is then adjusted for the local part and passive domain signals.

Validate a list together rather than one address at a time. Addresses sharing a domain reveal that domain's naming convention and any generated name variants, and target_bounce_rate returns the largest subset whose blended expected bounce rate stays under the ceiling receivers actually judge you on.

batch = client.emails.validate_batch(addresses, target_bounce_rate=0.015)
print(batch.summary.catch_all, batch.selection.projected_bounce_rate)
send_to = batch.selection.included

Feed outcomes back so the estimates improve. A raw bounce can be handed over whole instead of being summarised by hand.

client.emails.record_validation_feedback(
    "person@example.com", "hard_bounce", smtp_code=550, enhanced_status="5.1.1"
)
client.emails.ingest_bounce(raw_dsn_message)

# Check that the published probabilities held up.
report = client.emails.validation_calibration(days=90)
print(report.brier_score, report.observed_rate)

Staged sending

A message cannot be recalled once it leaves the MTA, so the only way to bound exposure on a catch-all domain is to not commit the whole batch at once. A staged send delivers a small sample first, watches the bounce window, and releases the rest only if the sample survived.

canary = client.emails.create_send_canary(
    recipients=addresses,
    from_address="hello@example.com",
    subject="Quarterly update",
    body="...",
    sample_size=2,
    hold_minutes=15,
)
state = client.emails.get_send_canary(canary.id)
print(state.status, state.decision_reason)

Attachments

attachments accepts raw bytes, str, or a pathlib.Path. The SDK base64-encodes the content for you.

from pathlib import Path

client.emails.send(
    from_="hello@example.com",
    to=["user@example.com"],
    subject="Invoice",
    html="<p>See attached.</p>",
    attachments=[
        {
            "filename": "invoice.pdf",
            "content_type": "application/pdf",
            "content": Path("./invoice.pdf"),
        }
    ],
)

Real-time events (SSE)

for event in client.events.stream():
    print(event.event_type, event.data)

The async version:

async with AsyncMailcue(api_key="mc_xxx") as client:
    async for event in client.events.stream():
        print(event.event_type, event.data)

The SSE client auto-reconnects with exponential backoff if the connection drops.

Error handling

from mailcue import (
    Mailcue,
    AuthenticationError,
    NotFoundError,
    RateLimitError,
    ValidationError,
)

client = Mailcue(api_key="mc_xxx")

try:
    client.emails.get("not-a-real-uid", mailbox="user@example.com")
except NotFoundError as exc:
    print("missing:", exc)
except RateLimitError as exc:
    print(f"slow down; retry after {exc.retry_after}s")
except AuthenticationError:
    print("bad API key")
except ValidationError as exc:
    print("server rejected the request:", exc.detail)

Configuration

client = Mailcue(
    api_key="mc_xxx",  # or bearer_token="eyJ..."
    base_url="https://mail.example.com",  # default: http://localhost:8088
    timeout=30.0,  # seconds
    max_retries=3,  # 502/503/504 + network errors
    verify=True,  # set False for self-signed dev TLS
)

You can also inject your own httpx.Client / httpx.AsyncClient via http_client= for advanced cases (custom transports, proxies, mTLS).

Resources

Resource Methods
client.emails send, list, get, get_raw, get_attachment, delete, inject, bulk_inject, validate, validate_batch, record_validation_feedback, ingest_bounce, validation_calibration, suppressed_domains, create_send_canary, list_send_canaries, get_send_canary, decide_send_canary, cancel_send_canary
client.mailboxes list, create, delete, stats, purge, list_emails
client.domains list, create, get, verify_dns, delete
client.aliases list, create, get, update, delete
client.gpg list, generate, get, export_public, import_key, publish, delete
client.api_keys list, create, delete
client.system health, get_certificate, download_certificate, settings, tls_status
client.events stream() (SSE iterator)

License

MIT — see LICENSE.

Project home: https://github.com/Olib-AI/mailcue

Metadata

Release files for mailcue 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mailcue 0.2.0
File Size Uploaded Provenance Actions
mailcue-0.2.0.tar.gz 25.4 kB With provenance Details for mailcue-0.2.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for mailcue 0.2.0
File Interpreter ABI Platform Actions
mailcue-0.2.0-py3-none-any.whl Python 3 none any Details for mailcue-0.2.0-py3-none-any.whl

Total release size: 57.5 kB

Release files / mailcue-0.2.0.tar.gz

Download URL mailcue-0.2.0.tar.gz
Size 25.4 kB
Tags Source
SHA-256 checksum
How to use checksums
240223aaeacb5902f76d8db0dbb015349e2abb38be845288dc7870b08b93484d
BLAKE2b-256 checksum
How to use checksums
f95a2791a2aecadfa32293de828d560aa07c684b4af4c22b46f011b3072698d1
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 Aug 20, 2026.

Transparency log

Release files / mailcue-0.2.0-py3-none-any.whl

Download URL mailcue-0.2.0-py3-none-any.whl
Size 32.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ad53ed4005c587778618ccf2178603424931dd8e2c96012bb8fcb8d677dfc9c9
BLAKE2b-256 checksum
How to use checksums
f231847a737e934cea34cce1126a906c1d43787f1aea8042d2bba85c77057232
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 Aug 20, 2026.

Transparency log

Security for mailcue 0.2.0

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.

Select from 2 files

Attestation for mailcue-0.2.0.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 Aug 20, 2026.

Transparency log

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page