Protocols
How laim.email serves your email — JMAP, IMAP, and SMTP.
JMAP (JSON Meta Application Protocol)
JMAP is the modern, stateless, JSON-based protocol that powers the laim.email webmail interface. It replaces the complexity of IMAP with a clean HTTP-based API designed for today's applications.
- +Efficient delta sync — only fetch changes since last sync, not entire mailboxes
- +Push notifications — real-time updates without polling
- +Single HTTP connection — no persistent socket needed, works through firewalls and proxies
- +Batch operations— multiple commands in a single request
- +Standards-based— RFC 8620 (JMAP Core) and RFC 8621 (JMAP Mail)
The laim.email webmail uses JMAP by default. No configuration needed.
IMAP (Internet Message Access Protocol)
IMAP is the legacy protocol supported by every email client in existence. laim.email provides full IMAP access for users who prefer desktop or mobile clients.
| Server | mail.laim.email |
| Port | 993 (IMAPS / TLS) |
| Security | SSL/TLS (required) |
| Username | Your full email address |
| Password | Your laim.email password |
SMTP (Simple Mail Transfer Protocol)
SMTP is used for sending email from external clients. laim.email supports two secure ports.
| Server | mail.laim.email |
| Port (preferred) | 465 (SMTPS / implicit TLS) |
| Port (alternative) | 587 (STARTTLS) |
| Authentication | Required (your email address and password) |
| Delivery | Direct-to-MX (no third-party relay) |
Which Should You Use?
| Use Case | Protocol | Notes |
|---|---|---|
| Webmail | JMAP | Automatic, no configuration needed |
| Desktop clients | IMAP + SMTP | Thunderbird, Apple Mail, Outlook |
| Mobile clients | IMAP + SMTP | iOS Mail, Android clients |
| Programmatic access | JMAP via API keys | See the REST API docs |
© 2026 laim.email, All Rights Reserved