Tickets :: [#2828] Searching and Virtual Folders do not return results

6.0.0-beta1

12/31/25

Summary	Searching and Virtual Folders do not return results
Queue	IMP
Queue Version	HEAD
Type	Bug
State	Not A Bug
Priority	1. Low
Owners
Requester	mrubinsk (at) horde (dot) org
Created	10/22/2005 (7375 days ago)
Due
Updated	10/26/2005 (7371 days ago)
Assigned	10/22/2005 (7375 days ago)
Resolved	10/26/2005 (7371 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

10/26/2005 03:34:29 PM	Jan Schneider	Comment #10	Reply to this comment
an issue with our code, but this one provider's server. One last question, if the userbase for this particual install is okay with it, would it be an option to force a supported charset on the entire interface? Would this be done through config/nls.php? No, this is not possible at the moment. You need to hack the code.

10/26/2005 03:27:08 PM	Michael Rubinsky	Comment #9 State ⇒ Not A Bug	Reply to this comment
No, because we still don't know what the user entered in his search. You can't (obviously) convert a Japanese search to ascii for example, so the only option would be to force the charset supported by the imap server to the search interface. But that would really be a hack. Yea, I pretty much thought as much. I'll resolve this since it's not an issue with our code, but this one provider's server. One last question, if the userbase for this particual install is okay with it, would it be an option to force a supported charset on the entire interface? Would this be done through config/nls.php? Thanks for the help.

10/26/2005 02:37:52 PM	Jan Schneider	Comment #8	Reply to this comment
At the risk of sounding stupid, is this something that could be put into a pref? Something like 'Force charset?' for non-compliant IMAP servers? I'll give another go at convincing this host to provide No, because we still don't know what the user entered in his search. You can't (obviously) convert a Japanese search to ascii for example, so the only option would be to force the charset supported by the imap server to the search interface. But that would really be a hack.

10/26/2005 02:12:20 PM	Michael Rubinsky	Comment #7	Reply to this comment
Of course, but how would you decide which charset to use? We use the charset from the interface, because this is how the user entered his search. He could well be searching for Japanese text in a Russian interface displayed in the UTF-8 charset. I'm afraid I don't know enough about charset usage to give an intelligent answer here. I'm not even sure I understand how a user could send a search in Japanese text while in a Russian interface. Now I know the next area for some self-study. At the risk of sounding stupid, is this something that could be put into a pref? Something like 'Force charset?' for non-compliant IMAP servers? I'll give another go at convincing this host to provide UTF-8 support as the RFCs require. Nothing but problems with this provider...

10/26/2005 08:07:34 AM	Jan Schneider	Comment #6	Reply to this comment
under my control - is there a way to have only IMP use another charset, like ISO-8859-1? Of course, but how would you decide which charset to use? We use the charset from the interface, because this is how the user entered his search. He could well be searching for Japanese text in a Russian interface displayed in the UTF-8 charset.

10/26/2005 05:13:44 AM	mrubinsk (at) horde (dot) org	Comment #5	Reply to this comment
An update on this. When I speak IMAP to the server, I get Sorry - I got this from sniffing the traffic not speaking directly. The UTF-8 is coming from IMP.

10/26/2005 05:07:45 AM	mrubinsk (at) horde (dot) org	Comment #4	Reply to this comment
Have you tried testing with another IMAP client, or speaking IMAP directly, to see if your new server even supports searching? An update on this. When I speak IMAP to the server, I get 0000005 NO UTF-8 charset is not supported I thought that all IMAP servers were required to support this charset? This is Courier IMAP - which it turns out still allows a compile option to not include this charset...as this server is not under my control - is there a way to have only IMP use another charset, like ISO-8859-1? I'm not too familiar with the charset stuff...

10/22/2005 12:33:23 PM	Michael Rubinsky	Comment #3	Reply to this comment
Have you tried testing with another IMAP client, or speaking IMAP directly, to see if your new server even supports searching? Yep. It works with 2 other IMAP clients I tried as well as with an older Framework_3 checkout (before it was merged with the x.1 branch).

10/22/2005 06:19:35 AM	Chuck Hagenbuch	Comment #2 State ⇒ Feedback	Reply to this comment
Have you tried testing with another IMAP client, or speaking IMAP directly, to see if your new server even supports searching?

10/22/2005 05:22:23 AM	Michael Rubinsky	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Searching and Virtual Folders do not return results Queue ⇒ IMP State ⇒ Unconfirmed	Reply to this comment
I moved from a UW-IMAP server to a provider that uses Courier IMAP. All searches now fail to return any results and the Virtual INBOX does not contain any mail. Latest HEAD, updated configuration files. I even nuked all my vfolder related prefs for good measure. When I revert back to the UW-IMAP server, everything works as expected. Is there some config I am missing, or is there a problem with Courier?