I see report-ham, instead of archiving? I am not entirely sure if this is an
efficient approach to archiving. My users can only set a flag for 'auto
archiving' via sieve and then 3 months after every year messages are being
moved by cron jobs, and modification logs are put into their accounts. This all
is only happening in 'dead hours'.
If you want to analyze emails, why not do it with scheduled crons after they
are archived?
> I noticed that my sieve rules are taking a very long time when archiving
> messages. I can see on my logs that every message takes about two-three
> seconds to be evaluated.
>
> My sieve for the Archive is this:
>
> cat /var/mail/vmail/mail/sieve/global/report-ham.sieve
> require ["vnd.dovecot.pipe", "copy", "imapsieve", "environment",
> "variables"];
>
> if environment :matches "imap.mailbox" "*" {
> set "mailbox" "${1}";
> }
>
> if string "${mailbox}" "Trash" {
> stop;
> }
>
> if environment :matches "imap.user" "*" {
> set "username" "${1}";
> }
>
> pipe :copy "sa-learn-ham.sh" [ "${username}" ];
>
> And my sa-learn-ham.sh is this:
>
> #!/bin/sh
> export PATH="/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin:$PATH"
> exec /usr/bin/sa-learn -u ${1} —ham
>
>
>
>
> May 09 09:17:10 imap(fran...@med-lo.eu)<9349><4gm6NAAYsagKCige>: Debug:
> sieve: multi-script: Start execute sequence
> May 09 09:17:10 imap(fran...@med-lo.eu)<9349><4gm6NAAYsagKCige>: Debug:
>
> I also noticed this happens for a few accounts. Do you know what could be
> causing this?
>
> Best,
> Francis
> _______________________________________________
> dovecot mailing list -- dovecot@dovecot.org
> To unsubscribe send an email to dovecot-le...@dovecot.org
_______________________________________________
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
