wrong filter rule execution after upgrade

Hi,
since we upgrade from ingo 2.0.7 to 2.0.8 we got a wrong filter rule execution. All
e-mails from inbox are moved to subfolder defined by the rule. The horde log shows:
WARN: HORDE [ingo] PHP ERROR: array_merge() [<a
href='function.array-merge'>function.array-merge</a>]: Argument #2 is not an array [pid 29870 on
line 626 of "/usr/share/php/Horde/Imap/Client/Search/Query.php"]
Is this an ingo or an imp issue? Thanks for your help.
Rene

Hi,
since we upgrade from ingo 2.0.7 to 2.0.8 we got a wrong filter rule execution. All
e-mails from inbox are moved to subfolder defined by the rule. The horde log shows:
WARN: HORDE [ingo] PHP ERROR: array_merge() [<a
href='function.array-merge'>function.array-merge</a>]: Argument #2 is not an array [pid 29870 on
line 626 of "/usr/share/php/Horde/Imap/Client/Search/Query.php"]
Is this an ingo or an imp issue? Thanks for your help.
Rene

Re: wrong filter rule execution after upgrade

Zitat von Rene Zeipelt <zeipelt@...>:

> Hi,
> since we upgrade from ingo 2.0.7 to 2.0.8 we got a wrong filter rule  
> execution. All
> e-mails from inbox are moved to subfolder defined by the rule. The  
> horde log shows:
> WARN: HORDE [ingo] PHP ERROR: array_merge() [<a  
> href='function.array-merge'>function.array-merge</a>]: Argument #2  
> is not an array [pid 29870 on line 626 of  
> "/usr/share/php/Horde/Imap/Client/Search/Query.php"]
> Is this an ingo or an imp issue? Thanks for your help.
> Rene

http://bugs.horde.org/ticket/11197

--

-- 
Jan Schneider
The Horde Project
http://www.horde.org/

Re: wrong filter rule execution after upgrade

> Am 01.06.2012 11:27, schrieb Jan Schneider:
>>
>> Zitat von Rene Zeipelt <zeipelt@...>:
>>
>>> Hi,
>>> since we upgrade from ingo 2.0.7 to 2.0.8 we got a wrong filter rule execution. All
>>> e-mails from inbox are moved to subfolder defined by the rule. The horde log shows:
>>> WARN: HORDE [ingo] PHP ERROR: array_merge() [<a
href='function.array-merge'>function.array-merge</a>]: Argument #2 is not an array [pid 29870 on
line 626 of "/usr/share/php/Horde/Imap/Client/Search/Query.php"]
>>> Is this an ingo or an imp issue? Thanks for your help.
>>> Rene
>>
>> http://bugs.horde.org/ticket/11197
>>
> Thanks. The Commit 958daacad7e1b85c539a9f5fc00b9fade123c645 helps.
> Rene

> Am 01.06.2012 11:27, schrieb Jan Schneider:
>>
>> Zitat von Rene Zeipelt <zeipelt@...>:
>>
>>> Hi,
>>> since we upgrade from ingo 2.0.7 to 2.0.8 we got a wrong filter rule execution. All
>>> e-mails from inbox are moved to subfolder defined by the rule. The horde log shows:

Filter doesn`t work (H4)

Hi!

I try to use mail filtering by ingo but anything I do doesn`t work.

My storage driver is sql; the table "ingo_rules" (postgres) is the place
where conditions are stored in. But as if the filter is not active, the
mail is not placed in another folder as defined in the active rule. For
testing I have switched off any other filter.

The configuration seems to be okay for that the rules in "ingo_rules"
changes if I change the rule in the frontend.

Has someone had the same problem?

Best Regards

Joe

Re: Filter doesn`t work (H4)

Am 08.06.2012 14:30, schrieb Christopher Neuhaus:
> Hi!
> 
> I try to use mail filtering by ingo but anything I do doesn`t
> work.
> 
> My storage driver is sql; the table "ingo_rules" (postgres) is the
> place where conditions are stored in. But as if the filter is not
> active, the mail is not placed in another folder as defined in the
> active rule. For testing I have switched off any other filter.
> 
> The configuration seems to be okay for that the rules in
> "ingo_rules" changes if I change the rule in the frontend.
> 
> Has someone had the same problem?
> 
> Best Regards
> 

