Re: [Dovecot] Annoying "feature" in dovecot/pidgeonhole - include depth limitation

2011-09-11 Thread Stephan Bosch
On 9/11/2011 12:07 PM, Timo Sirainen wrote: On 11.9.2011, at 13.01, Stephan Bosch wrote: I've made the limits for the include extension configurable now. This will be included in the next release. Is there really a need for such a limit? Isn't it mainly to avoid infinite loops, which could a

Re: [Dovecot] Annoying "feature" in dovecot/pidgeonhole - include depth limitation

2011-09-11 Thread Timo Sirainen
On 11.9.2011, at 13.01, Stephan Bosch wrote: > I've made the limits for the include extension configurable now. This will be > included in the next release. Is there really a need for such a limit? Isn't it mainly to avoid infinite loops, which could also be detected by seeing if there are any

Re: [Dovecot] Annoying "feature" in dovecot/pidgeonhole - include depth limitation

2011-09-11 Thread Stephan Bosch
On 9/10/2011 4:36 AM, Mihai Moldovan wrote: Hi all, I'm using dovecot 2.0.14 build on Debian. The maintainers obviously patch the dovecot source so that it uses the pidgeonhole sieve system. Today I ran into a very annoying issue: I created several sieve scripts and interlinked via the include

[Dovecot] Annoying "feature" in dovecot/pidgeonhole - include depth limitation

2011-09-10 Thread Mihai Moldovan
Hi all, I'm using dovecot 2.0.14 build on Debian. The maintainers obviously patch the dovecot source so that it uses the pidgeonhole sieve system. Today I ran into a very annoying issue: I created several sieve scripts and interlinked via the include command, only to find dovecot spewing this er