Tickets :: [#7662] IMAP and "Destination" rules

11/11/2008 04:35:02 PM	Chuck Hagenbuch	Comment #4 State ⇒ Duplicate	Reply to this comment
Let's continue this in ~~#7343~~. We're going to need to get deeper than blank page at some point though.

11/11/2008 02:55:22 PM	jouva (at) moufette (dot) com	Comment #3	Reply to this comment
They are not handled properly. Infact after even FURTHER investigation, I don't think any "extended search" filter works under IMAP. I've added a "Bcc" filter to Ingo, which according to the code is an "extended search" because it is not a common field to search for (Such as To, From, Cc or Subject). I have Ingo setup to filter upon logging in, along with authentication against IMP and going to the main Horde portal view upon logging in. When I have this filter installed, I get a blank page from redirect.php upon logging in, since the code chokes on the extended search call without an error anywhere. So I then have to manually modify the URL to see Horde. At which point, if I go into Ingo and view the rule I made, the rule won't fully display.

11/11/2008 07:22:44 AM	Chuck Hagenbuch	Comment #2 State ⇒ Feedback	Reply to this comment
Can you be more specific than "an issue"?

11/09/2008 08:04:04 PM	jouva (at) moufette (dot) com	Comment #1 Priority ⇒ 2. Medium Type ⇒ Bug Summary ⇒ IMAP and "Destination" rules Queue ⇒ Ingo Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
After much debugging with ~~ticket #7603~~ and finding out about ticket ~~#7117~~ and ~~ticket #7611~~ I've determined that there's an issue with Ingo and using the "Destination" rules (and probably inheriently, Source and Participant or ANY comma separated list of headers). It seems to affect both the filtering process in itself AND the interface of Ingo when attempting to edit said rules.