30% failure rate with sieve? debug output...?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



So I *finally* got my employers out of stone-age multihundred megabyte inbox files and over to cyrus. Yay!

However, we're seeing fairly consistent sieve failures. For example, 21 messages came from a certain address that we're filtering last night. 12 were filed into the subfolder correctly. 4 fell down and hit a later rule in the ruleset, and 5 made it into my inbox. Grepping through the logs (at debug level) indicates zero complaints from sieve.

So... clue me in. How do I get real debugging enabled? I want very verbose output stored somewhere so that I can analyze the failures...

--
Jo Rhett
Senior Network Engineer
Network Consonance

----
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

[Index of Archives]     [Cyrus SASL]     [Squirrel Mail]     [Asterisk PBX]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [KDE]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux