docs: Update internals/ to not mention quirks of go-imap v1

This commit is contained in:
fox.cpp
2022-06-18 18:47:08 +03:00
parent 37bfe3bbd6
commit dab36e41a7
2 changed files with 2 additions and 11 deletions

View File

@@ -14,17 +14,10 @@ interoperability.
### `sql` ### `sql`
- `\Recent` flag is not implemented and it always set. - `\Recent` flag is not reset in all cases.
This _does not_ break [RFC 3501]. Clients relying on it will work (much) less This _does not_ break [RFC 3501]. Clients relying on it will work (much) less
efficiently. efficiently.
- Sequence numbers don't stay consistent between SELECT/CHECK commands.
This _does not_ break [RFC 3501] which is unclear about synchronization
issues, however it deviates from behavior implemented by most servers. This
can lead to operations applied to the wrong messages if sequence numbers are
used by multiple clients connected at the same time.
[RFC 2821]: https://tools.ietf.org/html/rfc2821 [RFC 2821]: https://tools.ietf.org/html/rfc2821
[RFC 3501]: https://tools.ietf.org/html/rfc3501 [RFC 3501]: https://tools.ietf.org/html/rfc3501

View File

@@ -20,9 +20,7 @@ maddy along with any known deviations.
## IMAP ## IMAP
- [RFC 3501] - Internet Message Access Protocol - Version 4rev1 - [RFC 3501] - Internet Message Access Protocol - Version 4rev1
* **Broken**: Unilateral updates are sent immedately, sequence numbers are not frozen. * **Partial**: `\Recent` flag is not reset sometimes.
[GH 188]
* **Partial**: `\Recent` flag is not implemented.
- [RFC 2152] - UTF-7 - [RFC 2152] - UTF-7
### Extensions ### Extensions