similar to: set seen flag and junk moving a mail manually to JUNK

Displaying 20 results from an estimated 3000 matches similar to: "set seen flag and junk moving a mail manually to JUNK"

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 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
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
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
0
set seen flag and junk moving a mail manually to JUNK
Ok. I tried another Thunderbird-specific Flag: require ["imap4flags", "vnd.dovecot.pipe", "copy", "imapsieve", "environment", "variables"]; if environment :matches "imap.email" "*" { ? set "email" "${1}";?? } addflag "Junk"; addflag "\\seen"; addflag "$label3"; pipe
2018 Dec 04
0
set seen flag and junk moving a mail manually to JUNK
* Jakobus Sch?rz: > addflag "Junk"; > setflag "\\seen"; That's probably not what you want, because the 'setflag' command replaces all existing flags. In any case, I recommend you use this method instead: plugin { sieve_pipe_bin_dir = /etc/dovecot/sievepipe # Message moved into Spam folder imapsieve_mailbox1_name = Junk
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
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'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
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
2018 Dec 05
3
BUG: sieve does not set seen-Flag
* Jakobus Sch?rz: > Does it matter, if the keyword-files do not match? Possibly. The keyword files define flag<->letter mappings. You have shown two files with mappings (let's call them A and B) with A being a subset of B. If a file is moved from A to B, all is fine. What happens if a file is moved from B to A is for Aki to know. ;-) > 0 $label3 > 1 NonJunk > 2 Junk > 3
2018 May 12
3
Marks as read on mover to Archive
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
2020 Jun 11
2
executing script on mail arrival from sieve
I currently have a basic script to process some mails, it runs from cron every 10 minutes, basically, sieve copies some mails to subfolder on mail arrival, script fetches mails if any from this subfolder then processes these mail, get maybe 1 or 2 or often none but cron runs the script every 10 minutes, most times not needed as nothing is retrieved it's pretty crude - but works getmail
2018 Jan 05
1
Released Pigeonhole v0.5.0.1 for Dovecot v2.3.0.
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
2018 Jan 05
1
Released Pigeonhole v0.5.0.1 for Dovecot v2.3.0.
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
2010 Aug 20
2
pigeonhole sieve imapflags bug
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") {
2018 Jun 11
2
Sieve_default
I created a sieve_default to move any spam-tagged messages into the Junk mailbox automatically, but it doesn?t appear to be working (though the other imapsieve_mailbox? scripts are working). From doveconf -n plugin { imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before =