[ingo] Re: Does ingo read existing scripts?

Michael M Slusarz slusarz at bigworm.colorado.edu
Mon Jan 19 11:38:04 PST 2004

Quoting Christian Tramnitz <maillist at tramnitz.com>:

| Jan Schneider wrote:
| >Parsing existing scripts into an Ingo rule set is pretty hard if not
| >unpossible. If you could come up with a working solution, we'd happily
| >accept a patch.
| >
| >Jan.
| >
| >
| >
| I'm no coder and I even don't know if anyone really *needs* this feature.
| For now I'd be happy to know where Ingo "caches" it's current ruleset.
| E.g. when creating a sieve rule with Ingo and then changing it using en
| editor: When using Ingo the next time it will still present what it
| created itself the last time, so if I made the changes there instead of
| the sieve rule directly this could already help...

Ingo stores it's internal data structure in a Horde preference variable
(although, in the future, other storage drivers (e.g. sql) could be coded). 
See ingo/config/prefs.php


Michael Slusarz [slusarz at bigworm.colorado.edu]
The University of Colorado at Boulder

More information about the ingo mailing list