On 12/22/2011 7:06 AM, Thomas Leuxner wrote:
Am 22.12.2011 um 12:59 schrieb Stephan Bosch:
That is why I didn't explicitly announce this change. The .sieve extension only has significance in the filesystem (to make
sure that the Sieve interpreter refuses to open anything but Sieve scripts). When specified in the Sieve language, that
extension would just be part of the script name, meaning that<< include "global.sieve";>> maps to
`global.sieve.sieve' on the filesystem. So, in your case using<< include :global "global";>> should
fix it.
Because it is technically a bugfix, it is also due to be released for Dovecot
v2.0.
Is it a big problem to change your include instructions? Is anyone else
depending on this unintended feature?
Not a biggie at all to fix on my end. And thanks for the explanation.
Not a biggie here either, but my "include"s specified the full filename
too. I guess I never read the CMUSieve migration page, since my scripts
weren't migrated. So I suspect this will trip up other installations.
Good to know, thanks!
