Displaying 20 results from an estimated 6000 matches similar to: "sieve rules processing"
2009 Jul 08
4
Sieve vacation with russian subject
Hello list,
I have noticed that sieve vacation action breaks some non-english letters in the subject.
I tested with russian language, if subject contains letters from specific diapason russian alphabet, the message received with unreadable subject, but text in the body with the same letters looks ok.
Here is example of full subject header, it contains russian alphabet:
Subject:
2009 Jul 20
3
[Bug] dovecot deliver v1.2.1 segfaults
Hello list,
I have noticed strange dovecot behavior with exim system-filter.
I'm using exim+dovecot setup. My exim configuration have system filter enable, which restrict some attachments, like exe, vbs etc. When message with forbidden attachment received, exim accept the message, then construct bounce-message(Reject reason + original message) and returns it to sender. Trying to deliver such
2009 Jul 30
2
sieve delivery to utf folders
Hello list,
Today, my users have noticed, that delivery to folders with non-english names is broken. For example, if I create russian directory, it correct encoded and display into mail-client program and my webmail:
Encoded: Normal view
.INBOX.&BEIENQRBBEI- ????
This is part of sieve script, which routing delivery to russian folder.
....
elsif allof (header :contains "Subject"
2009 Oct 28
3
expire plugin + --exec-mail in 1.2.6 version
Hello list,
After upgrade to dovecot version 1.2.6 I have noticed some quota malfunctions(users become often overquota). Looking at logs closely I have found that quota value resets to general dovecot-config(
quota = maildir:Mailbox quota
quota_rule = *:storage=500M
quota_rule2 = Trash:storage=10%%
), after dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool.sh command. The problem that
2015 Apr 30
2
Sieve Rule: What am I missing here?
I have a rule that sends all mail from root to a mailbox, but I want it to
NOT send mail from mailing-lists there.
if allof (address :contains :localpart "From" "root",
not anyof(exists ["List-Id","List-ID","Mailing-List",
"X-List-Name","List-Post"]))
{
fileinto "root-mail";
stop;
}
2010 May 15
2
sieve spamtest extension
Hello Stephan,
First of all, thanks for time you spent implementing this useful extension.
I have found some ugly behavior with such config:
sieve_extensions = +notify +spamtest
sieve_spamtest_status_type = score
sieve_spamtest_status_header = X-Spam-Scan-Score: (-?[[:digit:]]+\.[[:digit:]])
sieve_spamtest_max_value = 10
Sieve:
require
2012 Jul 06
2
Pigeonhole Sieve SetFlag question
Hello,
I use
FreeBSD 8.2-RELEASE-p7 i386
dovecot-2.1.6
dovecot-pigeonhole-0.3.0_1
I have the following problem:
When I use the following script - the flag is set in \Seen :
require ["imap4flags"];
# rule:[test]
if anyof (header :contains "Subject" "test")
{
setflag "\\Seen";
stop;
}
. SELECT INBOX
* OK [CLOSED] Previous mailbox
2016 Nov 30
2
Sieve script won't compile. Compiler output isn't helpful.
Hey martin,
Thanks for the reply! I made the changes you suggested but I got the
same results.
According to my understanding, #header "from" "person at example.com"# is
correct for an exact match.
On 11/30/2016 04:10 AM, Martin Wheldon wrote:
> Hi Steven,
>
> I think you may be missing the :contains from the two header lines below:
>
>> if anyof (header
2019 Nov 16
2
Sieve and recipient_delimiter
I use recipient_delimiter addresseses quiet a bit, and I want to put several of them into a mailbox
if anyof (header :contains ["to"] [ ?FOO", ?foo", ?bar", ?florin"]) {
fileinto :create ?later";
stop;
}
When I get an email addressed to me+FOO at example.com or me_florin at example.com, the messages end up in my inbox (Yes, I have both + and _
2018 May 28
3
Second rule isn't apply when first rule matches
Dear list,
I want to define two concurrent rules :
1. I want to flag an e-mail containing the word "cloud" in the body
2. I want to move mail sent explicitly to me (as opposed to mail sent to an alias I am part of) going to "INOBX.I must answere this"
If I put rule (1) first, everything works as expected. If put rule (2) first, only that rule applies.
Here's a small test
2016 Nov 30
2
Sieve script won't compile. Compiler output isn't helpful.
Hello! I hope you will forgive my ignorance but I have a problem I have
been trying to solve for a week and I'm not sure where else to turn.
I'm trying to write a sieve script to sort all of my mail. I was writing
this script to replace the one I am currently using but I can't seem to
get it to compile. I don't know a lot about sieve or really scripting of
any kind and I just
2016 Nov 30
3
Sieve script won't compile. Compiler output isn't helpful.
Hello Martin,
Wow. That was indeed the problem. I have been staring at that small
script for a week and I just couldn't see it. I even had a friend look
at it and he couldn't find it either. I feel a bit ridiculous now.
Thanks so much for your help,
Steven
On 11/30/2016 04:48 AM, Martin Wheldon wrote:
> Hi Steven,
>
> OK a on closer inspection :)
>
> You are missing
2011 Dec 12
3
dovecot 2.1.rc1: sieve and folders with umlauts
Hi,
now the umlauts problem with sieve:
# cat /mailspool1/in-preetz.de/test1/.dovecot.sieve
## Generated by Roundcube Webmail SieveRules Plugin ##
require ["fileinto"];
# rule:[Test]
if anyof (header :contains "Subject" "test")
{
fileinto "m&APY-";
}
Error: DBBjDsXL5U7mIAAA/TNBsA: sieve: execution of script
2012 Apr 05
3
Problem with polish characters and sieve fileinto
Hi,
I have problems with sieve fileinto and polish characters in folder names:
# rule:[??????????????????]
elsif anyof (header :contains "Subject" "??????????????????")
{
fileinto "INBOX/&AQUBBwEZAUIBRADzAVsBegF8AQQBBgEYAUEBQwDTAVoBeQF7-";
}
dovecot log:
Apr 5 15:17:42 mailer dovecot: lmtp(54203, test at test1.com):
rmHVJHabfU+70wAA9hAjDg: sieve:
2009 Aug 19
1
expire plugin: columns not uniq
Hello list,
My dovecot setup have expire plugin enabled. It is working fine: new records added to database(sqlite), expire-tool successfully expunges old mail, but when expire-tool try to update database record for processed user, I get error in logs:
root at mail dovecot 0:0 # /usr/sbin/dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool.sh --test
Info: koshikov.n at domain.com/Spam:
2009 Jul 22
1
Released Sieve v0.1.9 for Dovecot v1.2.1
Hello Dovecot users,
Relatively many bugs and problems were reported recently in a short
period of time. Apparently, now that Dovecot v1.2 is finally stable, the
new Sieve plugin is also starting to get used much more. No known bugs
remain. Let's hope I didn't spawn any new ones.
Apart from the bugfixes I made the deprecated notify plugin
implementation compatible with CMUSieve. You
2009 Jul 22
1
Released Sieve v0.1.9 for Dovecot v1.2.1
Hello Dovecot users,
Relatively many bugs and problems were reported recently in a short
period of time. Apparently, now that Dovecot v1.2 is finally stable, the
new Sieve plugin is also starting to get used much more. No known bugs
remain. Let's hope I didn't spawn any new ones.
Apart from the bugfixes I made the deprecated notify plugin
implementation compatible with CMUSieve. You
2015 Aug 07
2
pigeonhole/lda accessing -m folder
hi jost thx for the reply,
by access I mean to read the variable
require ["fileinto", "variables", "?destfolder?" ];
if anyof ( destfolder :matches "*") {
fileinto "${1}/subfolder";
}else{
fileinto "INBOX/subfolder";
}
On 08/07/2015 12:26 PM, Jost Krieger wrote:
> On Fri Aug 7 12:19:22 2015, matthias lay wrote:
2009 Jul 28
3
dovecot 1.2.1 and sieve-0.9.1
Hi all,
ok, can someone tell me which header fields that the "Sender" function
in sieve looks at ???
I've created a sieve rule to move a mail to a directory that looks like
this :
# rule:[File Message]
if anyof (address :contains "Sender" "Dude")
{
fileinto "TestFolder";
}
And the emails headers look like this :
Received: (qmail 5811 invoked
2018 Jun 30
4
How to log a Sieve match in Dovecot debug_log
Hi everybody!
I manage a mail server running Dovecot 2.2.21 with Pigeonhole 0.4.10. I successfully configured sieve and use it also to filter some spam messages. Here is one of the script I use to filter messages on the basis of prohibited words in message body.
As you can see, the last command writes to the log the action of this script.
-- the script begins ------------
require