[imp] Re: Can't get Ingo to do my filtering

[Ruben van der Steenhoven]

I think i am on a track now Michael, i think it has to do with backends.php
i came to this conclusion after finding out that 
$_SESSION['ingo']['script_categories'] returns nothing.

I think that file needs some modifications not documented.
I tried this set-up in backends.php:

$backends['vfs'] = array(
     'driver' => 'vfs',
     'preferred' => 'localhost',
     'script' => 'procmail',
     'hordeauth' => 'user',
     'params' => array('procmailrc' => '.procmailrc',
                       'vfstype' => 'ftp',
                       'hostspec' => 'localhost',
                       'port' => 21));

first of all: why use ftp as vfstype?
   What user/password combination would be used?
   Can i set this to sql?
   Do i need special settings in .procmailrc?

Ruben van der Steenhoven wrote:
> I understand your problem Michael, it can be very difficult to reproduce 
> a problem in certain situations, but it seems (to me a least) in this 
> case, that the combination of a real-life database thats been upgraded 
> along with the head-version of horde COULD result in these problems.
> 
> If my assumption is true this could result in major problems when 
> releasing HORDE 4.
> 
> I am more than willing to work with you in resolving this issue 
> step-by-step, athough i don't think this list would be the right medium 
> to do so. Is that an option for you?
> 
> Michael M Slusarz wrote:
> 
>> Quoting Ruben van der Steenhoven <ruben_donotspamme at webmeesters.nl>:
>>
>> | as you know, i have similar problems with using ingo. Maybe a full
>> | reinstallation on a fresh DB might do the trick for me too, but i think
>> | this may be an issue worth looking into, because if more people have
>> | this problem, and version 4 becomes stable, some serious issues may
>> | arise, especially on bigger sites.
>>
>> Unfortunately, there is nothing I can personally do about this.  Vague
>> claims of "ingo didn't work, but I reinstalled my entire Horde 
>> installation
>> and it works fine now" doesn't leave me with much (if any) information I
>> can use to 'fix' the problem.  So if I can't either 1) reproduce the
>> problem myself or 2) get a concise report on what _fixed_ the problem, 
>> you
>> can't expect to see any changes (at least from me).
>>
>> michael
>>
>> ______________________________________________
>> Michael Slusarz [slusarz at bigworm.colorado.edu]
>> The University of Colorado at Boulder
>>
> 
> 
>