I don't think so. Since Sieve always uses berkeley db in a rather straightforward fashion, the transaction will just be retried and the error never gets propogated up to a higher level.Given that it's for the deliver.db, which is used for duplicate delivery suppression and sieve, will an aborted locker result in sieve not correctly processing an email?
Larry
