IMAP Search RFC #58

New issue

Open

opened 2024-01-04 13:28:06 +00:00 by quentin · 0 comments

quentin commented

2024-01-04 13:28:06 +00:00

Owner

RFC3501 IMAP4rev1 section 6.4.4 - Reference

RFC4731 ESEARCH - A server advertising the ESEARCH capability supports the following result options: minimal value, maximal value, all found messages, and number of found messages. These result options allow clients to get SEARCH results in more convenient forms, while also saving bandwidth required to transport the results, for example, by finding the first unseen message or returning the number of unseen or deleted messages. Also, when a single MIN or a single MAX result option is specified, servers can optimize execution of SEARCHes.

Tracked in #40.

RFC5267 CONTEXT & ESORT - This memo borrows concepts from [ACAP], such as providing a windowed view onto search or sort results, and making updates that are bandwidth and round-trip efficient. These are provided by two extensions: "ESORT" and "CONTEXT".

RFC5032 WITHIN - This document describes the WITHIN extension to IMAP SEARCH. IMAP SEARCH returns messages whose internal date is within or outside a specified interval. The mechanism described here, OLDER and YOUNGER, differs from BEFORE and SINCE in that the client specifies an interval, rather than a date. WITHIN is useful for persistent searches where either the device does not have the capacity to perform the search at regular intervals or the network is of limited bandwidth and thus there is a desire to reduce network traffic from sending repeated requests and redundant responses.

RFC6203 SEARCH=FUZZY - When humans perform searches in IMAP clients, they typically want to see the most relevant search results first. IMAP servers are able to do this in the most efficient way when they're free to internally decide how searches should match messages. This document describes a new SEARCH=FUZZY extension that provides such functionality.

RFC9051 IMAP4rev2 section 6.4.4 - Requires ESEARCH

Ref:

[RFC3501 IMAP4rev1 section 6.4.4](https://www.rfc-editor.org/rfc/rfc3501.html#section-6.4.4) - Reference [RFC4731 ESEARCH](https://datatracker.ietf.org/doc/html/rfc4731) - A server advertising the ESEARCH capability supports the following result options: minimal value, maximal value, all found messages, and number of found messages. These result options allow clients to get SEARCH results in more convenient forms, while also saving bandwidth required to transport the results, for example, by finding the first unseen message or returning the number of unseen or deleted messages. Also, when a single MIN or a single MAX result option is specified, servers can optimize execution of SEARCHes. *Tracked in #40*. [RFC5267 CONTEXT & ESORT](https://datatracker.ietf.org/doc/html/rfc5267) - This memo borrows concepts from [ACAP], such as providing a windowed view onto search or sort results, and making updates that are bandwidth and round-trip efficient. These are provided by two extensions: "ESORT" and "CONTEXT". [RFC5032 WITHIN](https://datatracker.ietf.org/doc/html/rfc5032) - This document describes the WITHIN extension to IMAP SEARCH. IMAP SEARCH returns messages whose internal date is within or outside a specified interval. The mechanism described here, OLDER and YOUNGER, differs from BEFORE and SINCE in that the client specifies an interval, rather than a date. WITHIN is useful for persistent searches where either the device does not have the capacity to perform the search at regular intervals or the network is of limited bandwidth and thus there is a desire to reduce network traffic from sending repeated requests and redundant responses. [RFC6203 SEARCH=FUZZY](https://datatracker.ietf.org/doc/html/rfc6203) - When humans perform searches in IMAP clients, they typically want to see the most relevant search results first. IMAP servers are able to do this in the most efficient way when they're free to internally decide how searches should match messages. This document describes a new SEARCH=FUZZY extension that provides such functionality. [RFC9051 IMAP4rev2 section 6.4.4](https://www.rfc-editor.org/rfc/rfc9051.html#name-search-command) - Requires ESEARCH Ref: - https://gist.github.com/nevans/8ef449da0786f9d1cc7c8324a288dd9b - https://www.imapwiki.org/ImapRFCList