similar to: blames for using maillists ?

Displaying 20 results from an estimated 2000 matches similar to: "blames for using maillists ?"

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") {
2023 Mar 11
1
set imap flags in user sieve scripts
spi skrev den 2023-03-11 13:34: > if address :domain "From" "whatever.com"{ > fileinto :flags ["\\todo"] "working/whatever"; > } require ["fileinto","imap4flags"]; # rule:[set todo] if allof (header :contains "subject" "set imap flags in user sieve scripts", header :contains "from" "user at
2020 Feb 18
3
managesieve / sieve - append dot prefix on moving mails into folder
Hello mailinglist-subscribers, i have an issue with the managesieve / sieve plugin in dovecot. We use roundcube as webmailer and if i define a new filter to move incoming mails directly into a subfolder i get the following sieve-code: require ["fileinto","imap4flags"]; # rule:[mail into folder] if allof (header :contains "from" "sender at domain.org") {
2020 Jul 12
2
Sieve and handling multiple addresses
On 12 Jul 2020, at 10:17, Benny Pedersen <me at junc.eu> wrote: > @lbutlr skrev den 2020-07-12 16:43: >> I an trying to write a sieve action that will take mail that is >> addressed to a user only it is filed in a mailbox (e.g. "Direct") if >> it is to the email AND to any other email address, then file it in a >> mailbox named, e.g. "Cc". And
2020 Jul 19
3
Sieve and handling multiple addresses
On 18 Jul 2020, at 11:23, Stephan Bosch <stephan at rename-it.nl> wrote: > On 12/07/2020 22:47, @lbutlr wrote: >> On 12 Jul 2020, at 10:17, Benny Pedersen <me at junc.eu> wrote: >>> @lbutlr skrev den 2020-07-12 16:43: >>>> I an trying to write a sieve action that will take mail that is >>>> addressed to a user only it is filed in a mailbox
2023 Mar 11
1
set imap flags in user sieve scripts
11.03.2023 19:23:21 Benny Pedersen <me at junc.eu>: > spi skrev den 2023-03-11 13:34: > >> if address :domain "From" "whatever.com"{ >> fileinto :flags ["\\todo"] "working/whatever"; >> } > > require ["fileinto","imap4flags"]; imap4flags seems not to be accepted in an user script. My sieve editor
2020 Jul 12
2
Sieve and handling multiple addresses
I an trying to write a sieve action that will take mail that is addressed to a user only it is filed in a mailbox (e.g. "Direct") if it is to the email AND to any other email address, then file it in a mailbox named, e.g. "Cc". And if the mail is not addressed to the user at all, sieve does nothing with it. Message 1: to foo at example.com => Direct Message 2: to/cc foo at
2016 Mar 01
1
which DNS backend ?
Hi Reindl, For me there lot of misunderstanding around DNS, especially when it comes to AD and a bit more when that AD is Samba AD. This thread just shows that once more time. I'm relatively new in DNS world and learnt a lot these last months, thanks to colleagues who are daily DNS admins and who accept to enlighten me a little bit. You claim to be a DNS admin and you said Rowland and you
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
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
2020 Sep 05
2
Default sieve mark seen?
I have the following in my default.sieve file: require "fileinto"; if header :contains "X-spam-flag" "YES" { require ["vnd.dovecot.pipe", "copy", "imapsieve", "environment", "variables", "imap4flags"]; setflag "\\Seen"; fileinto "Junk"; } This is largely unchanged, except that I
2016 Jul 26
2
[PATCH] Add support for the 'unless' matcher in the dynamic layer.
I was wondering if there is any objection to removing the 2-element minimum on the eachOf, anyOf and allOf matchers. It is frustrating when playing with matchers to have to edit significant amounts of code to be able to temporarily go from 2 to 1 matcher inside an any- or allOf matcher. And overall it feels very "un-set-theory"-like. The change was made here:
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
2013 Feb 01
4
[LLVMdev] Asserts in bundleWithPred() and bundleWithSucc()
Jakob, I have a question about the following (four) asserts recently added in bundleWithPred() and bundleWithSucc() (see below). What is the real danger of reasserting a connection even if it already exist? My problem with them happens when I try to call finalizeBundle() on an existing bundle to which I have added a new instruction. The goal - a new bundle header with liveness abbreviation, but
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
2019 May 29
1
Changes in sieve Dovecot 2.2
Hi People, I'm use dovecot in my mailbox system, until last month i used the dovecot version 2.0 and now i use version 2.2, version 2.2 works well for me, but i have one small problem, in sieve. In version 2.0 i had rules in sieve similiar to rule bellow: if allof (true){ keep; fileinto "INBOX"; redirect "xxxxxx"xxxxxx.com.br"; stop; } In the new version
2023 Mar 11
1
set imap flags in user sieve scripts
Hi all Could anyone lead me into the right direction please? I use 'addflag ...' or 'fileinto :flags ...' in global sieve scripts to flag and sort incoming mail - that works. Trying to do that with custom user scripts doesn't work - I get the error that imap4flags only can be used in global scripts. Is there any way to get incoming mails labled and sorted by user sieve
2013 Aug 14
2
proxy: get rid of redundant log-informations
Hi login_log_format_elements = user=<%u> method=%m rip=%r %k is it possible to get rid of the "proxy(test at testserver.rhsoft.net): started proxying to 127.0.0.1:143: " part because on a proxy-only server i know that and it is explicitly not listed in "login_log_format_elements" as well as for the "TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA" it would be
2016 Jul 26
2
[PATCH] Add support for the 'unless' matcher in the dynamic layer.
Even if it still did add overhead, it seems perfectly reasonable, from a user's perspective (namely mine), that if I introduce unnecessary narrowing matchers to my chain that there may be a performance penalty. The ability to do the following easily outweighs any performance issues for me: anyOf ( /* hasName("..."), */ hasName("...") ) though C++ not allowing