similar to: Default sieve mark seen?

> On 12 Jun 2018, at 01:23, Alex JOST <jost+lists at dimejo.at> wrote: > > Am 12.06.2018 um 01:01 schrieb @lbutlr: >> 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 { >>

On 30 Oct 2020, at 12:34, @lbutlr <kremels at kreme.com> wrote: > I am not sure about the $1. I think filter just pipes the message (or part of the message. > > I will see what happens without the echo I suppose. > > Nope, still the same. > > 32: starting `:contains' match with `i;ascii-casemap' comparator: > 32: matching value `<!DOCTYPE

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 =

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

> On 30/10/2020 19:25 Bernd Petrovitsch <bernd at petrovitsch.priv.at> wrote: > > > On 30/10/2020 17:11, @lbutlr wrote: > [...] > > echo $1 | sed -e '|</head>|<style>* {color:white !important; background-color: black !important; } </style></head>|' > > What should the sed stuff do? > TTBOMK '|' is not known by sed ...

I am trying to create some sieve scripts to filter my mailing lists and am wondering if sieve logs anywhere, and it so where? I don?t see anything in mail.log beyond lines like: dovecot: lda(kremels at kreme.com)<39790><hNchChSkAV1umwAAIdGjjQ>: sieve: msgid=<267D5D71-D99C-4790-8706-C1A92BCC9F97 at kreme.com>: stored mail into mailbox ?INBOX' Which doesn?t really tell me

On 10/21/20 2:12 PM, @lbutlr wrote: > Do I HAVE to have a default.sieve, that's the only thing that I can think the has changed in that folder. RE: compile, fyi note @ https://wiki2.dovecot.org/Pigeonhole/Sieve/Usage#Manually_Compiling_Sieve_Scripts https://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration#Executing_Multiple_Scripts_Sequentially the conditions under which you need to

Since switching to lmtp in dovecot, mail to user+mailboix at example.com does not get saved in ?.mailbox? as it did with LDA, instead it gets saved into the INBOX. If it matters, these are users who do NOT have a ~/.active_sieve file. I could understand (though it would bene a bit annoying) if the save overrode this mechanism. I did add lmtp_save_to_detail_mailbox = yes in the protocol lmtp

Any ideas on this? > On 05 Sep 2020, at 11:47, @lbutlr <kremels at kreme.com> wrote: > > 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",

Error: program `/usr/lib/dovecot/sieve/sa-learn-spam.sh' terminated abnormally, signal 11 Error: sieve: pipe action: failed to pipe message to program `sa-learn-spam.sh': refer to server log for more information. [2019-05-29 17:59:12] What server log? This is all that get logged. # pwd /usr/lib/dovecot/sieve # ls -lsa > total 96 > 8 drwxrwxrwx 3 root wheel 512 Jun 18 2018

I am in troubles with compiling sieve scripts larger than 1MB. I see in logs following errors: Aug 19 13:10:26 mail dovecot: lmtp(z.z at xxx.xxx)<22117><uNBGHKIIPV9lVgAA5ldI4A>: Error: sieve: autoreply: line 16818: quoted string started at line 3 is too long (longer than 1048576 bytes) Aug 19 13:10:26 mail dovecot: lmtp(z.z at xxx.xxx)<22117><uNBGHKIIPV9lVgAA5ldI4A>:

On 13 Jun 2018, at 12:51, Sami Ketola <sami.ketola at dovecot.fi> wrote: > Are you sure your sieve even gets executed? Anything in the logs? can you enable mail_debug=yes and try again? > Can you post your doveconf -n? I am not sure. I?ve made a couple of changes (put the default script and compiled script into their own folder and defined sieve_global), but still no joy. In fact,

Hello, The documentation says imapsieve_url "has no effect on the administrator-controlled Sieve scripts". However, when setting this item, I get lines such as: Error: imapsieve: mailbox INBOX: Failed to read /shared/imapsieve/script mailbox attribute: Mailbox attributes not enabled and that's it. imapsieve_mailboxXXX_* settings are completely ignored. Unsetting imapsieve_url

I am now trying portmaster -f dovecot-2.3.6 which is reinstalling 78 ports. ?? On Wed, May 15, 2019 at 7:26 PM Cerebus the Aardvark <kreme at kreme.com> wrote: > > I've rebuilt dovecot, but no change in behavior. > > I also enabled debug, but nothing else is logged to /var/log/dovecot > as to why IMAP is crashing. > > On Wed, May 15, 2019 at 5:46 PM @lbutlr via

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 action of this script. -- the script begins ------------ require

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

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

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

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

That's what I was afraid of. Some users are trying to set up vacation message with inline picture. I am aware it's not ideal but in some cases it's needed. It would be nice if this configuration option works in the future. Regards, Zdenek On 8/19/20 5:01 PM, Stephan Bosch wrote: > > > Op 19-8-2020 om 13:47 schreef Zden?k Z?me?n?k: >> I am in troubles with compiling