Used the following script:

C_FILES=`git ls-files *.c`
H_FILES=`git ls-files *.h`
for F in "$C_FILES $H_FILES"; do
        echo "$F"
  perl -p -i -e 's/safe_memset\(&\(?([^,]*)\)?,\s*0,\s*sizeof\(\g1\)\)/i_zero_safe(&$1)/g' $F
  perl -p -i -e 's/safe_memset\(([^,]*),\s*0,\s*sizeof\(\*\g1\)\)/i_zero_safe($1)/g' $F
  perl -p -i -e 's/memset\(&\(?([^,]*)\)?,\s*0,\s*sizeof\(\g1\)\)/i_zero(&$1)/g' $F
  perl -p -i -e 's/memset\(([^,]*),\s*0,\s*sizeof\(\*\g1\)\)/i_zero($1)/g' $F
done

Added assertions.

This allows extension of test commands that evaluate the message somehow.
Currently this is implemented only for the message header.
Extensions can thereby influence what headers are evaluated and how.

lib-sieve: optimized compilation of tests that yield constant results (i.e. known at compile tme), such as true and false.
If the result of a test is known at compile time, it is optimized away. If an if-command depends on an entirely constant test, it is optimized away as well,
causing only the 'true' sub-block to be compiled.

- Changed operand read functions to prove exec status return codes in stead of boolean.
- Restructured optional-operand, stringlist and string-match APIs to provide execution status (error code) upon failure.
- Corruption errors are only produced when the binary is actually corrupt. Normal failures should never cause a recompile attempt anymore.
- Simplified optional-operand API.
- Cleaned up test command implementations that use the string-match API.

Testsuite: added RFC compliance tests for the variables extension and fixed use of wrong default comparator.