search for: imap_siev

...with signal 15 (by pid=1 uid=0 code=kill) 2017-02-24 21:57:00managesieve: Fatal: Plugin 'sieve_imapsieve' not found from directory /usr/lib64/dovecot/sieve 2017-02-24 21:57:00config: Error: managesieve-login: dump-capability process returned 89 2017-02-24 21:57:05imap: Fatal: Plugin 'imap_sieve' not found from directory /usr/lib64/dovecot 2017-02-24 21:57:05imap: Fatal: Plugin 'imap_sieve' not found from directory /usr/lib64/dovecot 2017-02-24 21:57:08imap: Fatal: Plugin 'imap_sieve' not found from directory /usr/lib64/dovecot 2017-02-24 21:57:08imap: Fatal: Plugin...

Dear all, I just saw that a "new" plugin imap_sieve is available: https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve I configured everything using the plugin sieve. Was the plugin sieve just renamed to imap_sieve or is it completely different? Thanks a lot for explaining what had been changed here, I cannot find anything in the wiki....

...t; uid=0 code=kill) > 2017-02-24 21:57:00managesieve: Fatal: Plugin 'sieve_imapsieve' not > found from directory /usr/lib64/dovecot/sieve > 2017-02-24 21:57:00config: Error: managesieve-login: dump-capability > process returned 89 > 2017-02-24 21:57:05imap: Fatal: Plugin 'imap_sieve' not found from > directory /usr/lib64/dovecot > 2017-02-24 21:57:05imap: Fatal: Plugin 'imap_sieve' not found from > directory /usr/lib64/dovecot > 2017-02-24 21:57:08imap: Fatal: Plugin 'imap_sieve' not found from > directory /usr/lib64/dovecot > 2017-02-24...

...bug.log being an empty world-writeable file in /usr/lib/dovecot. >> >> Absolutely nothing happens. The file debug.log is not even touched. But when I remove retrain.sh >> there?s an error logged so up >> until then, *something* happens. >> >> After this I tried imap_sieve, following the wiki on dovecot.org, but again nothing happens. My >> imap.log says: >> Info: sieve: pipe action: piped message to program `retrain.sh? >> >> But again debug.log is untouched. >> >> I?m fresh out of ideas here. Any help would be most welcome. &g...

...: #!/bin/sh echo hi >> debug.log ...with debug.log being an empty world-writeable file in /usr/lib/dovecot. Absolutely nothing happens. The file debug.log is not even touched. But when I remove retrain.sh there?s an error logged so up until then, *something* happens. After this I tried imap_sieve, following the wiki on dovecot.org, but again nothing happens. My imap.log says: Info: sieve: pipe action: piped message to program `retrain.sh? But again debug.log is untouched. I?m fresh out of ideas here. Any help would be most welcome. I?m on Debian in virtual machine, Postfix delivering ma...

> On 21/09/2020 11:11 Bernardo Reino <reinob at bbmk.org> wrote: > > > On Mon, 21 Sep 2020, Ferenc wrote: > > > Thanks for your quick reply! I tried /tmp/debug.log, world-writeable, > > but no dice. > > > >> https://doc.dovecot.org/configuration_manual/howto/antispam_with_sieve > > > > I followed the setup here. I think it works up

...ood Angelou wrote: >> Package: dovecot-core >> Version: 1:2.2.32-2 >> >> I've just discovered a bug where the sieve plugin (especially IMAP) >> will not work with a virtual mailbox. I recently found this out when >> testing a virtual mailbox setup and I use imap_sieve for SPAM >> filtering so to lose that would be painful. >> >> This is what is reported in dovecot's debug log... >> >> Sep 21 10:53:01 imap(personal at othersider92.com): Panic: file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed:...

...have other necessary plugins per protocol, for example "imap_quota" which would be specifically for the imap protocol and which does not apply for the lmtp protocol. For this I need to specify that for the imap protocol I have: protocol imap { mail_plugins = quota imap_quota zlib imap_sieve mail_log notify } and for the lmtp protocol I have: protocol lmtp { mail_plugins = quota zlib fts fts_solr sieve } I did it according to the "extra fields" documentation and separated the name and key with /. My queries are correct but are not being applied to dovecot. Then in t...

On Mon, 21 Sep 2020, Ferenc wrote: > Thanks for your quick reply! I tried /tmp/debug.log, world-writeable, > but no dice. > >> https://doc.dovecot.org/configuration_manual/howto/antispam_with_sieve > > I followed the setup here. I think it works up until the external script > is called (pipe :copy "sa-learn-ham.sh"). That's why I tried echo hi >>

...to show it userdb { args = uid=vmail gid=vmail home=/var/mail/%d/%n driver = static } protocol lmtp { info_log_path = /var/log/dovecot-lmtp.log mail_plugins = " virtual" } protocol lda { mail_plugins = " sieve virtual" } protocol imap { mail_plugins = " virtual imap_sieve" } I hope this helps. On Thu, Sep 21, 2017 at 4:47 AM, Apollon Oikonomopoulos <apoikos at debian.org> wrote: > Control: tags -1 + moreinfo upstream > > [Forwarding this to the Dovecot mailing list, just in case someone can > help] > > Hi, > > Thanks for the re...

