[ingo] sieve script error

Jan Schneider jan at horde.org
Fri Feb 15 23:57:15 UTC 2008

Zitat von Noah Meyerhans <noahm at csail.mit.edu>:

> Hi all.  One of my users recently started getting the following error
> when modifying her Sieve rules in Ingo:
> ====
> Success Changes saved.
> Error There was an error activating the script. The driver said:
> {62}script errors: line 33: parse error, unexpected $undefined.
> ====
> It's a simple script and the changes were trivial.  What is a reasonable
> way for me to debug this?  The rules are stored in the prefs backend in
> a postgres database, and it's pretty hard for me to learn anything
> meaningful by looking at the actual data stored in the db entry.  The
> changes do seem to show up there, as all she changed was a folder name.
> But the sieve script is untouched and still references the old folder.
> Is there a reasonable way for me, as the server admin, to look at the
> user's rules in the Ingo interface?

How does the generated script look like? That's the important bit of  


Do you need professional PHP or Horde consulting?

More information about the ingo mailing list