[imp] Horde 4.0.14 / IMP 5.0.19 / Trouble with dynamic interface

[Vilius Šumskas]

> Hello,
> 
> Thank you Francis for your answer, I already did this but nothing changed.
> 
> I increased my memory limit (512M, even if the max memory used by horde
> is 20M according to its own logs...), I have recompiled php on Unbuntu
> to remove the suhosin patch, I tried on a another server with Zend
> Server without suhosin, and I always have the same trouble :
> my Inbox is partially fetched then
> "Error when communicationg with the server" and this javascript error :
> TypeError: this.data.get(o.key) is undefined :
> this.data.get(o.key).VP_rownum = o.value;
> There's no messages in the logs (no messages in the logs of horde and no
> messages in the logs of apache)

As it is a JS error, have you tried with different browsers? Which IMAP/POP3 mail server you are using? What mail server log says?
 
> Could someone tell me where I can look into the code to find where it
> comes from  (I'm a 10 years old PHP/Javascript developper) or if I
> missed something obvious...
> 
> Florent
> 
> 
> francis picabia a écrit :
> > On Mon, Mar 19, 2012 at 3:41 PM, francis picabia <fpicabia at gmail.com>
> wrote:
> >
> >> On Thu, Mar 15, 2012 at 7:47 PM, Simon Brereton
> >> <simon.brereton at buongiorno.com> wrote:
> >>
> >>> On Mar 15, 2012 5:55 PM, "Florent TETART" <ftetart at sigb.net> wrote:
> >>>
> >>>> Hi all,
> >>>>
> >>>> First, thank you all for this nice Groupware, wich is exactly what I need
> >>>>
> >>> for my company.
> >>>
> >>>> I installed Horde 4.0.14 / IMP 5.0.19 (I followed the quick setup guide)
> >>>>
> >>> on a Ubuntu 11.10 with all the defaults packages (apache, mysql, etc.)
> from
> >>> the distro.
> >>>
> >>>> Everything works fine except for IMP in dynamic mode. I often get the
> >>>>
> >>> following js error that makes the inbox stay empty :
> >>>
> >>>> TypeError: this.data.get(o.key) is undefined
> >>>> this.data.get(o.key).VP_rownum = o.value; (log in the console of
> firebug
> >>>>
> >>> in Firefox)
> >>>
> >>>> It happens what ever the size of the mailbox (I have the same error
> from
> >>>>
> >>> a mailbox with 50 messages as well as a mailbox with 6500 messages).
> >>>
> >>>> I changed the parameters of the php.ini file to have a long execution
> >>>>
> >>> time (300s), a big memory limit (128Mo), I cleaned the browsers cache, I
> >>> changed the timeout parameter for the Imap backend to 100, I
> >>> disabled/enabled the cache, with the file driver or Sql driver, there's no
> >>> error message in horde logs, no error message in apache/php logs, the
> >>> responses to the ajax queries viewPort and listMailboxes seems to be
> good
> >>> (firebug can interpret the returned json structure ), I searched for two
> >>> days in Google, mailings lists and I can't understand why...
> >>>
> >>>> The only clues I found :
> >>>> -There's the suhosin patch on my apache2 php module but as I read, it
> >>>>
> >>> should works
> >>>
> >>>> -It works for a few users  (even with big mailboxes) in dynamic mode
> >>>> -It always works in classic mode
> >>>> -I found a mail :
> >>>>
> >>> http://lists.horde.org/archives/imp/Week-of-Mon-
> 20111128/052961.html with
> >>> the same problem where the IMP version mentionned is 5.0.15. Michael
> M
> >>> Slusarz answered it was fixed in IMP 5.0.14
> >>>
> >>>> So I don't know what to do more to find a solution if any. I may use the
> >>>>
> >>> classic interface but the dynamic one is so nice...
> >>>
> >>> Google should also have pointed you to numerous threads advising you
> to
> >>> delete/disable suhosin.  It comes up at least once a month.
> >>>
> >>> Google would also also have pointed you to a thread of mine advising a
> >>> memory limit for php of 256mb.
> >>>
> >> Suhosin exists for a reason.  This answer and the google answer is ill-
> informed.
> >> Debian comes with suhosin compiled in.  It can work, once some limits
> >> are tweaked.
> >>
> >> Here is what I last used on our Redhat Horde server:
> >>
> >> /etc/php.d/suhosin.ini:
> >>
> >> extension=suhosin.so
> >>
> >> suhosin.memory_limit = 201326592
> >> suhosin.post.max_vars = 400
> >> suhosin.request.max_vars = 400
> >> suhosin.session.encrypt = 0
> >>
> >> To this you can safely add:
> >>
> >> suhosin.simulation = on
> >>
> >> to run your set up without actually blocking anything
> >> but only to see warnings in /var/log/messages
> >>
> >
> > That was from an older Horde.  In version 5 of IMP
> > it appears this would be useful:
> >
> > extension=suhosin.so
> >
> > suhosin.simulation = on
> >
> > suhosin.memory_limit = 201326592
> > suhosin.post.max_vars = 400
> > suhosin.request.max_vars = 400
> > suhosin.session.encrypt = 0
> >
> > suhosin.cookie.disallow_nul = Off
> > suhosin.get.disallow_nul = Off
> > suhosin.post.disallow_nul = Off
> > suhosin.request.disallow_nul = Off
> >
> > Once you see there are no entries for false positives, then
> > try with simulation off.
> >
> --
> imp mailing list
> Frequently Asked Questions: http://wiki.horde.org/FAQ
> To unsubscribe, mail: imp-unsubscribe at lists.horde.org