On Sun, 2025-06-29 at 16:25 -0400, Genes Lists via dovecot wrote:
On Sun, 2025-06-29 at 15:04 -0400, Genes Lists via dovecot wrote:
On Sun, 2025-06-29 at 13:57 -0400, Genes Lists via dovecot wrote:
I am not yet sure, but I just renamed the "after" file from default.sieve to after.sieve. I will know later, but looks like personal scripts might just possibly be working after that.
Not sure that makes any sense but ...
fingers crossed.
I can confirm now that after renaming the "after" script file from default to something else - everything is running as usual.
The lesson I came away with:
1) do not use the filename 'default.sieve' for anything (other than possibly a default script). 2) ensure that certificate file must readable by all users, otherwise sievec will fail for non-root.
-- Gene
On Sun, 2025-06-29 at 16:25 -0400, Genes Lists via dovecot wrote: On Sun, 2025-06-29 at 15:04 -0400, Genes Lists via dovecot wrote: On Sun, 2025-06-29 at 13:57 -0400, Genes Lists via dovecot wrote:
I am not yet sure, but I just renamed the "after" file from
default.sieve to
after.sieve.
I will know later, but looks like personal scripts might just
possibly be
working after that.
Not sure that makes any sense but ...
fingers crossed.I can confirm now that after renaming the "after" script file from default to something else - everything is running as usual.
The lesson I came away with:
1) do not use the filename 'default.sieve' for anything (other than possibly a default script). 2) ensure that certificate file must readable by all users, otherwise sievec will fail for non-root.
-- Gene