RFC5530 IMAP Response Codes #47

New Issue

Open

opened 2023-12-29 18:10:43 +00:00 by quentin · 1 comment

quentin commented

2023-12-29 18:10:43 +00:00

Owner

Section 7.1 of [RFC3501] defines a number of response codes that can
help tell an IMAP client why a command failed. However, experience
has shown that more codes are useful. For example, it is useful for
a client to know that an authentication attempt failed because of a
server problem as opposed to a password problem.

Currently, many IMAP servers use English-language, human-readable
text to describe these errors, and a few IMAP clients attempt to
translate this text into the user's language.

This document names a variety of errors as response codes. It is
based on errors that have been checked and reported on in some IMAP
server implementations, and on the needs of some IMAP clients.

This document doesn't require any servers to test for these errors or
any clients to test for these names. It only names errors for better
reporting and handling.

imap_codec support: NOT REQUIRED (YES)

https://datatracker.ietf.org/doc/html/rfc5530

> Section 7.1 of [RFC3501] defines a number of response codes that can help tell an IMAP client why a command failed. However, experience has shown that more codes are useful. For example, it is useful for a client to know that an authentication attempt failed because of a server problem as opposed to a password problem. > Currently, many IMAP servers use English-language, human-readable text to describe these errors, and a few IMAP clients attempt to translate this text into the user's language. > This document names a variety of errors as response codes. It is based on errors that have been checked and reported on in some IMAP server implementations, and on the needs of some IMAP clients. > This document doesn't require any servers to test for these errors or any clients to test for these names. It only names errors for better reporting and handling. imap_codec support: NOT REQUIRED (YES) https://datatracker.ietf.org/doc/html/rfc5530

quentin added this to the 0.2.0 milestone 2023-12-29 18:10:43 +00:00

quentin added the

cat

feature

label 2023-12-29 18:10:43 +00:00

quentin added this to the IMAP4REV2 project 2023-12-29 18:10:43 +00:00

quentin added the

prio

high

label 2024-01-03 08:27:55 +00:00

~~quentin referenced this issue 2024-01-03 09:41:43 +00:00~~

Implement some IMAP extensions #50

quentin referenced this issue

2024-01-04 11:18:16 +00:00

Aerogramme refactoring #57

quentin commented

2024-01-20 10:58:02 +00:00

Author

Owner

Implementing this RFC in a clever/useful way is not that simple, as ideally we would want to write our code to fall as much as possible in these cases. Furthermore, it would make sense to contribute these codes to imap-codec firt. Removing from 0.2.0 target.

quentin removed this from the 0.2.0 milestone 2024-01-20 10:58:06 +00:00