search for: multiscript

Hello Dovecot users, After about a month of silence, I finally release a new version of Pigeonhole Sieve. This release fixes problems in the multiscript support and improves the body extension further towards RFC compliance. The body extension still needs work, however, since some content types still give erroneous results. Changelog Sieve v0.1.13: + Body extension: implemented proper handling of the :raw transform and added various new...

Hello Dovecot users, After about a month of silence, I finally release a new version of Pigeonhole Sieve. This release fixes problems in the multiscript support and improves the body extension further towards RFC compliance. The body extension still needs work, however, since some content types still give erroneous results. Changelog Sieve v0.1.13: + Body extension: implemented proper handling of the :raw transform and added various new...

...in a sieve_before script. > > For more information: > > [1]: https://tools.ietf.org/html/rfc5228#section-4.3 [1] > [2]: https://tools.ietf.org/html/rfc5228#section-2.10.2 [2] > [3]: https://tools.ietf.org/html/rfc3894 [3] > [4]: http://tools.ietf.org/html/draft-degener-sieve-multiscript-00 [4] > > Regards, > > Stephan. Thanks Stephan, However still have one small issue: fileter.sieve ========== # rule:[amavis] if anyof (address :contains "From" "amavis", address :contains "Cc" "amavis-users at amavis.org", address :c...

...be placed > in a sieve_before script. > > For more information: > > [1]: https://tools.ietf.org/html/rfc5228#section-4.3 > [2]: https://tools.ietf.org/html/rfc5228#section-2.10.2 > [3]: https://tools.ietf.org/html/rfc3894 > [4]: http://tools.ietf.org/html/draft-degener-sieve-multiscript-00 > > Regards, > > Stephan. > Thanks Stephan, However still have one small issue: fileter.sieve ========== # rule:[amavis] if anyof (address :contains "From" "amavis", address :contains "Cc" "amavis-users at amavis.org", add...

...ot v2.2.21. Nothing changed since the RC. Changelog v0.4.12: + Implemented the Sieve extracttext extension (RFC 5703; Section 7). It is now possible to extract body text from a message into a variable. * Increased ABI version due to changes in the Sieve interpreter's object definitions. - multiscript: Fixed bug in handling of (implicit) keep; final keep action was always executed as though there was a failure. This caused the keep action to revert back to the initial message, causing editheader actions to be ignored. - managesieve-login: Fixed proxy to allow SASL mechanisms other than P...

...ot v2.2.21. Nothing changed since the RC. Changelog v0.4.12: + Implemented the Sieve extracttext extension (RFC 5703; Section 7). It is now possible to extract body text from a message into a variable. * Increased ABI version due to changes in the Sieve interpreter's object definitions. - multiscript: Fixed bug in handling of (implicit) keep; final keep action was always executed as though there was a failure. This caused the keep action to revert back to the initial message, causing editheader actions to be ignored. - managesieve-login: Fixed proxy to allow SASL mechanisms other than P...

...-spam. > > rules do have exactly one order, in which they appear in the Sieve script. > > But you certainly mean something different. Maybe a particular Sieve > front-end, that assembles the Sieve script together? > > See, http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration#multiscript > > There is one personal script the user may change and you can define one > or more scripts to be executed before or after the personal script. So, > if this would be pigeonhole problem, you define the spam processing in > an "after" global script and let have the user wh...

...ello Dovecot users, The recent release of Dovecot v1.2.15 is a good opportunity to release new versions of Sieve and ManageSieve for Dovecot v1.2. These releases consist entirely of bugfixes and introduce no new features. Changelog Sieve v0.1.18: - Imap4flags: fixed segfault bug occuring in multiscript context. Occured in specific situations when a script using imap4flags was followed in the sequence by scripts not using imap4flags. - Imap4flags: fixed bug in setflag command; when parameter was a stringlist, only the last item was actually set. - Prevented assertion failure d...

