similar to: Sieve can't find Extprograms or Extdata

Also, of course I have entered this in 90-plugins.conf plugin { seive_plugins = sieve_extdata sieve_extprograms sieve_extensions = +vnd.dovecot.filter +vnd.dovecot.extdata } And enabled sieve for lmtp (as I noted, I have tested that simple sieve scripting is working OK) protocol lmtp { mail_plugins = " sieve" } > On a new install-from-source with Dovecot 2.2.16rc1, >

Am 08.03.2015 um 09:08 schrieb E.B.: > Also, of course I have entered this in 90-plugins.conf > > plugin { > seive_plugins = sieve_extdata sieve_extprograms > maybe you have a typo... seive != sieve

Hi, I wonder if someone could give me a little help bringing the sieve-extdata plugin up to date to be usable with latest Dovecot/pigeonhole Trying to use both together at present I get an error: ? managesieve: Fatal: Couldn't load required plugin /usr/lib/dovecot/sieve/lib90_sieve_extdata_plugin.so: dlopen() failed: /usr/lib/dovecot/sieve/lib90_sieve_extdata_plugin.so: undefined symbol:

Hi Ed, On 18/09/2020 23:37, Ed W wrote: > Hi, I wonder if someone could give me a little help bringing the > sieve-extdata plugin up to date to be usable with latest Dovecot/pigeonhole > > Trying to use both together at present I get an error: > > ? managesieve: Fatal: Couldn't load required plugin > /usr/lib/dovecot/sieve/lib90_sieve_extdata_plugin.so: dlopen()

Hello, I want to install Dovecot Pigeonhole and use the Extdata and Extprograms plugins. According to the dovecot documentation[1,2], those plugins need to be compiled. So two questions: * Are either of these plugins built into the Pigeonhole that is available in the CentOS 7 extras repo? * Is it possible to use these plugins with Pigeonhole installed from yum? Does the compilation

Hello, I want to install Dovecot Pigeonhole and use the Extdata and Extprograms plugins on CentOS 7. I prefer to install software via yum, and a reasonably new version of Dovecot is available in the CentOS repo. But according to the dovecot documentation, these plugins need to be compiled, so I don't know if yum is out of the question? * Does anyone know if either of these plugins built

thanks you AKi for alway responding! >> Pigeonhole download page has links for extdata plugin up to v0.4 but >> nothing more and no link to the master repository >> >> https://pigeonhole.dovecot.org/download.html >> >> I want to use with dovecot 2.3.2rc1 but v0.4 won't compile with it. > > Seems to need v0.5 for it. What are you using it for? For a

Are the dovecot environment variables mutable? I'd like to override like: set "${env.vnd.dovecot.username}" "someuser at example.org" Or better, I prefer to override %u Dovecot variable during the userdb lookup. Is either possible? PS, when Sieve does extdata lookups for username key, where does username come from? %u? Does an override as above change the dict

Hi, I'd like to ask about status of extdata plugin for sieve. The wiki page (http://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/Extdata) mentions versions for PigeonHole 0.2 and 0.3, but there seems to be no version for 0.4 and Dovecot 2.2. Is the plugin dead or is it planned to make version for Dovecot 2.2 (when time allows I guess)? Regards J.

Pigeonhole download page has links for extdata plugin up to v0.4 but nothing more and no link to the master repository https://pigeonhole.dovecot.org/download.html I want to use with dovecot 2.3.2rc1 but v0.4 won't compile with it. Thanks for helping ------------------------------------------------- ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's

On 2018-03-19 06:31, Aki Tuomi wrote: > On 19.03.2018 06:40, MRob wrote: >> Are the dovecot environment variables mutable? I'd like to override >> like: >> >> set "${env.vnd.dovecot.username}" "someuser at example.org" >> >> Or better, I prefer to override %u Dovecot variable during the userdb >> lookup. >> >> Is

Good day to everyone Currently, I'm trying to implement the sieve "vacation" plugin with the sieve "Extdata" plugin to lookup information from a MySQL remote server. I'm following the instructions in the documentation: https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/Extdata ===== I have the following error === Apr 09 13:46:51 mail dovecot[5512]: dict: Error:

I am looking at porting and generalizing an old in-house patch that I'm using for the CMU Sieve plugin. It allows sieve script to test & lookup arguments from LDAP. Before getting too involved in this, I'd like to discuss my goals here in the hopes that someone else also thinks this would be useful. Many heads may make better design? Goal: ------ Allows scripts which are still

Hello (Stephan?), is this planned? Have to abandon dovecot 2.3.2 if extdata not available. > thanks you AKi for alway responding! > >>> Pigeonhole download page has links for extdata plugin up to v0.4 but >>> nothing more and no link to the master repository >>> >>> https://pigeonhole.dovecot.org/download.html >>> >>> I want to use

I've tried to use sieve-filter for my inbox (~6000 messages). It failed after some work with this backtrace: sieve-filter(kas): Error: socketpair() failed: Too many open files sieve-filter(kas): Panic: file script-client-local.c: line 155 (script_client_local_disconnect): assertion failed: (pid >= 0) sieve-filter(kas): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x66a71)

On Thu, 2015-08-06 at 16:10 +0200, Stephan Bosch wrote: > Since the extdata plugin is not part of the normal Debian packages (not > afaik anyway), you likely compiled and installed the extdata plugin > manually in the past while using Dovecot 2.1. Do that again, but use > this repository: http://hg.rename-it.nl/pigeonhole-0.4-sieve-extdata/ I'm just trying to install this now,

dir("inst/extdata/") dir("./inst/extdata/") dir("inst/extdata") works all fine, listing the directory content. but: unzip(tmp[1],exdir = "inst/extdata/") Error in unzip(tmp[1], exdir = "inst/extdata/") : 'exdir' does not exist unzip(tmp[1],exdir = "./inst/extdata/") Error in unzip(tmp[1], exdir = "inst/extdata/") :

On 3/10/2015 8:11 PM, E.B. wrote: >> Last time I had a few stupid problems in the releases, so >> I'll follow >> Timo's example and I release an RC first. >> >> The highlights include the implementation of the index and >> metadata >> extensions. Quite a few bugs are fixed as well. > When I compiled and installed this, Sieve scripts were being

I'm putting together an R package. I would like to show example code in the vignette, where example data files (included in the package) are used to generate an (example) output file. I read about using example data in Hadley Wickham's post ( http://r-pkgs.had.co.nz/data.html), and believe I should keep my example data as raw data, as it must be parsed to generate the output. So, I

On 19.03.2018 06:40, MRob wrote: > Are the dovecot environment variables mutable? I'd like to override like: > > set "${env.vnd.dovecot.username}" "someuser at example.org" > > Or better, I prefer to override %u Dovecot variable during the userdb > lookup. > > Is either possible? > > PS, when Sieve does extdata lookups for username key, where