How to prevent (?) sieve from running ...
jwade at oakton.edu
Thu Sep 30 01:41:08 EDT 2004
Reduce the logging level for cyrus from debug to something less verbose
in your syslog config. At debug level on a heavily used mail server it
is amazing how many CPU cycles syslog will take. If you really wanted
to see all the other debug messages you could also comment out the line
in sieve/script.c that reads:
syslog(LOG_DEBUG, "IOERROR: fstating sieve script %s: %m", fname);
and then recompile. (In 2.2.3 it is on line 426) However, I think most
people would just recommend a lower logging level unless you are
actually debugging a problem.
Hope this helps,
Christiaan den Besten wrote:
> Hi All !
> More requests, sorry, have been googling, but can not find any answers
> on the web.
> My logs are filling up with sieve fstating attemps. Is there anyway to
> disable sieve ? (or at least the messages in the logfile ?)
> Sep 28 13:54:25 mail3 lmtpunix: accepted connection
> Sep 28 13:54:25 mail3 lmtpunix: lmtp connection preauth'd as
> Sep 28 13:54:25 mail3 lmtpunix: IOERROR: fstating sieve script
> /var/lib/imap/sieve/S/raymond/defaultbc: No such file or directory
> Cyrus Home Page: http://asg.web.cmu.edu/cyrus
> Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
More information about the Info-cyrus