What is your filter driver? How did you configure backends.local.php?

--

-- 
Ralf Lang
Linux Consultant / Developer
Tel.: +49-170-6381563
Mail: lang@...

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de

Re: Filter doesn`t work (H4)

Please do not contact me personally but keep discussions on the list.

> 
> In conf.php: $conf['storage']['driver'] = 'sql'; (the table
> "ingo_rules" fills up with the rule)
> 
> The backends.php is the dist-version:
> 
> /* IMAP Example */ $backends['imap'] = array( // ENABLED by
> default 'disabled' => false, 'transport' => 'null', 'hordeauth' =>
> true, 'params' => array(), 'script' => 'imap', 'scriptparams' =>
> array(), 'shares' => false );
> 
> [...]
> 
> all other entries: 'disabled' => true
> 

The "imap" filter driver only works ondemand or onclick. It's not an
active filter, you need to trigger it manually.

You need a procmail, sieve or similar backend for active filtering.

--

-- 
Ralf Lang
Linux Consultant / Developer
Tel.: +49-170-6381563
Mail: lang@...

Re: Filter doesn`t work (H4)

Please do not contact me personally but keep discussions on the list.

Am 08.06.2012 14:47, schrieb Christopher Neuhaus:
> 2012/6/8 Ralf Lang <lang@...>
> 
> Please do not contact me personally but keep discussions on the
> list.
> 
>>>> 
>>>> In conf.php: $conf['storage']['driver'] = 'sql'; (the table 
>>>> "ingo_rules" fills up with the rule)
>>>> 
>>>> The backends.php is the dist-version:
>>>> 
>>>> /* IMAP Example */ $backends['imap'] = array( // ENABLED by 
>>>> default 'disabled' => false, 'transport' => 'null',
>>>> 'hordeauth' => true, 'params' => array(), 'script' => 'imap',
>>>> 'scriptparams' => array(), 'shares' => false );
>>>> 
>>>> [...]
>>>> 
>>>> all other entries: 'disabled' => true
>>>> 
> 
> The "imap" filter driver only works ondemand or onclick. It's not
> an active filter, you need to trigger it manually.
> 
> You need a procmail, sieve or similar backend for active
> filtering.

Re: Filter doesn`t work (H4)

Zitat von Ralf Lang <lang@...>:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> Please do not contact me personally but keep discussions on the list.
>
> Am 08.06.2012 14:47, schrieb Christopher Neuhaus:
>> 2012/6/8 Ralf Lang <lang@...>
>>
>> Please do not contact me personally but keep discussions on the
>> list.
>>
>>>>>
>>>>> In conf.php: $conf['storage']['driver'] = 'sql'; (the table
>>>>> "ingo_rules" fills up with the rule)
>>>>>
>>>>> The backends.php is the dist-version:
>>>>>
>>>>> /* IMAP Example */ $backends['imap'] = array( // ENABLED by
>>>>> default 'disabled' => false, 'transport' => 'null',
>>>>> 'hordeauth' => true, 'params' => array(), 'script' => 'imap',
>>>>> 'scriptparams' => array(), 'shares' => false );
>>>>>
>>>>> [...]
>>>>>
>>>>> all other entries: 'disabled' => true
>>>>>

Re: Filter doesn`t work (H4)

2012/6/8 Jan Schneider <jan@...>

>
> Zitat von Ralf Lang <lang@...>:
>
>
>  -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>>
>> Please do not contact me personally but keep discussions on the list.
>>
>> Am 08.06.2012 14:47, schrieb Christopher Neuhaus:
>>
>>> 2012/6/8 Ralf Lang <lang@...>
>>>
>>> Please do not contact me personally but keep discussions on the
>>> list.
>>>
>>>
>>>>>> In conf.php: $conf['storage']['driver'] = 'sql'; (the table
>>>>>> "ingo_rules" fills up with the rule)
>>>>>>
>>>>>> The backends.php is the dist-version:
>>>>>>
>>>>>> /* IMAP Example */ $backends['imap'] = array( // ENABLED by
>>>>>> default 'disabled' => false, 'transport' => 'null',
>>>>>> 'hordeauth' => true, 'params' => array(), 'script' => 'imap',
>>>>>> 'scriptparams' => array(), 'shares' => false );
>>>>>>