similar to: Sieve question

I cutover to a new server which uses Postfix & Dovecot to handle emails as opposed to Postfix & Courier in the old server. Below is the contents of my global sieve script and dovecot config info. The dovecot-deliver.log does show that the email is being delivered to INBOX.spam but it ends up in the INBOX instead. If I put the exact same rule in the user script, the emails are delivered

In Dovecot 1.1.11 cmusieve is apparently integrated in the Ubuntu 9.10 package "dovecot-common" since the files are there. I am wanting to right now just do a very basic test of the setup to see how it runs before doing more sophisticated steps that could obscure any errors or bugs (e.g. unit testing). So I took the following example sieve script from the wiki1 documentation: require

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

I'm using maildrop to filter mail like: xfilter "/usr/bin/spamc" xfilter "/usr/bin/bogofilter -ep" I want to change to deliver (so I can use sieve) but can deliver do this?

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

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 need some advice about replacing maildrop with the Dovecot LDA. I need to replicate a setup that uses postfix+maildrop+spamassassin. We'll be using Dovecot 1rc13. In the current setup, maildrop reads a file called .mailfilter in each user's folder, then call spamassassin according to the user's preferences. The file is simple, and looks like this -- if ( $SIZE > 20971520 ) {

I use dovecot 1.2.4 release with sieve 0.1.12 If I setup sieve-before script and latest script contains "keep" at the very end and no personal scripts found then segfault take place. here is part of exim log: 2009-09-01 18:43:06 1MiUZA-0005V9-IB ** ivanov_maxim at domain.my <admin at domain.my> R=localuser T=local_delivery: Child process of local_delivery transport (running

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

Hi all, I am trying to setup a mail server using postfix (virtual_mailboxes), spamassassin and dovecot, along with SQL where appropriate. From my research so far I realized that, for several reasons, it is required for me to use dovecot LDA instead of maildrop, local, procmail or other alternatives. My configuration was working flawlessly, until spamassassin per-user configuration came to

Hi, I have written a plugin so that each time a message is added to a specific box, a program is run and the message is piped into it. Note that the message is also really added to the box. I've been using it for nearly 3 month, for spam/ham learning, and have not had any problem with it. I guess it could also be used to implement an out box (I remember seeing someone asking for such

Hello, Yes but how to activate this for all users, not on a per user basis or without writing out thousands of sieve files to users directories. Thank you. On 2017-06-15 13:33, Stephan Bosch wrote: > Op 6/15/2017 om 12:19 PM schreef Luescher Claude: >> I have +vnd.dovecot.duplicate plugin enabled but it seems to be >> ineffective. Any other tips for a workaround? >> >

I'm currently using maildrop to do delivery, because I like to use it's xfilter to pipe through spamc. I don't see a similar option for dovecot's deliver. Is there something? It would be nice to use deliver, since I use dovecot for reading mail.

sieve and managesieve are both working fine, have been for years. Now I want to add a sieve_after script: /etc/dovecot/conf.d/90-sieve.conf : plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_before = sieve_after = ~/sieve/personal.sieve sieve_subaddress_sep = + } I have compiled ~/sieve/personal.sieve to ~/sieve/personal.svbin, but it doesn't seem to be read. Any

Thanks to your help Steffen I was able to find out the issue which was simply the size of the Spam mail as you can see here: spamc[16545]: skipped message, greater than max message size (512000 bytes) The spam mail was around 900 kbytes as such I have changed the spamc limit to 1MB. Bastard spammer who abuses this limit by attaching a big image... Regards ML On Thursday, January 15, 2015

I just discovered that my spam filters are not being properly executed in CentOS 5.3 because when procmail attempts to invoke spamc. I have spamd running properly, and can invoke spamassassin and spamc from the bash prompt manually without any issues, however procmail fails with "permission denied" then bails. Watching the procmail.log I get the following: procmail: Executing

On 10/21/20 1:10 PM, @lbutlr wrote: > I have trace logs enabled for user scripts, but I think only error get logged for upper level, and only along the lines of "could not compile <name of sieve>". verify that you can compile the scripts manually, even as root then double-check your perms on your sieve/ dir, making sure that the write perms are correct for your dovecot

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 15 Jan 2015, ML mail wrote: It would be better to have the original question & discussion at the top, so one could cut and read nicely, > On Wednesday, January 14, 2015 9:06 PM, Pascal Volk <user+dovecot at localhost.localdomain.org> wrote: > On 01/14/2015 03:05 PM, ML mail wrote: > >> Hello, >> >> I am

Thank you for your helpful hints on debugging this issue. I wanted first to get the mail which generates this error but unfortunately the user already deleted it as well from his trash. Now I got another hint and it looks like this mail had a big attachment to it. Is it possible that spamc generated this error due to the size of the mail? Regards ML On Thursday, January 15, 2015 8:29 AM,

Hi Everyone, I have dovecot, postfix, roundcube and piegeonhole managesieve all working nicely together. Personal scripts defined in roundcube run without issue. I have configured the global sieve dir defined in 90-sieve.conf: sieve_global_dir = /var/lib/dovecot/sieve/global/ I pre-compiled the script in there: # ls -l /var/lib/dovecot/sieve/global/ total 8 -rw-r--r--. 1 root root 118 Sep 19