similar to: How to log a Sieve match in Dovecot debug_log

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",

Am Samstag, 30. Juni 2018, 11:28:43 CEST schrieb Lukas: > 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

Sorry @lbutlr, this is a very silly answer to my question...! My script is not the definite spam solution on my mail server, obviously. In addition to Spamassassin, blacklist implementation, SPF, DKIM and more, I need to filter some specific messages with particular words and log the script action. In my first mail I made an example with three really obvious words but my need is not about sex or

On 30 Jun 2018, at 03:28, Lukas <lukas at email.it> wrote: > body :text :contains "crypto", > body :text :contains "sex", > body :text :contains "viagra" This is a very silly way to try to deal with spam. In fact, your own message to the list will be flagged by your rule. Actual spam message will illy not even hit this rule as

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

Anybody here familiar with the Sieve language? I'm rebuilding my mail server, and I am working with the sieve language to automatically filter spam into a separate account. However, I've hit a snag that I can't get around. BTW, I'm using a clean install of dovecot, postfix, spamassassin on Debian 7.5. I want to do server-side spam filtering, so I've got spamasassin

Hello, I'm trying to do a simple thing using imapsieve, I want messages to be marked as read when moved to certain folders (Trash, Archive, Spam). All the set up to run the imapsieve script works perfectly, but I'm having trouble to make changes effective. As the RFC says, IMAP messages are immutable, but it's not clear to me reading the specs if this applies to IMAP flags too, as one

Hi all, I want to add a custom header to incoming emails from a particular sender. This is what my user Sieve script looks like: require ?editheader?; if address :is "From? ?special-sender at example.com? { addheader ?X-My-Custom-Header? ?Header Value"; } I have enabled the editheader extension in my Dovecot configuration: plugin { ? sieve_extensions = +editheader }

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 >

I'm trying to get blow Sieve filter to work require ["fileinto", "imap4flags", "mailbox", "body", "envelope", "vnd.dovecot.pipe", "variables", "vnd.dovecot.execute"]; if envelope :matches "To" "*@*" { set "recipient" "${0}"; set "user" "${1}"; set

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]]

In order to simplify auto-response suppression and other filtering, I want to synthesise an Auto-Submitted header on notification mails that should have them but do not. In a sieve file I add the following: if anyof ( header :contains ["From","Sender"] ?info at example.com" ) { if header :contains "Subject" [" just joined "," just left

Hi I'm changing from fetchmail to getmail, in order to fetch my mail from several mail servers and deliver it to my local dovecot server. Fetchmail supports LMTP, getmail doesn't. So I'm making getmail call dovecot-lda for delivering the mail. But now, the incoming mail doesn't get filtered through sieve any longer. However, this command works: sieve-filter -v -u v

Hello, Dovecot. Is it possible to write one rule in sieve, which will: (1) Trigger on any message with "List-Id" header AND (2) Put this message to folder with name build from content of "List-Id" header, in such way, that message with List-Id List-Id: This is decription of list <list-name.host.org> will be put into folder "org.host.list-name" where

Server: Ubuntu 10.04 LTS 32bit There seems to be an incompatibility when compiling Pigeonhole against Dovecot v2.2.13.rc1. # make check with Pigeonhole throws up the following error message: <snip> Test case: ./tests/extensions/editheader/addheader.svtest: 1: Test 'Addheader - first' SUCCEEDED 2: Test 'Addheader - last' SUCCEEDED 3: Test 'Addheader - framed'

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

Hello! Dovecot 2.2.34 (874deae) Pigeonhole version 0.4.22 (22940fb7) After the update to pigeonhole version 0.4.22 the following configuration does not work. With version 0.4.21 it works. dovecot.conf (only sieve configuration) --------------------------------------------------------------- managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope

> Please try a stable version of LAME. I don't really know what to do > with this backtrace. It would also help immensely if you could > reproduce the crash reliably (eg on the same song). DEBUG: Using LAME version 3.93 (gdb) bt #0 0x402b7585 in III_dequantize_sample () from /usr/local/lib/libmp3lame.so.0 #1 0x402d1200 in ispow () from /usr/local/lib/libmp3lame.so.0 Cannot access

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello guys, I'm having troubles making "script_after" to exec sieve scripts:: So: plugin { quota = maildir quota_rule2 = INBOX.Trash:ignore quota_rule3 = INBOX.Sent:ignore sieve = ~/Maildir/sieve/dovecot1.sieve sieve_before = /etc/dovecot/sieve/global.sieve sieve_after =

Op 3/3/2018 om 9:15 AM schreef Stephan Bosch: > Op 3/3/2018 om 2:57 AM schreef Jan: >> Hello! >> > We're looking into it. Right, this is not reproducible in the test suite, but I can reproduce it when I replicate your setup. Regards, Stephan. >> Dovecot 2.2.34 (874deae) >> Pigeonhole version 0.4.22 (22940fb7) >> >> After the update to pigeonhole