similar to: A few new Pigeonhole features

Op 14-4-2016 om 12:08 schreef Matthias Lay: > On Thu, 7 Apr 2016 15:44:04 +0200 > Stephan Bosch <stephan at rename-it.nl> wrote: > > >> - Recently, I implemented support for the "imapsieve" extension in >> Sieve and its IMAP counterpart (https://tools.ietf.org/html/rfc6785). >> This is now in the Pigeonhole master branch. This allows running >>

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

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

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

Hi Folks, I am having a problem configuring imapsieve via dovecot-pidgeonhole on CentOS7. After following the docs here: https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve I get: dovecot[22026]: managesieve: Fatal: Plugin 'sieve_imapsieve' not found from directory /usr/lib64/dovecot/sieve dovecot[22026]: doveconf: Error: managesieve-login: dump-capability process returned 89

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 access them so I can see what I did wrong?

On 16.10.2018 21.32, J. de Meijer wrote: > I'm still trying to fix this problem. Hopefully someone can help. > > I've upgraded dovecot to 2.3.3 > # dovecot --version > 2.3.3 (dcead646b) > > That didn't help. > > Next I switched 10-auth.conf to use a local password file (instead of LDAP) Can you provide doveconf -n please? Aki

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

Dear Dovecot and community, We run a small email service for our customers, based on two machines that are made ?redundant or clustered? by using the replication feature of Dovecot. This works well, for most emails. Sometimes the following happends: Email to our support database arrives at the inbox. Every period a cronjob looks into that mailbox and parses the information and makes a support

Hello Aki, I have this problem just with 2.3.8, my self-compiled 2.3.3 works fine. I have previously tried to update from 2.3.3 to higher versions (possibly 2.3.5 or so), but always had this error, which is why I am always back to 2.3.3. Configuration is exactly the same. Here my output from "doveconf -n": # 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf# Pigeonhole version 0.5.8

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

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 18.10.2018 21.24, J. de Meijer wrote: >> On 16.10.2018 21.32, J. de Meijer wrote: >>> I'm still trying to fix this problem. Hopefully someone can help. >>> >>> I've upgraded dovecot to 2.3.3 >>> # dovecot --version >>> 2.3.3 (dcead646b) >>> >>> That didn't help. >>> >>> Next I switched

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

Hello Dovecot users, It's been about 5 months since the last Pigeonhole release, so it is high time for a new one. However, the main reason to make a release now is the fact that Dovecot v2.2.15 has one change that causes problems with the previous release of Pigeonhole. Unlike recent earlier releases, this release has a few big new features. Most notably, I implemented a generic Sieve

Hello Dovecot users, It's been about 5 months since the last Pigeonhole release, so it is high time for a new one. However, the main reason to make a release now is the fact that Dovecot v2.2.15 has one change that causes problems with the previous release of Pigeonhole. Unlike recent earlier releases, this release has a few big new features. Most notably, I implemented a generic Sieve

Hello List, first thanks for previous hints, you helped me a lot. Unfortunately i have new problem with sieve and executing multiple scripts sequentially. This is current conf which is complete working : #CONF1 plugin { sieve = ~/sieve/.dovecot.sieve sieve_plugins = sieve_extprograms sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.filter +vnd.dovecot.execute +editheader

Op 11/6/2016 om 5:39 PM schreef Larry Rosenman: > ok, I found: > https://github.com/dovecot/pigeonhole/blob/master/doc/plugins/imapsieve.txt > and that helps. > > Can this be added to the Wiki? Yes: http://wiki.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve > > On Sun, Nov 6, 2016 at 10:30 AM, Larry Rosenman <larryrtx at gmail.com> wrote: > >> How do you

Hello, I wonder how to configure IMAPSieve with user scripts. I can't find much information on the internet. I have Sieve and IMAPSieve for spam configured as described in the wiki and it works. Documentation mentions that imapsieve_url has to be set to appropriate ManageSieve server but no further explanation is given. What I want to achieve: let users create their own sieve scripts and

Hello Dovecot users, It's been a few months since the last Pigeonhole release. The main reason is that I've introduced a few big new features. Although the new features themselves probably haven't seen much testing so far, I'm now pretty confident that existing configurations are not broken by these changes. The biggest change is the addition of dict support for Sieve script