Hello, I am using a custom directory for sieve logs and trace and it apparently generate an error, in some corner case. - I have an IMAP global sieve script, that is run when appending emails into the "Archives" folder. - I have Thunderbird configured to archive emails by year When archiving an email, for instance in "Archives/2018", I often have an error message like this: Mar 31 08:03:02 homebox dovecot[14078]: imap(andre): Error: sieve: trace: creat(/home/users/andre/mails/sieve/logs//andre.Archives/2018.3.20180331-080302.14235.5.trace) failed: No such file or directory I have this configuration (amongst) for sieve logs: sieve_user_log = ~/mails/sieve/logs/ sieve_trace_dir = ~/mails/sieve/logs/ sieve_trace_level = commands sieve_trace_debug = yes sieve_trace_addresses = yes Did I a misconfigured something? Thanks for your help, Andr? -- https://github.com/progmaticltd/homebox
Op 3/31/2018 om 9:27 AM schreef Andr? Rodier:> Hello, > > I am using a custom directory for sieve logs and trace and it apparently > generate an error, in some corner case. > > - I have an IMAP global sieve script, that is run when appending emails > into the "Archives" folder. > - I have Thunderbird configured to archive emails by year > > When archiving an email, for instance in "Archives/2018", I often have > an error message like this: > > Mar 31 08:03:02 homebox dovecot[14078]: imap(andre): Error: sieve: > trace: > creat(/home/users/andre/mails/sieve/logs//andre.Archives/2018.3.20180331-080302.14235.5.trace) > failed: No such file or directory > > I have this configuration (amongst) for sieve logs: > sieve_user_log = ~/mails/sieve/logs/ > sieve_trace_dir = ~/mails/sieve/logs/ > sieve_trace_level = commands > sieve_trace_debug = yes > sieve_trace_addresses = yes > > Did I a misconfigured something?No, this not your fault. This is just a very, very stupid bug. Regards, Stephan.
Op 3/31/2018 om 9:27 AM schreef Andr? Rodier:> Hello, > > I am using a custom directory for sieve logs and trace and it apparently > generate an error, in some corner case. > > - I have an IMAP global sieve script, that is run when appending emails > into the "Archives" folder. > - I have Thunderbird configured to archive emails by year > > When archiving an email, for instance in "Archives/2018", I often have > an error message like this: > > Mar 31 08:03:02 homebox dovecot[14078]: imap(andre): Error: sieve: > trace: > creat(/home/users/andre/mails/sieve/logs//andre.Archives/2018.3.20180331-080302.14235.5.trace) > failed: No such file or directory > > I have this configuration (amongst) for sieve logs: > sieve_user_log = ~/mails/sieve/logs/ > sieve_trace_dir = ~/mails/sieve/logs/ > sieve_trace_level = commands > sieve_trace_debug = yes > sieve_trace_addresses = yes > > Did I a misconfigured something?This should fix the trace directory problem: https://github.com/stephanbosch/pigeonhole-core/commit/ee0d15407d231198519b4f87a0fc533b941765a2 I still need to create some CI tests for this and it needs some internal review before it will be merged in Pigeonhole core. Also, I notice that your sieve_user_log setting points to a directory. That needs to be a file, otherwise it will not work. Regards, Stephan.
On 31/03/18 09:29, Stephan Bosch wrote:> Op 3/31/2018 om 9:27 AM schreef Andr? Rodier: >> Hello, >> >> I am using a custom directory for sieve logs and trace and it apparently >> generate an error, in some corner case. >> >> - I have an IMAP global sieve script, that is run when appending emails >> into the "Archives" folder. >> - I have Thunderbird configured to archive emails by year >> >> When archiving an email, for instance in "Archives/2018", I often have >> an error message like this: >> >> Mar 31 08:03:02 homebox dovecot[14078]: imap(andre): Error: sieve: >> trace: >> creat(/home/users/andre/mails/sieve/logs//andre.Archives/2018.3.20180331-080302.14235.5.trace) >> failed: No such file or directory >> >> I have this configuration (amongst) for sieve logs: >> sieve_user_log = ~/mails/sieve/logs/ >> sieve_trace_dir = ~/mails/sieve/logs/ >> sieve_trace_level = commands >> sieve_trace_debug = yes >> sieve_trace_addresses = yes >> >> Did I a misconfigured something? > > This should fix the trace directory problem: > https://github.com/stephanbosch/pigeonhole-core/commit/ee0d15407d231198519b4f87a0fc533b941765a2 > I still need to create some CI tests for this and it needs some internal > review before it will be merged in Pigeonhole core. > > Also, I notice that your sieve_user_log setting points to a directory. > That needs to be a file, otherwise it will not work. > > Regards, > > Stephan. >Thanks for your help and your advice, Stephen. I suppose it will take some time before being included into the Debian main repository. I have amended the sieve_user_log setting. Kind regards, Andr? -- https://github.com/progmaticltd/homebox