How to efficiently provide email access to our users?
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Quentin cc775799a6
Add EAS
7 months ago
README.md Add EAS 7 months ago

README.md

How to efficiently provide email access to our users?

JMAP

specs:

  • rfc8620 The JSON Meta Application Protocol (JMAP)
  • rfc8621 The JSON Meta Application Protocol (JMAP) for Mail
  • specs JMAP: The Specs

clients:

IMAP

specs:

  • rfc3501 INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
  • rfc4466 Collected Extensions to IMAP4 ABNF
  • rfc4469 Internet Message Access Protocol (IMAP) CATENATE Extension
  • rfc4551 IMAP Extension for Conditional STORE Operation or Quick Flag Changes Resynchronization
  • rfc5032 WITHIN Search Extension to the IMAP Protocol
  • rfc5182 IMAP Extension for Referencing the Last SEARCH Result
  • rfc5738 IMAP Support for UTF-8
  • rfc6186 Use of SRV Records for Locating Email Submission/Access Services
    • Can be used by the alps webmail
  • rfc6858 Simplified POP and IMAP Downgrading for Internationalized Email
  • rfc7817 Updated Transport Layer Security (TLS) Server Identity Check Procedure for Email-Related Protocols
  • rfc8314 Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access
  • rfc8437 IMAP UNAUTHENTICATE Extension for Connection Reuse
  • rfc8474 IMAP Extension for Object Identifiers

Exchange ActiveSync (EAS)

[MS-ASHTTP]: Exchange ActiveSync: HTTP Protocol

Existing projetcs that could help us

  • maddy full-featured easy-to-setup email server. IMAP storage is "beta".
    • go-emersion a client and server IMAP implementation. The client implem is used by alps.