[ingo] Accessing .dovecot.sieve

[Patrick Domack]

Hmm, not really from my understanding/implementation.

With sieve you can have many scripts.
In my case they get uploaded into the sieve directory.
I have ingo set to upload it to a file called ingo.
What happens is after ingo uploads it's script, it sets it active.
When managesieve/pysieve gets the set active command it symlinks  
.dovecot.sieve to sieve/ingo (in this case)
Then the next time dovecot deliever runs, it compiles it into .dovecot.sievec

If you are not going to use managesieve/pysieve or other sieve server,  
then you would upload directly to .dovecot.sieve


Quoting Jan Schneider <jan at horde.org>:

> Zitat von Maik Stubbe <lupus at stubbi.org>:
>
>>
>> Am 30.09.2009 um 21:22 schrieb Michael M Slusarz:
>>
>>> Quoting Maik Stubbe <lupus at stubbi.org>:
>>>
>>>> Hi,
>>>>
>>>> I would like to use my existing sievescript in  
>>>> $vmail/%d/%u/.dovecot.sieve. Editing the backend.php doesn't work  
>>>> for me [1].
>>>>
>>>> Any ideas how to access the .dovecot.sieve and edit it with ingo?
>>>
>>> You can't.  Ingo has no ability to parse pre-existing files.
>>>
>>> michael
>>
>> Any chance to save the new script to $vmail/%d/%u/.dovecot.sieve?  
>> This also would solve my problem
>
> Of course. That's what Ingo is supposed to do with Dovecot/Sieve.
>
> 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
>