similar to: Pigeonhole Sieve SetFlag question

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

Did you notice the fileinto :flags usage? It comes from imap4sieve extension. https://tools.ietf.org/html/rfc5232#page-7 Aki > On 04 December 2018 at 17:13 Larry Rosenman <larryrtx at gmail.com> wrote: > > > I've been using that recipe for YEARS, and it DOES work for me on FreeBSD > (I'm also the port maintainer for dovecot and pigeonhole). > > Not sure

Hi all, ok, I just instealled the dovecot 2.0.0 release, and the latest mercurial pigeonhole source. All is well, except for a particular sieve rule that may not be working right. It is a simple rule that looks like this : require ["fileinto","imap4flags"]; # rule:[Past Due Notices] if allof (header :contains "Subject" "Account Past Due Notice") {

I tried it like you... doesn't work. The message gets all the other flags, but not the \Seen-Flag. My repo is https://repo.dovecot.org/ce-2.3-latest/debian/stretch stretch dpkg -l|grep dove ii? dovecot-core????????????????????? 2:2.3.4-2~stretch????????????? amd64??????? secure POP3/IMAP server - core files ii? dovecot-imapd???????????????????? 2:2.3.4-2~stretch????????????? amd64???????

Hi Ralph! This is, what calls the correct sive-filter rules. I have that already in use. But the file file:/etc/dovecot/sievepipe/report-spam contains my sieve-script from my first posting. So, the difference from setflag to addflag is, setflag sets the flags, and only the given flags (removing all other flags), and addflag adds a flag to the existing flags... I fiddled around a little... The

Now i tried an additional rule in my "normal" working sieve-filter: if address :domain :matches "from" "company.example" ? { setflag "\\seen"; fileinto :create "INBOX/foo/test"; stop; } and sent an email from my company-account. The folder INBOX/foo/test gets created, but the message inside is not marked as seen. So i think, this is a bug in

Which version of dovecot are you using? jakob Am 04.12.18 um 15:44 schrieb Larry Rosenman: > I have the following, and it works: > require ["include","fileinto","imap4flags","variables"]; > global "MyFlags"; > if header :contains ["X-LERCTR-Spam-Flag","X-TNTSCAN-Spam-Flag"] "YES" > { > redirect

Hi there! I want to set the \seen and the Junk Flag to an email, which i move manually to my Junk-Folder. I tried a lot... but nothing worked like expected. I have a sieve-filter, which takes an email and copy it to a pipe to rspamc. This filter is working correctly, i get a debug-message from the script, which is called through the sieve-filter. But adding another rule (addflag

I have a rule in sieve like the following: if anyof (header :contains ["to"] [ "box", "change", "cornell?, ?twitter?]) { setflag "\\Seen"; fileinto :create "misc"; stop; } The messages that come in are using address extensions, so user+twitter at example.com, for example. The trouble is, this sieve recipe doesn?t get triggered and

How would I setup dovecot so that when messages are moved to the Archive mailbox, they are marked as read? Would it be similar to the imap-sieve for spam tagging? imapsieve_mailbox1_name = Junk imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve Or is there a simpler method? If it matters: mailbox Archive { auto = subscribe

Yes. I did it the same way, Larry described. And i have in my sieve-script, which i use also for years the other notation i tried before, many times in use. The last month it did not recognize, that this rules won't work any longer. Today i played around a little, then i saw, it won't work to set the \Seen-Flag... Please be aware, i can set Junk-Flag, and Thunderbird shows me the Emails

On 2/11/2015 8:41 PM, Stephan Bosch wrote: > On 2/11/2015 7:34 PM, Florin Portase wrote: >> Hello guys, >> >> I'm having troubles making "script_after" to exec sieve scripts:: >> > Keep in mind that the sieve_after script is only executed when the > "keep" action [1] is executed or when the implicit "keep" [2] is still >

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

Op 28-5-2018 om 14:18 schreef daniel_1983 at protonmail.com: > 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

Following the rfc5232, Sieve Email Filtering: Imap4flags Extension the following filter doesn't work when the `"flagvar"` part is added require "imap4flags"; if header :contains "X-Spam" "Yes" { ? setflag "flagvar" "spam"; } removing the `"flagvar"` part works as expected # 2.2.33.2 (d6601f4ec):

I have an additional information. Moving a already seen messsage to another imap-folder (drag&drop in thunderbird) shows this email in the other folder as unseen and recent. Is this normal behaviour? BR Jakob Am 04.12.18 um 16:36 schrieb Jakobus Sch?rz: > Yes. I did it the same way, Larry described. > > And i have in my sieve-script, which i use also for years the other >

On 2015-02-12 01:01, Stephan Bosch wrote: > On 2/11/2015 10:37 PM, Portase Florin wrote: On 2/11/2015 8:41 PM, Stephan Bosch wrote: On 2/11/2015 7:34 PM, Florin Portase wrote: Hello guys, > > I'm having troubles making "script_after" to exec sieve scripts:: > > Keep in mind that the sieve_after script is only executed when the > "keep" action [1 [1]]

Hi Volker! This is what I wanted to avoid with my question. I reported my script with only three word just to make an example but my list is quite longer than this. Let's suppose a list of 30 or 40 words... 30 or 40 rules? Possible but very unconfortable to manage. A more compact version of the script could be this: -- the script begins ------------ require ["fileinto",

Hello Dovecot users, This is a bugfix release to mend some problems that were found in v0.5.0. The imap4flags bug is actually not first seen in the 0.5.0 release (it is ancient), but I included the fix for it anyway. Changelog v0.5.0.1: - imap4flags extension: Fix binary corruption occurring when setflag/addflag/removeflag flag-list is a variable. - sieve-extprograms plugin: Fix segfault

Hello Dovecot users, This is a bugfix release to mend some problems that were found in v0.5.0. The imap4flags bug is actually not first seen in the 0.5.0 release (it is ancient), but I included the fix for it anyway. Changelog v0.5.0.1: - imap4flags extension: Fix binary corruption occurring when setflag/addflag/removeflag flag-list is a variable. - sieve-extprograms plugin: Fix segfault