There was a problem parsing your filter rules: parse error: evaluating Sieve script

Here is what you need to do to get rid of this problem.

I think that after a zimbra update the existing filter rules are somehow incompatible and are causing this troubles.
This Bugreport describes some similar problem.

To get rid of the old filter rules i try to delete them using the zimbra admin console.
Some more Information on the commands can be found in the Zimbra Wiki.

List existing filter rules:

zmmailbox -m <account-email-address> -z getFilterRules
# z/--zadmin   use zimbra admin name/password from localconfig for admin/password

Delete a filter rule:

zmmailbox -m <account-email-address> -z deleteFilterRule "name displayed in getFilterRules"

After deleting all filter rules i could add new ones using the zimbra collaboration suite.

The instructions for Installing a GoDaddy cert in zimbra wiki did not work for us.
Tomcat did not start up after we applied our new keystore.

Here is what worked out for us. Hopefully this will help others:

# openssl pkcs12 -inkey <your-ssl-key.key> -in <your-ssl-cert.crt> -export -out out.pkcs12

java -classpath $JETTY_HOME/lib/org.mortbay.jetty.jar org.mortbay.util.PKCS12Import out.pkcs12 keystore.fresh

sudo /opt/zimbra/java/bin/keytool -delete -alias 1 -keystore keystore.fresh

# cat <your-ssl-cert.crt> gd_intermediate.crt gd_cross_intermediate.crt > all.crt

# keytool -import -alias tomcat -keystore keystore.fresh -trustcacerts -file all.crt

/opt/zimbra/bin/tomcat restart

symptoms:

Suddenly we could not check in certain files. The checkin lasted at least 4 minutes.
On the client side we got the error:

svn: PUT request failed on '/repos/...'
svn: PUT of '/repos/...': 500 Internal Server Error (https://svn.webmeisterei.com/)

And in the error.log of apache we found:

[Wed Dec 12 14:27:06 2007] [error] [client 194.183.146.178] Could not get next bucket brigade  [500, #0]

Googling for svn bucket brigade made me think our repositry got corrupted by the last checkin.
svnadmin verify did not find any corruptions, and a dump and load revocery of the repository
did not help either.

In addition, defining svn:externals like this:

#
# Create this file: svn propget svn:externals . > EXTERNALS.txt
# Apply this file:  svn propset svn:externals -F EXTERNALS.txt .
#

package1      https://svn.webmeisterei.com/repos/foo/package1/trunk
simplejson    http://svn.red-bean.com/bob/simplejson/tags/simplejson-1.7/simplejson

resulted on the following error when checking the directory in after applying the property:

At least one property change failed; repository is unchanged

solution

If you encounter one of these errors you might want to check if your firewall has something to do with it.
In our case the Intrusion Protection has matched patterns when commiting certain files and svn:externals properties.

Usage:
You need a Container with Elements like

<div id="npContainer">
  <div class="npItem">Item1</div>
  <div class="npItem">Item2</div>
</div>

also you need the Columns

<div id="npColumn1"></div>
<div id="npColumn2"></div>
<div id="npColumn3"></div>

In Javascript just call:

jQuery().npColumns();

jQuery NPColumns Plugin Download

Online Demo: http://www.bregenzerwald-news.at/?classifieds=1

Example: (–dry-run try operation but make no changes)

me:~/mytrunk $ svn merge --dry-run -r32074:32182 \

https://svn.host.com/branch/mybranch