How modern e-mail really works and the pieces we build on
Internet Engineering Task Force – the community that writes the open specifications powering e-mail, HTTP, TLS, etc. All core mail specs are “RFCs” (Request for Comments) published by the IETF.
A numbered document that defines a protocol. Example: RFC 5322 specifies e-mail headers. Every server and client that follows the same RFC can inter-operate – that’s why you can fetch Gmail via Apple Mail.
Layer | Acronym | Example software | What it does |
---|---|---|---|
Mail Transfer Agent | MTA | Postfix, Exim | Routes SMTP traffic between domains. |
Mail Delivery Agent | MDA | Dovecot, Courier | Saves incoming mail to the user’s mailbox. |
Mail User Agent | MUA | Outlook, Thunderbird | that people click. |
Relay | - | (open-core) | Sits between MUA and IMAP, giving dev-friendly JSON + webhooks. |
Relay treats every provider the same as long as it offers IMAP/SMTP. Your code talks to a single /messages endpoint.
Both provide programmable access to email-related operations.
Category | Examples | Focus |
---|---|---|
Delivery APIs | Resend, SendGrid, SES | High-volume outbound (newsletters, receipts). |
Interaction APIs | Relay | Read, search, tag, reply, build full apps. |
Use both together: Resend for blasts, Relay for smart follow-ups.
Term | Short definition |
---|---|
Email account | IMAP/SMTP credential set you connect |
Message | A single e-mail, defined by its Message-ID or IMAP UID. |
Thread | All messages sharing References/In-Reply-To headers |
Label | User-defined tag saved server-side; survives new messages. |
Head back to Quick-start. We can’t wait to see what you’ll build!
Happy hacking — and welcome to programmable e-mail.