On 2/24/19, 15:56, Michael J Rubinsky wrote:
Yes. RFC 6855 [3], and further clarified in Errata 4029:
Once an IMAP client has enabled UTF-8 support with the "ENABLE
UTF8=ACCEPT" command, it MUST NOT issue a "SEARCH" command that
contains a charset specification. If an IMAP server rec
Quoting James Noyes :
On 2/24/19, 08:57, Michael J Rubinsky wrote:
The charset is only required if UTF-8 support is not enabled on the IMAP
server, and it is *prohibited* if UTF-8 is enabled on the server.
RFC5256 seems to disagree:
"The SORT command is a variant of SEARCH with sorting seman
On 2/24/19, 08:57, Michael J Rubinsky wrote:
The charset is only required if UTF-8 support is not enabled on the IMAP
server, and it is *prohibited* if UTF-8 is enabled on the server.
RFC5256 seems to disagree:
"The SORT command is a variant of SEARCH with sorting semantics for
the result
Quoting James Noyes :
I have a current up-to-date-via-pear install of horde/imp webmail,
using imp's IMAP for user authentication.
This setup was working well until recently.
Horde/imp is now reporting "IMAP error reported by server." at user login.
Capturing the IMAP conversation shows that
I have a current up-to-date-via-pear install of horde/imp webmail, using
imp's IMAP for user authentication.
This setup was working well until recently.
Horde/imp is now reporting "IMAP error reported by server." at user login.
Capturing the IMAP conversation shows that horde/imp is issuing an
