On 10/21/20 1:10 PM, @lbutlr wrote:

I have trace logs enabled for user scripts, but I think only error get logged for upper level, and only along the lines of "could not compile <name of sieve>".

verify that you can compile the scripts manually, even as root

then double-check your perms on your sieve/ dir, making sure that the write perms are correct for your dovecot (other?) sieve processes

On 10/21/20 2:12 PM, @lbutlr wrote:

Do I HAVE to have a default.sieve, that's the only thing that I can think the has changed in that folder. RE: compile, fyi note @

https://wiki2.dovecot.org/Pigeonhole/Sieve/Usage#Manually_Compiling_Sieve_Scripts
https://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration#Executing_Multiple_Scripts_Sequentially

the conditions under which you need to manually pre-compile the scripts specified by sieve_before and sieve_after

HAVE to have

In my config, it's def'd, but I don't explicitly _have_ a 'default.sieve'.

& my setup generally works. So far. Whether that's luck or by-design, still remains to be seen; the real-world docs/examples for 'this' are a bit ... sketchy.

fyi, my current dovecot config includes,

protocols = imap submission lmtp sieve
mail_plugins = virtual acl fts fts_solr

protocol sieve {
	mail_plugins = $mail_plugins
	mail_max_userip_connections = 10
	managesieve_notify_capability = mailto
	managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext vnd.dovecot.pipe vnd.dovecot.filter vnd.dovecot.execute
}

plugin {

	imapsieve_mailbox1_name   = Junk
	imapsieve_mailbox1_causes = COPY
	imapsieve_mailbox1_before = file:/etc/dovecot/sieve/global/report-spam.sieve

	imapsieve_mailbox2_name   = *
	imapsieve_mailbox2_from   = Junk
	imapsieve_mailbox2_causes = COPY
	imapsieve_mailbox2_before = file:/etc/dovecot/sieve/global/report-ham.sieve

	sieve_global = /etc/dovecot/scripts/sieve
	sieve         = file:/data/sieve/%u/;active=/data/sieve/%u/active.sieve
	sieve_default = /data/sieve/default.sieve
	sieve_default_name = managesieve

	sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.filter +vnd.dovecot.execute +vnd.dovecot.debug +vnd.dovecot.imapsieve

	sieve_pipe_bin_dir    = /etc/dovecot/sieve/pipe_bin/
	sieve_filter_bin_dir  = /etc/dovecot/sieve/filter_bin/
	sieve_execute_bin_dir = /etc/dovecot/sieve/execute_bin/
	sieve_plugins = sieve_imapsieve sieve_extprograms
}

& my Roundcube config (I use RC for user-friendly Sieve UI; so far, seems best of the bunch) includes

$config['managesieve_raw_editor']   = true;
$config['managesieve_default']      = '/data/sieve/default.sieve';
$config['managesieve_script_name']  = 'managesieve';

and with that^, I do not have a

/data/sieve/default.sieve

instead, I have, for each user@example.com

tree /data/sieve/user@example.com/
	/data/sieve/user@example.com/
	├── active.sieve -> managesieve.sieve
	├── active.svbin
	├── managesieve.sieve
	└── tmp

i assume i _could_ have/use a default.sieve, but have not yet done so.

Something odd happens when I copied and pasted.

On 21 Oct 2020, at 19:05, @lbutlr kremels@kreme.com wrote:

sieve_extensions = +editheader

sieve_extensions = +editheader sieve_filter_bib_dir = /usr/lib/dovecot/sieve sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_pipe_bin_dir = /usr/lib/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms sieve_trace_dir = ~/.trace sieve_trace_level = matching sieve_user_log = ~/sieve.log

sieve_trace_level = matching sieve_user_log = ~/sieve.log }

-- "It's like those French have a different word for *everything*" - Steve Martin

On 22 Oct 2020, at 09:35, @lbutlr kremels@kreme.com wrote:

Is there a way to force the default and sieve_before scripts to log to syslog?

OK, the "top level" sieves are also logged to the users trace files along with the user's sieve files, if any. So, I am getting this:

