search for: myfilter

While setting up sieve on my email server I mistakenly setup a symlink (~/sieve/myfilter.svbin > ~/.dovecot.sieve) but I think that that should have been (~/sieve/myfilter.sieve > ~/.dovecot.sieve). I have fixed the mistake but dovecot/sieve still throws an error saying that the symlink still links to the wrong file. I have made sure the symlink is fixed (it links to ~/sieve...

...0:11:22:33:44:55'/>    <source bridge='virbr1'/>    <virtualport type='openvswitch'>         <parameters interfaceid='0529d6b5-627c-4330-803f-0d7018e6d496'/>    </virtualport>    <model type='virtio'/>    <filterref filter='myfilter'>       <parameter name='IP' value='10.10.10.99'/>    </filterref>    <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>  </interface> The filter 'myfilter' is defined. If I star...

...ugins = sieve_extprograms sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.filter +vnd.dovecot.execute sieve_pipe_bin_dir = /usr/local/bin/ sieve_filter_bin_dir = /usr/local/bin/ } .dovecot.sieve example: if address "to" "test at example.com" { filter "myfilter"; } This is all working without problems. Is there a possibility to allow users the execution of individual scripts in own homepath? Some people need to pipe mails to scripts for immediately processing (some ticketsystems need this). Is there a way to make this possible with sieve? Thanks...

