On Mon, 31 May 2004, Bryan Fullerton wrote:
Generally, everything works. However, a small percentage of messages (~5%?) are not properly filtered by sieve and wind up in INBOX. This happens across all my users who have sieve rules setup, including me.
I first saw this problem with IMAPd v2.0.x, and migrated to 2.1.x this past weekend in hopes it was a bug - same problem. This makes me think perhaps it's not IMAPd related, but I'm hoping someone here might have worked around a similar problem.
There is an issue where if a bad sieve script is installed, an lmtpd will fail to parse any future sieve script after it tries to run that one. This is fixed in the 2.2 series with the sieve bytecode support.
-Rob
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper
--- 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
