Quoting James Noyes <jnoyes-ho...@retrogeeks.com>:

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 improper IMAP "SORT" command, leaving out the mandatory charset specification, at login. This breaks imp functionality, and appears to be a reasonably recent change in behavior.

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.

What IMAP server are you using? Since you mention this recently started happening, what has been changed recently?

What is the CAPABILITY response from the IMAP log?


The IMAP command being issued by horde/imp is:
"<n> UID SORT (ARRIVAL) ALL"

when the proper structure of this command is something like:
"<n> UID SORT (ARRIVAL) UTF-8 ALL"
or
"<n> UID SORT (ARRIVAL) US-ASCII ALL"

Is this a configuration mistake on my part, or is this a bug?
Do I need to explicitly set/declare a charset somewhere in my configuration?
--
imp mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: imp-unsubscr...@lists.horde.org



--
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject

Attachment: binIn6eL_hoHV.bin
Description: PGP Public Key

Attachment: pgpVK53DbSY3v.pgp
Description: PGP Digital Signature

-- 
imp mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: imp-unsubscr...@lists.horde.org

Reply via email to