[SIEVE] create filter with api or cli

panzli

Hello everyone,

I’m trying to automate the setup to use the x-mail-forwarding-address attributes from our LDAP via Sieve.

Since there’s currently no Sieve API endpoint available, I decided to configure it via the CLI.

However, I ran into issues when trying to manually edit or create the following files with vim — the changes don’t seem to take effect:

/var/lib/docker/volumes/mailcowdockerized_vmail-vol-1/_data/c.com/c.c/sieve/sogo.sieve /var/lib/docker/volumes/mailcowdockerized_vmail-vol-1/_data/sieve/global_sieve_before.sieve
And another problem, I cannot find the filter, which I defined here:

Regards

ETNyx

Hello,

in general dovecot is using pre-compiled sieve scripts so maybe you need reload those? You can see it there /var/lib/docker/volumes/mailcowdockerized_vmail-vol-1/_data/c.com/c.c/.dovecot.svbin Something like doveadm sieve -u c.c@c.com reload

About screenshot, i believe this is saved in mysql database sieve_filters defined here

panzli

ETNyx Thanks for your response, but the doveadm command inside the mailcow-container does’t have the reload parameter and put or activate doesn’t provide an output until pressing STRG-C.

CK_beats

I also tried to define prefilter via the GUI.
Rejection of emails with certain file types.
Although they are displayed, they are not observed/executed.
I suspect that Sieve in general just has an integration problem with Mailcow.

ETNyx

panzli Yes sorry, my bad, did not check it and wrote it from top of my head,…

Next you can try to create your sieve file on different location by config here sieve = /var/vmail/sieve/%u.sieve it should be relative to dovecot container by dockerfile it’s mounted vmail

Edit: this one should be compiled on the fly when requested
Edit2: if this work, it will be invisible for user, most-likely,… If you need to be visible in Sogo, try to reverse engineering Sogo way,…