similar to: IMAP and sieve

Hi list, Enabling plugins returns fatal errors like the following: Jan 16 00:28:11 norman dovecot: deliver(jman at zultron.com): Fatal: Plugin sieve_plugin not found from directory /usr/lib64/dovecot/lda Same errors for loading plugins in the "protocol imap" section of dovecot.conf (tested trash_plugin), same errors for loading other plugins (tested virtual_plugin), same

Hello, I have installed the dovecot-2.0.2 and dovecot-2.0-pigeonhole-0.2.0 but if I try to use sieve I get this error. I can't find any help in documentation. Any ideas? thanks ----------------------- /usr/local/sbin/dovecot start doveadm(root): Error: dlopen(/usr/local/lib/dovecot /lib90_sieve_plugin.so) failed: /usr/local/lib/dovecot/libdovecot-sieve.so.0: undefined symbol:

Greetings dovecot-mailing list! after upgrading from debian squeeze -> debian wheezy and therefore making the big dovecot jump from 1.x to 2.x we are stuck with one final(?) error that we can't get fixed. During login attempts the following is written to the logfiles. Error: dovecot: imap: Error: dlopen(/usr/lib/dovecot/modules/lib90_sieve_plugin.so) failed:

dovecot -n # 2.2.19: /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 (357ac0a0e68b+) # OS: FreeBSD 10.2-RELEASE-p7 amd64 doveconf: Warning: Dovecot was last started using /etc/dovecot/dovecot.conf, but this config is /usr/local/etc/dovecot/dovecot.conf auth_cache_size = 10 M auth_cache_ttl = 5 mins auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-userdb

I want to know what the best way to run sieve filters on already delivered mail is. Problem is that I have a rather large unfiltered mailbox and filtering it by hand would be a PITA. I don't mind coding something up to do this, but I just don't think that I'm the first one with this problem. Thanks - Axel

Hi, I'm currently restructuring my mail archives and migrated from a decade and a half old procmail supported solution to sieve. While doing so I often found that I'd like to filter a bunch of messages (with "bunch" in the area of 1-10K) with my shiny new sieve script. I found in the wiki a way to do that: http://wiki.dovecot.org/HowTo/RefilterMail And it works well, it picks

hi, I had two problems with deliver / sieve. First one is not reproducible anymore. Im using debian unstable (amd64), often dist-upgraded, with some experimental stuff too (wine i think). The first basically triggered a backtrace when confronted an email with spammassassins report headers prepended. (user_prefs: report_safe 0) However i dont have that backtrace anymore, sorry. The second

Running: dovecot revision 9333:15b4b2c904fe dovecot sieve revision: 1091:0fe00772366f AIX 5.3 64bit Deliver gives error: Aug 19 12:30:52 deliver(jsiegle): Error: dlopen(/usr/dovecot-1.2.4/lib/ dovecot/lda/lib90_sieve_plugin.so) failed: rtld: 0712-001 Symbol notify_command was referenced from module /usr/dovecot-1.2.4/lib/dovecot/lda/ lib90_sieve_plugin.so(), but a runtime

Hello, two days ago I've upgraded to 1.2rc2 and the new sieve implementation (version 0.1.4). Today I got the first mail that got stuck in the postfix queue because deliver was dying with a segfault. The mail is spam, thus I don't have any issues sharing it: http://users.birkenwald.de/~berni/temp/deliver-segfault.mail It happens with this small sieve script (my normal one is larger, but

Am building sieve plugin on AIX. This is revision 1095:8010f1eb66b3. I see the following error when doing the build: rm -fr .libs/lib90_sieve_plugin.lax^M mkdir .libs/lib90_sieve_plugin.lax^M rm -fr .libs/lib90_sieve_plugin.lax/libsieve.a^M mkdir .libs/lib90_sieve_plugin.lax/libsieve.a^M (cd .libs/lib90_sieve_plugin.lax/libsieve.a && ar x /usr/sadmin/src/

An email came to several users but one user didn't receive it and we got 'Mail delivery failed' message. As I see from the log below, there were broken index file. Then dovecot repaired that index and we got the error: Panic: file mail-index-sync-update.c: line 1013 (mail_index_sync_map): assertion failed: (map->hdr.indexid == index->indexid || map->hdr.indexid == 0) It was

Hello, The current version of LDA can crash (seg fault 11) under certain circumstances. I don't know why it happens only with some accounts, but here is a backtrace. The user has a sieve filter in place : (gdb) bt full #0 0x0000000800443434 in smtp_client_open () from /usr/lib/dovecot/libdovecot-lda.so.0 No symbol table info available. #1 0x00000008009943ab in

Hello, I'm trying to compile the sieve plugin for dovecot2 Dovecot2-beta6 is allready running and working. i did a hg clone http://hg.renamie-it.nl/dovecot-2.0-pigeonhole and ran the autogen.sh script as mentioned in the INSTALL file configure options: /configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc --with-dovecot=/usr/lib/dovecot/ --with-managesieve=no compiling gives an

Hi there! i installed and configured dovecot with management-sieve and sieve plugin ?on my server. I'm trying to apply filters to existing mail (not just the incoming one) but it doesn't work... Can i do it?? thanks!!! bye

I was wondering if anyone thought of applying filters to email post delivery, pre-read. Basically the idea would be to head off Spam, Malware or Phishing for already delivered email. Malware would probably be the least likely target, as (knock on wood) user workstations would be updated, but a targeted phishing scam would not create a public signature that would be downloaded, yet an

I did a mistake (shame on me). While migrating accounts on a new server, I didn't pay attention to a detail: sieve_max_actions, that I set to a low value for my testings, but then forgot to raise before the migration. As a result, several redirect-only accounts have now their inbox filled with messages that should have been redirected to "real people", then discarded. Would there

is there a way to process a mailbox through an existing sieve script as it the mail was being delivered anew? I?ve cleaned up a lot of my list-sorting scripts and I would like to process a bunch of mail again so it gets sorted properly. If I can do this could I also do it for a specific date range? For example, let?s say io want to reprocess all the messages that are in ?Archive? from between

Hi, After upgrading from dovecot 1.1 to dovecot 1.2.2 and the new sieve implementation (0.1.9), I'm having some strange problems. I'm including some general purpose scripts into my user script from sieve_global_dir. After some tests it seems that ths scripts get executed at random: sometimes the mail gets stored in the correct dir, and sometimes it goes to inbox. This also happens while

Hi Stephan Bosch, any update on this? Regards, T.B. Am 08.05.2014 um 14:37 schrieb Stephan Bosch: > T.B. schreef op 7-5-2014 10:40: >> I think it would not be a problem to develop a solution to remotely >> trigger re-filtering for me, myself and I. But that is not the point >> here. Clients like the Thunderbird Sieve Extension >> (https://github.com/thsmi/sieve,

On 07/10/2019 10:17, Demonhost via dovecot wrote: > Hi Stephan, > > Here it is: > We still can't reproduce it here. First of all, did you update Pigeonhole along with Dovecot? This kind of weirdness can happen when Pigeonhole was compiled against a different version of Dovecot. You could compile Pigeonhole manually as well to make sure, which also gives you the opportunity to