similar to: Sieve Header question.

Displaying 20 results from an estimated 1000 matches similar to: "Sieve Header question."

2018 Dec 04
2
BUG: sieve does not set seen-Flag
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???????
2018 Dec 04
3
BUG: sieve does not set seen-Flag
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
2018 Dec 04
2
BUG: sieve does not set seen-Flag
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
2018 Dec 04
2
BUG: sieve does not set seen-Flag
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
2018 Dec 04
0
BUG: sieve does not set seen-Flag
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 exactly what you are doing wrong, but I use lmtp to deliver the mail to mbox formatted mailboxes. On Tue, Dec 4, 2018 at 9:11 AM Jakobus Sch?rz <wertstoffe at nurfuerspam.de> wrote: > I tried it like you... doesn't work. The message
2018 Jan 03
2
sieve/internal error/detail subaddress and IMAP4FLAGS.
I'm trying to set an IMAP Flag with the detail part of an address, but getting an internal error: an 3 13:37:27 thebighonker exim[537]: 1eWoqt-00008f-4u <= ler at lerctr.org H=(lrosenman.local) [74.203.163.58]:4650 I=[192.147.25.65]:587 P=esmtpsa X=TLSv1.2:ECDHE-RSA-AES256-GCM-SHA3 84:256 CV=no SNI="smtp.lerctr.org" A=dovecot_login:ler S=769 id=20180103193716.oofszdaxopnkgfvd at
2018 Dec 04
0
BUG: sieve does not set seen-Flag
2.3.4/0.5.4 (dovecot/pigeonhole) Note the casing on the \\Seen flag. On Tue, Dec 4, 2018 at 9:02 AM Jakobus Sch?rz <wertstoffe at nurfuerspam.de> wrote: > 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
2018 Dec 04
0
BUG: sieve does not set seen-Flag
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
2018 Dec 04
0
BUG: sieve does not set seen-Flag
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 "spamtrap at spambouncer.org"; addflag "MyFlags" "\\Seen Junk"; fileinto :flags
2018 Dec 04
2
BUG: sieve does not set seen-Flag
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 >
2018 Dec 04
2
set seen flag and junk moving a mail manually to JUNK
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
2018 Mar 02
1
Sieve filter imapflags with "flagvar" not working
its quite likely fixed in 0.4.22 ---Aki TuomiDovecot oy -------- Original message --------From: Larry Rosenman <larryrtx at gmail.com> Date: 02/03/2018 19:55 (GMT+02:00) To: Konstantinos Tsakiltzidis <ktsakiltzidis at modulus.gr>, dovecot at dovecot.org Subject: Re: Sieve filter imapflags with "flagvar" not working I don't remember if this was fixed in 0.4.21 or not,
2018 Dec 04
2
set seen flag and junk moving a mail manually to JUNK
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
2008 Nov 25
1
Unable to use imapflags in sieve
Hello, I'm using dovecot 1.1.6 with libsieve 2.2.5 and I can't use the imapflags extension. Here's the begginning of my .dovecot.sieve file : require ["fileinto"]; #require "imapflags"; #require "reject"; #if header :contains "X-DSPAM-Probability: 0.9" { # addflag "$label3"; #} # On d?place le spam dans le dossier Spam et on
2020 Jul 02
3
LLVM Incubator + new projects draft
On Wed, Jul 1, 2020 at 11:12 PM Chris Lattner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I'm not sure I agree with the no-code standard. I agree with minimal code, but I think an incubator should be established enough to be discussed concretely (e.g. "what is" vs "ideals"). > > I hear what you’re saying, but I think we can handle this as part of
2020 Jul 01
6
LLVM Incubator + new projects draft
This looks to be a reasonable starting point. A couple of nit picks, none are blockers. 1. I'd hold off on handing out the sub-domain for the moment. This feels more official than we probably want for a random incubator.  I reserve the right to change my mind here, but maybe we should delay this part until we see what actual incubators look like?  As an alternative, maybe
2017 Apr 25
4
Pigeonhole / Bug with "duplicate" ?
Hello, Previously, while running Dovecot 2.2.27/Pigeonhole 0.4.16 the following code snippet was working as one would expect: if duplicate { addflag ["\\seen", "Duplicate"]; fileinto "Duplicate"; stop; } if address :contains "to" "user.email at example.com" { addflag "$label1"; } After upgrading to
2006 Aug 16
2
Server Push, with Active MQ?
I''ve read the postings about Juggernaut with interest, it is an interesting approach but in wondering about a solution that wouldn''t require flash I did some searching and came across activemq (http://incubator.apache.org/activemq). Their approach for messaging to an AJAX client (http://incubator.apache.org/activemq/ajax.html)seems to be a combination of polling and keeping
2016 Nov 04
2
How does one mark all messages as read (imap4flag "seen") with sieve?
Hello! I had hoped that marking all messages that arrive to a specific mailbox as read/seen would be as simple as applying the following sieve script to all incoming mail for that mailbox user: ######################## require ["imap4flags"]; addflag "\\Seen"; ######################## With this script in-place, mail does not appear to be marked as read/seen. It arrives as it
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