After migrating to 0.9.1, I got: usr/local/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:123:in `const_missing'': uninitialized constant TokenFilter (NameError) Here is a snapshot of my code: ... require ''ferret'' class MyFilter < Analysis::TokenFilter ... I works fine on my dev machine, but not a production server (shared host). Any idea? -- Posted via http://www.ruby-forum.com/.

...tly appreciated. > > ~# grep sieve /var/log/syslog | nano temp.save > > Nov 23 01:32:09 1 dovecot: lda(steve at degga.net): Warning: sieve: file > storage: Active Sieve script symlink > /var/mail/vmail/degga.net/steve/.dovecot.sieve is broken: Invalid scriptname > (points to myfilter.svbin). ^^^ no mail here > > vmail at 1:/var/mail/vmail/degga.net/steve/mail$ ls -l -a ^^^ mail here > #redacted irrelevant stuff > lrwxrwxrwx 1 vmail vmail 14 Nov 23 02:43 .dovecot.sieve -> > myfil...

I want to set up a before_filter, and I want to be able to pass it some parameters. My method looks like def my_filter(a) ... end And I want to do before_filter :myfilter ''a'' I''ve tried the above and before_filter :myfilter, ''a'' but neither one is acceptable. How can I specify an argument to pass in to the filter method? Pat

...domain type='kvm' id='65'> <name>XXXX</name> <uuid>b602b5f2-b9d7-43bd-a949-acc7eeeb9f8f</uuid> <memory unit='KiB'>1048576</memory> <devices> <interface type='bridge'> <filterref filter='myfilter'> <parameter name='CTRL_IP_LEARNING' value='none'/> <parameter name='DHCPSERVER' value='104.156.226.10'/> <parameter name='IP' value='104.207.129.11'/> <parameter name='IP6_ADDR'...

Hello R users, I am trying to use R to do the low pass filter analysis for the tidal data. I am a novice in R and so far been doing only simple stuffs on R. I found a package called signal but couldn't find the proper tutorial for the low pass filter. Could anyone point me to the proper tutorial or starting point on how to do low pass filter analysis in R ? Thank you so much. Janesh

Hello, I am trying to make a heatmap in R and am having some trouble. I am very new to the world of R, but have been told that what I am trying to do should be possible. I want to make a heat map that looks like a gene expression heatmap (see http://en.wikipedia.org/wiki/Heat_map). I have 43 samples and 900 genes (yes I know this will be a huge map). I also have copy numbers associated with

...s = +vnd.dovecot.pipe +vnd.dovecot.filter > +vnd.dovecot.execute > sieve_pipe_bin_dir = /usr/local/bin/ > sieve_filter_bin_dir = /usr/local/bin/ > } > > .dovecot.sieve example: > > if address "to" "test at example.com" > { > filter "myfilter"; > } Uhh.. you're pointing extprograms to a directory where many programs can be installed by default. That is unwise to put it mildly. Do not allow Sieve to execute random programs like this. Typical use is to point it to a directory of scripts that check their arguments vigorously f...

...8YbkCBd9ye7Cvs Content-Type: text/x-pod; charset=utf-8 Content-Disposition: attachment; filename="nbdkit-filter.pod" Content-Transfer-Encoding: 8bit =encoding utf8 =head1 NAME nbdkit-filter - How to write nbdkit filters =head1 SYNOPSIS #include <nbdkit-filter.h> static int myfilter_config (nbdkit_next_config *next, void *nxdata, const char *key, const char *value) { if (strcmp (key, "myparameter") == 0) { // ... return 0; } else { // pass through to next filter or plugin return next (nxdata, key, value); } } sta...

...nbdkit-filter.pod b/docs/nbdkit-filter.pod new file mode 100644 index 0000000..75157ef --- /dev/null +++ b/docs/nbdkit-filter.pod @@ -0,0 +1,501 @@ +=encoding utf8 + +=head1 NAME + +nbdkit-filter - How to write nbdkit filters + +=head1 SYNOPSIS + + #include <nbdkit-filter.h> + + static int + myfilter_config (nbdkit_next_config *next, void *nxdata, + const char *key, const char *value) + { + if (strcmp (key, "myparameter") == 0) { + // ... + return 0; + } + else { + // pass through to next filter or plugin + return next (nxdata, key, value); + }...

...nbdkit-filter.pod b/docs/nbdkit-filter.pod new file mode 100644 index 0000000..cec60c6 --- /dev/null +++ b/docs/nbdkit-filter.pod @@ -0,0 +1,510 @@ +=encoding utf8 + +=head1 NAME + +nbdkit-filter - How to write nbdkit filters + +=head1 SYNOPSIS + + #include <nbdkit-filter.h> + + static int + myfilter_config (nbdkit_next_config *next, void *nxdata, + const char *key, const char *value) + { + if (strcmp (key, "myparameter") == 0) { + // ... + return 0; + } + else { + // pass through to next filter or plugin + return next (nxdata, key, value); + }...

This patch isn't complete (patch 6/6 isn't finished) so it's just for discussion, although it does compile and run. This introduces to nbdkit a concept of "filters" which can be placed in front of plugins to modify their behaviour. Some examples where you might use filters: * Serve a subset of the data, such as (offset, range) or a single partition from a disk image.

This is still tentative and needs a lot of work, but: - partition filter works, supporting MBR & GPT - prepare and finalize methods fixed - open method can now be changed (allowing readonly flag to be modified) - thread_model can be limited I believe I made most of the changes which were previously suggested in email. I think the only one I didn't was preventing inclusion of both

Rebased filters patch. Requires current git master + the locks / thread model fix (https://www.redhat.com/archives/libguestfs/2018-January/msg00128.html) So a few changes here since last time: The "introduce filters" and "implement filters" patches are squashed together. I introduced a concept of .prepare and .finalize. These run before and after the data serving phase

The first three patches are identical to: https://www.redhat.com/archives/libguestfs/2018-January/msg00079.html "[PATCH nbdkit v2 0/3] Refactor plugin_* functions into a backend" The rest of the patches add filters using the new filter API previously described here: https://www.redhat.com/archives/libguestfs/2018-January/msg00073.html This needs a lot more testing -- and tests --

A combination of the work that both Rich and I have been doing lately, where filters use only the new API with flags on every command that the client can send over the wire (we can then add support for more flags in nbdkit without having to add new callbacks, as NBD adds more flags upstream). Eric Blake (4): protocol: Split flags from cmd field in requests backend: Pass flags argument through