3: address test 3: starting :matches' match with i;ascii-casemap' comparator: 3: extracting To' headers from message 3: parsing address header value @lbutlr kremels@kreme.com' 3: address value kremels@kreme.com' 3: extracting all' part from address kremels@kreme.com 3: matching value kremels@kreme.com' 3: with key *@*.' => 0 3: extracting `Cc' headers from message 3: finishing match with result: not matched 3: jump if result is false 3: jumping to line 4 ## Finished executing script 'bcc'

bcc.sieve: require ["variables", "copy"];

if address :matches ["To", "Cc"] ["*@*."] { redirect :copy "backup+295.${1}.${2}@*example.com*"; }

I've obviously done something wrong there, but what? I don't think 'redirect' has any required plugins (or at least I could find no mention of one, maybe it's implied to be part of fileinto?

-- Cause love's such an old fashioned word And love dares you to care for the people on the Edge of the night, and love dares you to change Our way of caring about ourselves, This is our last dance This is ourselves. Under Pressure.

On 22 Oct 2020, at 15:46, @lbutlr kremels@kreme.com wrote:

And it doesn't explain why "if address :matches ["To", "Cc"] ["*@*."] {" also failed to match despite also showing the email address.

...

“kremels@kreme.com” does not have a :detail part (https://wiki2.dovecot.org/Pigeonhole/Sieve/Examples talks about this).

And I am not asking for :detail

OK, fair enough. I looked at that line many times for some reason. But the first point still stand.

-- For my birthday I got a humidifier and a de-humidifier... I put them in the same room and let them fight it out.

On 22 Oct 2020, at 18:22, Sean Kamath kamath@moltingpenguin.com wrote:

...

On Oct 22, 2020, at 15:58, @lbutlr kremels@kreme.com wrote:

On 22 Oct 2020, at 15:46, @lbutlr kremels@kreme.com wrote:

...

And it doesn't explain why "if address :matches ["To", "Cc"] ["*@*."] {" also failed to match despite also showing the email address.

...

“kremels@kreme.com” does not have a :detail part (https://wiki2.dovecot.org/Pigeonhole/Sieve/Examples talks about this).

And I am not asking for :detail

OK, fair enough. I looked at that line many times for some reason. But the first point still stand.

Does you To or CC address end with a .?

No, what I am trying to get is "user" and "example" in "user@example.com"

One problem I had with :matches (if I recall correctly, I can’t find where I ran into this) is that :matches has an implicit “^” and “$” wrapped around what you’re looking for.

That would break many things, but I will look into it. What I have done for now and is working is a much more complicated process where I am manually removing the '@' myself:

require ["copy", "variables", "envelope", "fileinto", "subaddress"];

if not envelope :matches "to" "backup" { if envelope :matches "to" "*" { set :lower "name" "${1}"; if string :matches "${name}" "*@*" { set "email" "${1}_${2}"; } # Only replaces one '.' But that's OK at this point. if string :matches "${email}" "*.*" { set "name" "${1}_${2}"; } set "backup" "backup+296.${name}@..."; redirect :copy "${backup}"; } else { redirect :copy "backup+296@..."; } }

This properly redirects a copy of the message to, for example, backup+296.kremels_kreme_com@...

If all goes well, the 'else' will never trigger.

I will try your suggestion if the implicit ^$.

Like I said, I’m not 100% sure, but I suspect if you add * to the end:

if address :matches ["To", "Cc"] ["*@*.*"] {

Thanks for the advice, I will definitely give that a go,

-- Mister Teatime had a truly brilliant mind, but it was brilliant like a fractured mirror, all marvelous facets and rainbows but, ultimately, also something that was broken. --Hogfather

On 23 Oct 2020, at 05:47, @lbutlr kremels@kreme.com wrote:

Excellent! That was the secret sauce!

Thank you!

For the sake of completeness, this is what I have ended up with:

#v+ require ["copy", "variables", "envelope", "fileinto", "subaddress"]; # :matches has implicit ^ and $ around the match if not envelope :matches "to" "*backup*" { # get the top level after @ (example.com => example) if envelope :matches "to" "*@*.*" { set :lower "domn" "${2}"; } # get the user without detail (foo+bar => foo) if envelope :user :matches "to" "*" { set :lower "user" "${1}"; } # Un-needed step, but shows what is done in the trace log set "backup" "backup+297.${domn}.${user}@*somedomain*"; redirect :copy "${backup}"; } #v-

(I don't think I need fileinto)

This means that mail for user@domain.tld and user+foo@domain.tld ends up in a mailbox, today, of

backup/Maildir/.297.domain.user/

And user2@domain.tld

backup/Maildir/.297.domain.user2/

(Which means the backup IMAP hierarchy is all sorted DOY=>domain=>user)

I'd like a fail condition if the redirect for some reason cannot send, but that's a project for tomorrow.

-- and I swear it happened just like this: / a sigh, a cry, a hungry kiss, the Gates of Love they budged an inch / I can't say much has happened since / but CLOSING TIME