serv/mox
1
0
Fork 0
mirror of https://github.com/mjl-/mox.git synced 2024-12-26 08:23:48 +03:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
mox/website/protocols/summary.md
Mechiel Lukkien 0bc3072944
new website for www.xmox.nl 
most content is in markdown files in website/, some is taken out of the repo
README and rfc/index.txt. a Go file generates html. static files are kept in a
separate repo due to size.
2024-01-10 17:22:03 +01:00

4.4 KiB
Raw Permalink Blame History

Protocols

Summary

First a high-level description of protocols and implementation status. Each topic links to the second table with more detailed implementation status per RFC.

TopicImplementedDescription
Internet Message Format Yes The format of email messages
SMTP Yes Delivering email
SPF Yes Message authentication based on sending IP
DKIM Yes Message authentication based on message header
DMARC Yes Reject/accept policy for incoming messages that pass/fail DKIM and/or SPF message authentication
ARC Roadmap Signed message authentication results from forwarding server
DANE Yes Verification of TLS certificates through DNSSEC-protected DNS records
MTA-STS Yes PKIX-based protection of TLS certificates and MX records
TLS Reporting Yes Reporting about TLS interoperability issues
ARF Roadmap Abuse reporting format
IMAP Yes Email access protocol
Sieve Roadmap Scripts to run on incoming messages
JMAP Roadmap HTTP/JSON-based email access protocol
CalDAV/iCal Roadmap Calendaring
CardDAV/vCard Roadmap Contacts
SASL Yes Authentication mechanisms
Internationalization Yes Internationalization of domain names.
TLS Yes TLS, for encrypted and authenticated communication.
ACME Yes Automatically manage PKIX TLS certificates
CAA Yes CAA DNS reords specify which certificate authorities (CAs) are allowed to sign certificates for a domain.
HTTP Yes HTTP for webservers. Required for automatic account configuration and MTA-STS. Also relevant for the built-in webserver.

RFCs

The mox source code is quite heavily annotated with references to the RFCs. This makes the implementation more maintainable, and makes it easier for new developers to make changes. See cross-referenced code and RFCs to navigate RFCs and source code side by side.

Implementation status per RFC, grouped by topic.

Statuses