...y, hope you?re all well! We have a really strange bug with our dovecot setup. After weeks and month of debugging we?re finally reached the point when we ask you for help. Our basic setup is quite simple: a single dovecot 2.3.10 (0da0eff44) install on Debian 10 with LDAP as user/passdb and sieve, imap_sieve and mail_crypt as mail_plugins. For the mail_crypt we have a special rule which allows us to enable crypting for each user individually. See this line from dovecot-ldap.conf.ext: pass_attrs = userPassword=password,=userdb_mail_plugins=%{if;%{real_lport};eq;993;imap_sieve;} %{if;%{real_lport};eq...

...6 Thu 21 Sep , Thurgood Angelou wrote: > Package: dovecot-core > Version: 1:2.2.32-2 > > I've just discovered a bug where the sieve plugin (especially IMAP) > will not work with a virtual mailbox. I recently found this out when > testing a virtual mailbox setup and I use imap_sieve for SPAM > filtering so to lose that would be painful. > > This is what is reported in dovecot's debug log... > > Sep 21 10:53:01 imap(personal at othersider92.com): Panic: file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0)...

...inbox = yes location = prefix = separator = . } passdb { args = /run/dovecot2/passwd driver = passwd-file } plugin { fts = squat fts_autoindex = yes fts_autoindex_exclude = Junk fts_enforced = yes fts_squat = partial=4 full=10 imapsieve_mailbox1_before = file:/var/lib/dovecot/imap_sieve/report- spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/var/lib/dovecot/imap_sieve/report- ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * plugin = fts fts_squat quota...

...x2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_pipe_bin_dir = /usr/lib/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms } protocol imap { mail_plugins = " virtual imap_sieve" } Now, should I see the report-spam or report-ham sieve's logged anywhere? Because I am not seeing them.

Suddenly I am getting undefined symbol errors having updated to 2.3.7. Jul 18 01:02:49 localhost dovecot: indexer-worker: Error: User <someone> lookup failed: Couldn't load required plugin /usr/lib/dovecot/modules/lib95_imap_sieve_plugin.so: dlopen() failed: /usr/lib/dovecot/modules/lib95_imap_sieve_plugin.so: undefined symbol: command_hook_register (I think I fixed this one by a config change) But I am left with this: Jul 19 14:09:52 localhost dovecot: indexer-worker: Error: User <someone> lookup failed: Couldn...

Hi, If a user moves a mail to a Junk folder, this e-mail is going thru imap_sieve and ends up in sa-learn. I wrote some tools to immediately propagate that to the other node of the cluster as well as locally. Everything works fine, but sometimes I see a storm of requests hogging the CPU and I would like to collect some debugging information, Preferably I would like the permane...

.... > > I am not using lda but it seems to be part of core. So, as I am only using lmtp, why is pigeonhole using lda-sieve at all? It's part of lib-lda, which is also used by lmtp. > Can I work around the error message by some config magic (as I did by calling the correct plugin for imap_sieve) or is this an actual bug? Could this be fixed simply by including mail-deliver.h in lda-sieve-log.c? I think you're not linking lmtp binary correctly somehow. That symbol should be part of it: % nm /usr/libexec/dovecot/lmtp | grep mail_deliver_ctx_get_log_var_expand_table 0000000000061960...

Hi Stephan yes the imap_sieve plugin is added to the mail_plugins for imap. Thanks for the hint with mail_debug. After enabling it I can see that the program seems to be called, so filter should not be the problem. But the result is that the message appears unencrypted in my sent folder > Apr 6 08:20:26 mbox2 dovecot: ima...

...;/etc/pki/tls/certs/example.net.crt ssl_key = </etc/pki/tls/private/example.net.key userdb { driver = passwd } userdb { driver = passwd } protocol lmtp { mail_plugins = " sieve" } protocol lda { mail_plugins = " sieve" } protocol imap { mail_plugins = " imap_sieve" } ------------- Thanks for any guidance here. -- @sadsfae // gpg: A31F27E0 // irc: sadsfae come have a squat at https://hobo.house

...only reported once at first occurrence).report-ham: error: validation failed.sievec(root): Fatal: failed to compile sieve script 'sieve-scripts/report-ham.sieve' Yes, in conf.d/20-imap.conf, imapsieve and vnd.dovecot.pipe are explicitly enabled: protocol imap { mail_plugins = $mail_plugins imap_sieve imap_acl mail_max_userip_connections = 50 plugin {sieve_plugins = sieve_imapsieve sieve_extprograms # From elsewhere to Spam folder imapsieve_mailbox1_name = Spam imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_before = file:/etc/dovecot/sieve-scripts/report-spam.sieve # From Spam folder...