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

[Peter Meier]

Hi

>>> 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)
>>
>> will it create the rules if somebody stores them again or during the
>> next login?
>>
> If the user tell ingo to store it again, yes, it will. Depending on the
> settings for ingo, it might also store it when a rule is
> added/deleted/modified.
>
> During the next login? I don't believe so, I haven't looked though and
> dunno about recent versions of ingo

the above is fine, we can easily tell the users to save their filters again.

>> does it still save the rules in its own format? If we use managesieve
>> to deploy the scripts, what will happen if somebody deploys their own
>> sieve script with managesieve?
>>
> 
> Yes, ingo will ALWAYS save it's rules in it's own format (in the prefs
> system? believe this is changable in recent versions)

ok good to know. Maybe I messed up the different storages, currently we
have it in the very own ingo_rules table.

> If someone updates it manually using like thunderbird, cause you have
> the managesieve port world accessable, then their ingo rules would be
> idle and not used. Since the support for sieve scripts seems to be so
> rare, I would put that down to user knowledge, only manage your scripts
> using webmail or yourself, don't attempt both, unless you know sieve,
> and thunderbird sieve support requires user knowledge of how sieve works
> so.

Yeah, all the geeks you can easily tell to pay attention. For all the
others the only supported way is via webinterface.

Thanks for all your answers!

cheers pete