[ingo] Possible bug?

[ANANT S ATHAVALE]

Dear Jan,

Thanks for your response.  Please find attached conf.php and  
backends.php of Ingo.  I have no problem in using Filters as such.   
Only problem is, Folder Overview in Portal Page is not referring to  
ingo_rules table and instead shows values from horde_prefs.



----- Message from jan at horde.org ---------
     Date: Thu, 04 Feb 2010 18:19:55 +0100
     From: Jan Schneider <jan at horde.org>
  Subject: Re: [ingo] Possible bug?
       To: ingo at lists.horde.org


> Zitat von ANANT S ATHAVALE <asa at isac.gov.in>:
>
>> Dear List,
>>
>> We have setup the latest stable Horde Groupware webmail edition.   
>> Today we noticed that, on the Portal Page where we can have summary  
>> of Mail,Filters etc, Filters Overview refers to the horde_prefs  
>> table instead of ingo_rules.
>>
>> Has anybody else noticed this?  How do I quickly solve this problem.
>
> No, and it doesn't make any sense, because any code in Ingo is using  
> the same global $ingo_storage object. And that always points to the  
> same, configured backend.
>
> Jan.
>
> -- 
> Do you need professional PHP or Horde consulting?
> http://horde.org/consulting/
>
> -- 
> Ingo mailing list - Join the hunt: http://horde.org/bounties/#ingo
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: ingo-unsubscribe at lists.horde.org
>


----- End message from jan at horde.org -----



Regards,

Anant Athavale.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: conf.php
Type: text/x-c
Size: 656 bytes
Desc: not available
URL: <http://lists.horde.org/archives/ingo/attachments/20100205/0f62c98f/attachment.bin>
-------------- next part --------------
<?php
/**
 * $Horde: ingo/config/backends.php.dist,v 1.20.8.12 2008-12-15 02:33:07 chuck Exp $
 *
 * Ingo works purely on a preferred mechanism for server selection. There are
 * a number of properties that you can set for each backend:
 *
 * driver:       The Ingo_Driver driver to use to store the script on the
 *               backend server. Valid options:
 *                   'null'       --  No backend server
 *                   'timsieved'  --  Cyrus timsieved server
 *                   'vfs'        --  Use Horde VFS
 *                   'ldap'       --  LDAP server
 *
 * preferred:    This is the field that is used to choose which server is
 *               used. The value for this field may be a single string or an
 *               array of strings containing the hostnames to use with this
 *               server.
 *
 * hordeauth:    Ingo uses the current logged in username and password. If
 *               you want the full username at realm to be used to connect then
 *               set this to 'full' otherwise set this to true and just the
 *               username will be used to connect to the driver.
 *
 * params:       An array containing any additional information that the
 *               Ingo_Driver class needs.
 *
 * script:       The type of Ingo_Script driver this server uses.
 *               Valid options:
 *                   'imap'      --  IMAP client side filtering
 *                   'maildrop'  --  Maildrop scripts
 *                   'procmail'  --  Procmail scripts
 *                   'sieve'     --  Sieve scripts
 *
 * scriptparams: An array containing any additional information that the
 *               Ingo_Script driver needs.
 *
 * shares:       Some drivers support sharing filter rules with other users.
 *               Users can then configure filters for each other if they
 *               give them permissions to do so. If you want to enable this
 *               feature, you need to set this parameter to true.
 */

/* Sieve Example */
$backends['sieve'] = array(
    'driver' => 'timsieved',
    'preferred' => 'localhost',
    'hordeauth' => true,
    'params' => array(
        // Hostname of the timsieved server
        'hostspec' => 'localhost',
        // Login type of the server
        'logintype' => 'PLAIN',
        // Enable/disable TLS encryption
        'usetls' => false,
        // Port number of the timsieved server
        'port' => 2000,
        // Name of the sieve script
        'scriptname' => 'ingo',
        // The following settings can be used to specify an administration
        // user to update all users' scripts. If you want to use an admin
        // user, you also need to disable 'hordeauth' above. You have to use
        // an admin user if you want to use shared rules.
        // 'username' => 'cyrus',
        // 'password' => '*****',
        // Enable debugging. With Net_Sieve 1.2.0 or later, the sieve protocol
        // communication is logged with the DEBUG level. Earlier versions
        // print the log to the screen.
        'debug' => false,
    ),
    'script' => 'sieve',
    'scriptparams' => array(),
    'shares' => false
);