On Wed, 5 Nov 2003, Aidan Evans wrote:
> >> for it in Cyrus 2.1 beyond 2.1.13? There does not seem to be a mention of
> >> it in 2.1.15 changes.html, but maybe it's covered under "Minor other bug
> >> fixes". If there was a correction, is it easy to incorporate into 2.1.11?
> >> I don't want to
On Tue, 4 Nov 2003, Aidan Evans wrote:
> I've just come across instances of this problem. Was there a correction
> for it in Cyrus 2.1 beyond 2.1.13? There does not seem to be a mention of
> it in 2.1.15 changes.html, but maybe it's covered under "Minor other bug
> fixes". If there was a corr
On Mon, Jun 09, 2003 at 12:07:34PM -0500, Amos Gouaux wrote:
> > On Mon, 9 Jun 2003 12:50:16 -0400 (EDT),
> > Rob Siemborski <[EMAIL PROTECTED]> (rs) writes:
>
> rs> I don't think so, I'm pretty sure its only caused by errors during
> rs> sieve_script_parse, not during sieve_execute_script
> On Mon, 9 Jun 2003 12:50:16 -0400 (EDT),
> Rob Siemborski <[EMAIL PROTECTED]> (rs) writes:
rs> I don't think so, I'm pretty sure its only caused by errors during
rs> sieve_script_parse, not during sieve_execute_script.
I'm not sure yet, but I think I might have found the culprit. The
o
On Mon, 9 Jun 2003, Amos Gouaux wrote:
> Interesting. Would an error like this also apply?
>
> sieve runtime error for X id <[EMAIL PROTECTED]>: Fileinto: Mailbox does not
> exist
>
> (The "X" is one of our users, but not myself.)
I don't think so, I'm pretty sure its only caused by err
> On Mon, 9 Jun 2003 12:14:15 -0400 (EDT),
> Rob Siemborski <[EMAIL PROTECTED]> (rs) writes:
rs> The sieve parser state doesn't get reset properly after an error. Thus
rs> once a script fails to parse, all scripts will fail to parse (try to
rs> submit a good script after a bad one in a ti
On Mon, 9 Jun 2003, Amos Gouaux wrote:
> I and a few others here have begun noticing that periodically Sieve
> won't filter a message properly. Sometimes I've even resent the
> message again to find that on that occasion it did get filtered
> just as expected. I wonder, could that BerkeleyDB lea
I and a few others here have begun noticing that periodically Sieve
won't filter a message properly. Sometimes I've even resent the
message again to find that on that occasion it did get filtered
just as expected. I wonder, could that BerkeleyDB leak for which
Rob just posted those two patches ha
