similar to: imapsieve environment variables missing?

On 2016-12-05 04:38, Stephan Bosch wrote: > Op 5-12-2016 om 13:28 schreef MRob: >> RFC6785 says imap.user and imap.email environment variables should be >> made available but I can't access them no matter what I try. Are they >> not implemented because vnd.dovecot.environment already provides the >> username? (which does work for me) >> >> If

On 2016-12-05 06:13, Stephan Bosch wrote: > Op 5-12-2016 om 14:32 schreef MRob: >> On 2016-12-05 04:38, Stephan Bosch wrote: >>> Op 5-12-2016 om 13:28 schreef MRob: >>>> RFC6785 says imap.user and imap.email environment variables should >>>> be made available but I can't access them no matter what I try. Are >>>> they not implemented

On 2016-12-05 07:22, Stephan Bosch wrote: > Op 5-12-2016 om 16:10 schreef MRob: >> On 2016-12-05 06:13, Stephan Bosch wrote: >>> Op 5-12-2016 om 14:32 schreef MRob: >>> >>> Could you show me your full script? I am mainly interested in the >>> require statements involved. >> >> I don't know how I managed to compile only using direct

>>>> I don't know how I managed to compile only using direct access of >>>> ${imap.user} before since now I get an unknown namespace error on my >>>> test script. >>>> >>>> But doing it this way compiles: >>>> >>>> require ["environment", "variables", "vnd.dovecot.debug"];

On 2016-12-05 15:26, Stephan Bosch wrote: > Op 12/6/2016 om 12:23 AM schreef MRob: >>>>>> I don't know how I managed to compile only using direct access of >>>>>> ${imap.user} before since now I get an unknown namespace error on >>>>>> my >>>>>> test script. >>>>>> >>>>>> But doing

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

Op 4/7/2017 om 7:29 PM schreef MRob: > On 2017-04-05 18:50, MRob wrote: >> RFC 6785 says I should be able to run scripts when a command changes >> flags on a message but I can't understand what to put in >> imapsieve_mailboxXXX_causes. Dovecot logs something like STORE as an >> invalid cause. >> >> How do I run an administrator Sieve script caused from

Op 4/8/2017 om 10:08 AM schreef MRob: > On 2017-04-08 01:03, Stephan Bosch wrote: >> Op 4/7/2017 om 7:29 PM schreef MRob: >>> On 2017-04-05 18:50, MRob wrote: >>>> RFC 6785 says I should be able to run scripts when a command changes >>>> flags on a message but I can't understand what to put in >>>> imapsieve_mailboxXXX_causes. Dovecot logs

Op 12/5/2016 om 10:25 PM schreef MRob: > On 2016-12-05 07:22, Stephan Bosch wrote: >> Op 5-12-2016 om 16:10 schreef MRob: >>> On 2016-12-05 06:13, Stephan Bosch wrote: >>>> Op 5-12-2016 om 14:32 schreef MRob: >>>> >>>> Could you show me your full script? I am mainly interested in the >>>> require statements involved. >>>

Op 5-12-2016 om 14:32 schreef MRob: > On 2016-12-05 04:38, Stephan Bosch wrote: >> Op 5-12-2016 om 13:28 schreef MRob: >>> RFC6785 says imap.user and imap.email environment variables should >>> be made available but I can't access them no matter what I try. Are >>> they not implemented because vnd.dovecot.environment already >>> provides the

Op 5-12-2016 om 13:28 schreef MRob: > RFC6785 says imap.user and imap.email environment variables should be > made available but I can't access them no matter what I try. Are they > not implemented because vnd.dovecot.environment already provides the > username? (which does work for me) > > If imap.user and imap.email are there, can you provide an example how > to

RFC 6785 says I should be able to run scripts when a command changes flags on a message but I can't understand what to put in imapsieve_mailboxXXX_causes. Dovecot logs something like STORE as an invalid cause. How do I run an administrator Sieve script caused from change in flags?

Op 5-12-2016 om 16:10 schreef MRob: > On 2016-12-05 06:13, Stephan Bosch wrote: >> Op 5-12-2016 om 14:32 schreef MRob: >> >> Could you show me your full script? I am mainly interested in the >> require statements involved. > > I don't know how I managed to compile only using direct access of > ${imap.user} before since now I get an unknown namespace error

What is your configuration (output from `dovecot -n`)? Op 16/08/2018 om 14:01 schreef Leandro Lucarella: > 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

> On February 10, 2017 at 12:13 PM Ralph Seichter wrote: > > On 10.02.17 18:34, Michael Slusarz wrote: > > > Can we add an exception for the Trash folder? > > This is handled in the sieve script. E.g.: > > > > require "environment"; > > if environment "imap.mailbox" "Trash" { > > stop; > > } > > This does

Op 12/6/2016 om 12:23 AM schreef MRob: >>>>> I don't know how I managed to compile only using direct access of >>>>> ${imap.user} before since now I get an unknown namespace error on my >>>>> test script. >>>>> >>>>> But doing it this way compiles: >>>>> >>>>> require

Hello list I currently have an issue with an imapsieve script on my dovecot server CentOS Linux release 7.3.1611 (Core) Dovecot 2.2.26.0 (23d1de6) Pigeonhole 2.2.26.0 The goal is to "fire" an imapsieve script upon mailclient saves message to sent folder I setup the following in 90-plugin.conf: plugin { sieve_plugins = sieve_imapsieve sieve_extprograms sieve_extensions =

On 2018-11-14 13:51, Adi Pircalabu wrote: > On 2018-11-14 13:11, Adi Pircalabu wrote: >> Hi, >> >> Using https://wiki.dovecot.org/HowTo/AntispamWithSieve I'm trying to >> execute scripts when moving to/from Spam folder, however nothing's >> happening. The actions are: >> 1. Move to Spam: redirect :copy "spamcop_spam at domain.local";

Hi, Using https://wiki.dovecot.org/HowTo/AntispamWithSieve I'm trying to execute scripts when moving to/from Spam folder, however nothing's happening. The actions are: 1. Move to Spam: redirect :copy "spamcop_spam at domain.local"; 2. Move from Spam: redirect :copy "spamcop_ham at domain.local"; Here's the configuration I'm working with: doveconf: Warning:

On 2017-04-08 01:03, Stephan Bosch wrote: > Op 4/7/2017 om 7:29 PM schreef MRob: >> On 2017-04-05 18:50, MRob wrote: >>> RFC 6785 says I should be able to run scripts when a command changes >>> flags on a message but I can't understand what to put in >>> imapsieve_mailboxXXX_causes. Dovecot logs something like STORE as an >>> invalid cause.