...ello Dovecot users, The recent release of Dovecot v1.2.15 is a good opportunity to release new versions of Sieve and ManageSieve for Dovecot v1.2. These releases consist entirely of bugfixes and introduce no new features. Changelog Sieve v0.1.18: - Imap4flags: fixed segfault bug occuring in multiscript context. Occured in specific situations when a script using imap4flags was followed in the sequence by scripts not using imap4flags. - Imap4flags: fixed bug in setflag command; when parameter was a stringlist, only the last item was actually set. - Prevented assertion failure d...

Hello, When new users are added we start them with a spam rule that routes spam to their junk folder. I don't see a way to assign priority ... so how does a user whitelist a spam-flagged email? Are the rules applied in some order? Alphabetically perhaps? If so I can name the spam rule z-spam. Thanks in advance.

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

...and >>>> without performing an explicit "keep" [2 >>>> <https://tools.ietf.org/html/rfc5228#section-2.10.2>] >>>> anywhere, the subsequent sieve_after scripts are not executed [4 >>>> <http://tools.ietf.org/html/draft-degener-sieve-multiscript-00>]. >>>> >>>> Therefore sieve_after is only useful to provide default behavior for >>>> when the user has no explicit rule for what should happen to the >>>> e-mail. >>>> >>>>> `/home/vpopmail/domains/medianetork.ro/por...

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

Hello Dovecot users, It has been about two months since the last release of the new Sieve implementation and the ManageSieve service for Dovecot v1.2. Therefore, this release contains quite a few changes. It adds new sieve features like the enotify extension and multiscript support. Also, quite a few (user-reported) bugs were fixed since the last release. Changelog Sieve v0.1.3: * Adapted to changes in Dovecot, making this release dependent on Dovecot >= 1.2.beta1 * Made mail address comparison fully case-insensitive. This is particularly noticea...

Hello Dovecot users, It has been about two months since the last release of the new Sieve implementation and the ManageSieve service for Dovecot v1.2. Therefore, this release contains quite a few changes. It adds new sieve features like the enotify extension and multiscript support. Also, quite a few (user-reported) bugs were fixed since the last release. Changelog Sieve v0.1.3: * Adapted to changes in Dovecot, making this release dependent on Dovecot >= 1.2.beta1 * Made mail address comparison fully case-insensitive. This is particularly noticea...

I'm looking for a way to set the \Seen flag on certain mail no matter what. Currently I'm using a global sieve script to do this. From what I've read, there is no way to enforce the global script if the user creates their own sieve script. More details: I have a postfix transport that along with sender_bcc_maps and recipient_bcc_maps uses deliver to create a read only archive of

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

...port for the Sieve extracttext extension. Changelog v0.4.12: + Implemented the Sieve extracttext extension (RFC 5703; Section 7). It is now possible to extract body text from a message into a variable. * Increased ABI version due to changes in the Sieve interpreter's object definitions. - multiscript: Fixed bug in handling of (implicit) keep; final keep action was always executed as though there was a failure. This caused the keep action to revert back to the initial message, causing editheader actions to be ignored. - managesieve-login: Fixed proxy to allow SASL mechanisms other than P...

Hello Dovecot users, Here's the definitive 0.4.17 release. There were no changes since the release candidate. Changelog v0.4.17: - LDA Sieve plugin: Fixed handling of an early explicit keep during multiscript execution. Action side-effects and the message snapshot would be lost at the final stage where the implicit keep is evaluated. This could result in the IMAP flags assigned to the message to be forgotten or that headers modified by the "editheader" extension would revert to their o...

...mailbox during a "COPY" event. This happens only after the Sieve script that is executed for the corresponding message in the destination mailbox finishes running successfully. + imapsieve plugin: Added non-standard Sieve environment items for the source and destination mailbox. - multiscript: The execution of the discard script had an implicit "keep", rather than an implicit "discard". The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.18.rc1.tar.gz http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2...