> On 30 Jun 2018, at 15:41, Lukas wrote:
>
> Sorry @lbutlr, this is a very silly answer to my question...!
> My script is not the definite spam solution on my mail server, obviously.
It doesn't matter. Triggering on specific words is not a spam solution.
> So, if you can help, please, help m
t;
A: "dovecot"
Inviato: Sabato, 30 giugno 2018 23:13:39
Oggetto: Re: How to log a Sieve match in Dovecot debug_log
On 30 Jun 2018, at 03:28, Lukas wrote:
> body :text :contains "crypto",
> body :text :contains "sex",
> body :text
On 30 Jun 2018, at 03:28, Lukas 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
Am Samstag, 30. Juni 2018, 12:33:49 CEST schrieb Lukas:
> 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 un
mpler to maintain if you have a long list of word. And here comes my
previous question: it would be great if there is a way to log the matching word
in order to know what word in that list was the "culprit".
Lukas
----- Messaggio originale -
Da: "Volker Wysk"
A: "
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 p
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 comman
