[horde] Ingo and Sieve?

[Arjen de Korte]

Citeren Matthew <mw at robotmouse.com>:

> On 03/05/15 19:44, Arjen de Korte wrote:
>> Citeren Matthew <mw at robotmouse.com>:
>>
>>> I've done this recently, and it worked quite well. You should see  
>>> a sieve example in your backends.php; I removed all the comments  
>>> but basically mine is as below.
>>>
>>> But note there is something strange in Ingo setup; I copied  
>>> backends.php to backends.local.php and deleted all the other  
>>> disabled backends, leaving just sieve - but it didn't work - I  
>>> just see whitelist and blacklist. But if I leave all the disabled  
>>> ones in, it works! I get full functionality. I didn't bother  
>>> trying to figure out what triggered it - just left them all in.
>>>
>>> (Note if you have not yet done so, you may need to get your MTA to  
>>> deliver mail to Dovecot LMTP instead of directly to the inbox;  
>>> again, let me know if unsure, having done this also recently!)
>>>
>>> ---
>>>
>>> $backends['sieve'] = array(
>>>    'disabled' => false,
>>>    'transport' => array(
>>>        Ingo::RULE_ALL => array(
>>>            'driver' => 'timsieved',
>>>            'params' => array(
>>>                'hostspec' => 'localhost',
>>>                'logintype' => 'PLAIN',
>>>                'usetls' => true,
>>>                'port' => 4190,
>>>                'scriptname' => 'ingo',
>>>                'debug' => false,
>>>            ),
>>>        ),
>>>    ),
>>>    'script' => array(
>>>        Ingo::RULE_ALL => array(
>>>            'driver' => 'sieve',
>>>            'params' => array(
>>>                'utf8' => false,
>>>             ),
>>>        ),
>>>    ),
>>>    'shares' => false
>>> );
>>
>> The above is wrong in so many ways, that I doubt you've actually  
>> read the comments in the backends.php (which is sadly all too  
>> common).
>>
>> First, don't use 'array' anywhere in any *.local.php file. See the  
>> example in the header. This syntax is mandatory or you risk  
>> breaking things when additional values are added in future releases.
>>
>> Second, the 'imap' backend is enabled by default. You must disable  
>> it in your backends.local.php, otherwise it will still be used  
>> instead of another backend you enable. That's why you only see the  
>> white- and blacklist.
>>
>> Third, you should only need to enable a single backend. It is  
>> pointless to keep the others in your backends.local.php.
>>
>> Last, all these things have been mentioned countless times on the  
>> mailinglists before. Search the archives in case of problems...
>
> Oops - missed this; I had to set this server up fairly quickly and I  
> had it working OK so didn't get too involved! Now re-rendered it  
> into direct element assignments rather than the array declarations,  
> and seems to be working with just the one in there. Thanks!
>
> But maybe the examples in the backends.php should now be in the  
> preferred format? Reformatting the examples is fiddly for somebody  
> not familiar with PHP...

Except that backends.php is the default configuration, it is not an example.

-- 
This message was sent from a mailinglist subscription address.
For off-list replies, you must remove the address extension.