Everything in a Langmail mailbox is reachable over standard protocols on mail.langmail.me. This page is the endpoint map — the same one an export tool or a competitor’s migration script would use. That’s the point.
Endpoints
| Protocol | Endpoint | Use |
|---|
| JMAP | https://mail.langmail.me — session at /.well-known/jmap | Modern JSON mail access; what the MCP server and webmail use |
| CalDAV | https://mail.langmail.me — discovery at /.well-known/caldav, collections under /dav/cal/ | Calendars and scheduling; what the calendar tools use |
| IMAP | mail.langmail.me:993 (SSL/TLS) or :143 (STARTTLS) | Any classic mail client; full archive access |
| SMTP submission | mail.langmail.me:465 (SSL/TLS) or :587 (STARTTLS) | Sending from mail clients |
| ManageSieve | mail.langmail.me:4190 | Server-side filtering rules (Sieve) |
Authentication
| Method | Works for | How to get it |
|---|
| OAuth bearer token | JMAP, CalDAV (HTTP Authorization: Bearer header) | The OAuth flow — this is what MCP clients and webmail use |
| App password | IMAP, SMTP, CalDAV | Generate in webmail under Settings → Security; see Use a mail client or Use a calendar client |
What this buys you
- Complete export, any time. An IMAP or JMAP sync of your mailbox is a complete, portable archive in standard formats — including the category keywords Langmail adds, which are plain mailbox keywords.
- Client freedom. Apple Mail, Thunderbird, Outlook, mutt, offlineimap — any standards-compliant mail client works without Langmail’s involvement.
- No proprietary surface to depend on. The MCP server itself is a thin layer over JMAP and CalDAV. If you outgrow it, the protocols underneath are yours.
Metadata that lives outside the mailbox — account settings, Morning Brief configuration — is app-level and not part of the protocol surface.
