similar to: Extdata plugin, MySQL

I'll try and break up my questions the other day about extdata that went unanswered into pieces in the hopes it will be more specific and clear. In general, I am trying to figure out the syntax of the map statement and what is allowed in that statement. So, by map statement, I mean for example perhaps the?dovecot-dict-expire.conf.ext file as shown in the doc. Is the syntax the same for the

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

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()

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

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:

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

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

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

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

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

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

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

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 22.06.2018 22:06, tai74 at vfemail.net wrote: > 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 > > >

While trying to isolate properly and reproduce, I was able to trigger the same bug with the following code: struct dict *dict; char* dict_uri = "proxy::sieve"; char* key = "priv/key"; char* username = "admin at domain.tld"; char* value, error; dict_drivers_register_builtin(); dict_init(dict_uri, DICT_DATA_TYPE_STRING, username,

Hi! This does sound like a bug, we'll have look. Aki On 17.10.2016 01:26, Pierre Jaury wrote: > I dived a little bit further into the rabbit hole, up to the point where > debugging has become unpracticle but I still haven't found the root > cause for sure. > > I read most of the code for "p_strdup" based on datastack memory pools > (which are used for

Hi, I noticed that dovecot's MySQL driver doesn't play well with UTF-8 encoded strings. I presume this issue has been around for a while. However, it still fails with the current release candidate 2.2.16-rc1. I have been using the sieve extdata plugin with a MySQL-backed dict to retrieve a folder name that is then passed to fileinto: fileinto :create

Oh duh, it used datastack pool. Try again with the attached patch? Please remember to clear the previous one out before trying. Aki > > The trace is missing some symbols, I will debug tomorrow and see where > the call comes from exactly. > > Regards, > > > On 10/17/2016 06:23 PM, Aki Tuomi wrote: > > Hi! > > > > Looking at the code, I think the bug

Hello, I am using a dict proxy for my sieve extdata plugin to access some fields from an SQLite database (autoreply text and other database-configured items). All tests are performed against version 2.2.25. $ dovecot --version 2.2.25 (7be1766) My configuration looks like: dict { sieve = sqlite:/etc/dovecot/pigeonhole-sieve.dict } [...] sieve_extdata_dict_uri = proxy::sieve I