search for: extdata

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?...

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

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/...

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 >>> >&g...

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 Metada...

Andrew Beverley schreef op 17-8-2015 om 14:05: > 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'...

On Thu, 2015-08-06 at 09:49 +0200, Stephan Bosch wrote: > You have no debug symbols installed. Could you install dovecot-dbg > package and try again? Sorry, how's this: #0 sieve_validator_find_command_registration (valdtr=0xffffffff, command=0x7fc573c4bcd8 "extdata") at sieve-validator.c:309 No locals. #1 sieve_validator_register_command (valdtr=0xffffffff, ext=0x7fc5761b1280, cmd_def=0x7fc573e4c400 <tst_extdata>) at sieve-validator.c:331 cmd_reg = <optimized out> #2 0x00007fc573c4b4e6 in ext_extdata_validator_load (ext=0x7fc576...

Hi, On a new install-from-source with Dovecot 2.2.16rc1, Piegeonhole 0.4.6 and a grab of the newest Extdata code, I confirmed basic Sieve functionality is working (made a simple sieve script with a test on message subject resulting in a fileinto action). But I cannot get Sieve to see Extdata or Extprograms. sievec reports "Warning: sieve: ignored unknown extension 'vnd.dovecot.filter' while...

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, >...

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 lookup key for extdata?

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)? R...

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

...le) 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 created a directory in my package structure /Users/userName/myPackage/inst/extdata/ with subdirectories InputFiles and OutputFiles. And I put the example file (exampleData.csv) inside of the InputFiles subdirectory (/Users/userName/myPackage/inst/extdata/InputFiles). My vignette is located in: /Users/userName/myPackage/vignettes/myPackage.Rnw It contains the following syntax...

...>> 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 >> lookup key for extdata? > > You could override the %u variable, but overriding it in userdb will > have surprising consequences. Basically this amounts to same as &gt...

...ette tests in R CMD check is the installed version of the ?doc? subdirectory. Make sure all files needed by the vignette (data sets, . . . ) are accessible by either placing them in the ?inst/doc? hierarchy of the source package, or using calls to system.file(). So, I moved this file to inst/doc/extdata/tv.dat, and changed the vignette to <<tv1,results=verbatim>>= tv.data<-read.table(system.file("inst","doc","extdata","tv.dat",package="vcdExtra")) head(tv.data,5) @ But I get the error: Error: processing vignette 'vcd-tutorial....

...", which I'd guess comes from the fact that R tries to automatically read the file with read.table that should be read in a different way as specified in my .R-file). So I decided, following the advice in "Writing R extensions", to put these files into a directory called inst/extdata. The data directory now only has .R-files that read stuff from files in inst/extdata. This, unfortunately, doesn't seem to work. For example, kykladspecreg.R in data has one line reading kykladspecreg <- read.table(system.file("extdata","kykladspecreg.txt",package=&quot...

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

...onment 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 > lookup key for extdata? You could override the %u variable, but overriding it in userdb will have surprising consequences. Basically this amounts to same as changing username for the u...

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() failed: > /usr/lib/dovecot/sie...

What version of the extdata plugin are you using? This looks like a version built for Dovecot v2.1/Pigeonhole 0.3.0. Keep in mind that the extdata plugin is not part of the Pigeonhole distribution, so that will not be upgraded along with Pigeonhole. Since the extdata plugin is not part of the normal Debian packages (not...