[ingo] Ingo seems to breaks Imp

Allan Michie allan at russellway.co.uk
Wed Mar 1 06:28:18 PST 2006


This problem only manifests itself on a development system using the 
latest releases of Horde and Imp.

Using Horde 3.1-RC3 and  (imp) H3 (4.1-RC3), Ingo H3 (1.0.2) indicates 
that filters have been  applied, but the messages are not actually 
deleted from the inbox.

With Horde (3.0.9) and Imp H3 (4.0.4) Ingo (1.0.2) works perfectly 
against the same backends (as does everyting else).

Lates version of Ingo (1.1.0)-RC2 on horde 3.1-RC3 and  imp 4.1-RC3 
produces empty blank white screen when Imp is fired up. There is no 
html source. There are three log entries (first repeated).

Mar 01 06:18:44 HORDE [debug] [imp] SQL Query by Prefs_sql::retrieve(): 
SELECT pref_scope, pref_name, pref_value FROM horde_prefs WHERE 
pref_uid = ? AND (pref_scope = ? OR pref_scope = 'horde') ORDER BY 
pref_scope [on line 132 of 

Mar 01 06:18:44 HORDE [notice] [imp] Login success for allan 
[] to {svr1.net.19x.co.uk:143} [on line 152 of 

Backends are IMAP-2204g and PostgresSQL which are both working fine 
supporting a production system.

Any ideas?

Thanks in anticipation,


More information about the ingo mailing list