I think I figured out what happened. I think I edited the .sieve file but
forgot to save it, so I was actually running an old version that did not have
?mailbox? in the require statement.
On which note, two more questions:
1. Is there any documentation about what ?requires? are needed to access
various features? The only source I?ve found for this is reverse-engineering
examples.
2. Is there a way to change the location of the sieve logfile that gets created
when a sieve script produces an error? Right now it ends up in the same
directory as the script, but I?d prefer to have in /var/log along with
everything else.
rg
On Jan 19, 2021, at 11:02 PM, Aki Tuomi <aki.tuomi at open-xchange.com>
wrote:
>
>> On 20/01/2021 08:46 Ron Garret <ron at flownet.com> wrote:
>>
>>
>> On Jan 19, 2021, at 10:40 PM, Aki Tuomi <aki.tuomi at
open-xchange.com> wrote:
>>
>>>
>>>> On 19/01/2021 19:45 Ron Garret <ron at flownet.com>
wrote:
>>>>
>>>>
>>>> I?m trying to get a sieve script to move messages into a
folder, and to create that folder if it doesn?t already exist. I?m following
the example code at:
>>>>
>>>> https://doc.dovecot.org/configuration_manual/sieve/examples/
>>>>
>>>> and doing this:
>>>>
>>>>> require ["fileinto", "mailbox?];
>>>>> ?
>>>>> fileinto :create ?myfolder?;
>>>>> ?
>>>>
>>>> That results in this error in the log file:
>>>>
>>>> error: unknown tagged argument ':create' for the
fileinto command
>>>>
>>>> What am I doing wrong?
>>>>
>>>> rg
>>>
>>> Which version of dovecot/pigeonhole is this?
>>
>> I?m not sure. How would I find out? I just installed it on Debian
using apt.
>>
>>> I tested this with 2.3.13 and it worked just fine. Are those quotes
mangled by your mailer or do you really have some fancy quotes in your sieve
script?
>>
>> Not sure what you mean by ?fancy quotes?. The quotes I have (and the
ones I see in your quoted message) are regular ascii double quotes, code point
0x22.
>>
>> But I think it is actually working now. I didn?t change anything, it
just seems to have spontaneously started working. Maybe sieve was working off
an earlier version of the script that it had cached?
>>
>> rg
>
> Ok. Sieve (re)compiles scripts when it sees that they change (comparing
file dates). It does not cache scripts in memory.
>
> Aki