[ingo] migrate from php-imap-filter to sieve

Patrick Domack patrickdk at patrickdk.com
Fri Oct 2 14:03:44 UTC 2009

That would be correct.
Since ingo stores it's rules in it's own format, it will create all  
the rules it can in the new format. not all formats support all rules  
though, so some rules might be lost, atleast till changed again, or  
support for those filtering methods where added (unless this was  
changed recently? I don't really see how it could be fixed though)

Quoting Peter Meier <peter.meier at immerda.ch>:

> Hi
> currently we are using prefs storage for ingo filters and filter with
> php. However with a new upcoming mailbackend, we'd like to switch to use
> sieve and manage the filters through managesieve.
> as it is stated on the ingo website: "System administrators are able to
> switch to a different filter system or script storage at any time and
> the users' filter rules will persist." can we assume that we only need
> to switch the backend and trigger a rewrite of the filters? I don't
> fully understand what you mean with that.
> Anybody ever switched the filter engine? Experiences?
> thanks a lot and cheers
> pete
> --
> 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

More information about the ingo mailing list