similar to: sieve_imapsieve centos 7

Displaying 20 results from an estimated 10000 matches similar to: "sieve_imapsieve centos 7"

2017 Feb 24
0
sieve_imapsieve centos 7
On 2017-02-24 23:16, Matthew Broadhead wrote: > i am using CentOS 7 centos-release-7-3.1611.el7.centos.x86_64 with > dovecot dovecot-2.2.10-7.el7.x86_64. i am trying to set up AntiSpam > with IMAPSieve but the package seems to be lacking sieve_imapsieve. is > there anything i can do? i am not really interested in compiling from > source because i like to receive security updates
2017 Feb 24
3
sieve_imapsieve centos 7
i am using CentOS 7 centos-release-7-3.1611.el7.centos.x86_64 with dovecot dovecot-2.2.10-7.el7.x86_64. i am trying to set up AntiSpam with IMAPSieve but the package seems to be lacking sieve_imapsieve. is there anything i can do? i am not really interested in compiling from source because i like to receive security updates automatically. 2017-02-24 21:57:00auth: Error:
2018 Jun 07
0
dovecot-pigeonhole Missing sieve_imapsieve Plugin?
On June 7, 2018 6:47:54 PM GMT+02:00, Will Foster <sadsfae at funcamp.net> wrote: >Hi Folks, > >I am having a problem configuring imapsieve via dovecot-pidgeonhole on >CentOS7. > >After following the docs here: > >https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve > >I get: > >dovecot[22026]: managesieve: Fatal: Plugin 'sieve_imapsieve'
2018 Jun 07
2
dovecot-pigeonhole Missing sieve_imapsieve Plugin?
Hi Folks, I am having a problem configuring imapsieve via dovecot-pidgeonhole on CentOS7. After following the docs here: https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve I get: dovecot[22026]: managesieve: Fatal: Plugin 'sieve_imapsieve' not found from directory /usr/lib64/dovecot/sieve dovecot[22026]: doveconf: Error: managesieve-login: dump-capability process returned 89
2017 Feb 10
5
Replacement for antispam plugin
On Fri, Feb 10, 2017 at 03:52:52PM +0100, Ralph Seichter wrote: >On 10.02.2017 09:06, Aki Tuomi wrote: > >> Since antispam plugin is deprecated and we would really prefer people >> not to use it, we wrote instructions on how to replace it with IMAPSieve. > >In my setup, I use the following sieve script globally for all users: > > if header :is "X-Spam-Flag"
2017 Nov 30
0
Plugin 'sieve_imapsieve' not found
Am Donnerstag, den 30.11.2017, 13:47 +0100 schrieb Christopher Satchell: > Hello, > > when Dovecot launches (and pretty much at any action afterwards) it > always throws following error: > > > managesieve: Fatal: Plugin 'sieve_imapsieve' not found from > > directory > > /usr/lib/dovecot/modules/sieve > > config: Error: managesieve-login:
2017 Mar 01
1
Replacement for antispam plugin
Some answers inline. Aki On 01.03.2017 00:42, Andy R wrote: > Greetings to the list :) > > > I've been meaning to ask a couple of questions about the imapsieve for > antispam. > > > Firstly, I guess that the example at the bottom of the page > "https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve" is > meant to link to the new example at >
2017 Feb 12
4
Replacement for antispam plugin
On Sun, Feb 12, 2017 at 3:52 PM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > On February 10, 2017 at 10:06 AM Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > > > > Hi! > > Since antispam plugin is deprecated and we would really prefer people > > not to use it, we wrote instructions on how to replace it with > > IMAPSieve. Comments and
2017 Nov 30
3
Plugin 'sieve_imapsieve' not found
Hello, when Dovecot launches (and pretty much at any action afterwards) it always throws following error: | managesieve: Fatal: Plugin 'sieve_imapsieve' not found from directory /usr/lib/dovecot/modules/sieve | config: Error: managesieve-login: dump-capability process returned 89 dovecot-sieve and dovecot-managesieved are both installed and the only plugin in the mentioned folder is
2018 Jan 03
1
Re: dovecot v2.3.0: imap segfault when sieve_extprograms_plugin.so called
pigeonhole 0.5.0 has been already released... ---Aki TuomiDovecot oy -------- Original message --------From: Daniel Kenzelmann <dovecot.org at k8n.de> Date: 03/01/2018 21:31 (GMT+02:00) To: Rhys Williams <lux+mailinglists at melted.me>, dovecot at dovecot.org Subject: Re: dovecot v2.3.0: imap segfault when sieve_extprograms_plugin.so ? called Hi, see the following thread:
2019 Nov 05
1
Trying to replace anti spam plugin with IMAPSieve; no joy
I?m trying to follow the instructions on the wiki to move from antispam to IMAPSieve, but it?s not working at all. A bit of a background: dovecot-core 2:2.3.8-4~buster dovecot-imapd 2:2.3.8-4~buster dovecot-lmtpd 2:2.3.8-4~buster dovecot-managesieved 2:2.3.8-4~buster dovecot-pgsql 2:2.3.8-4~buster dovecot-pop3d 2:2.3.8-4~buster
2016 Dec 05
1
imapsieve environment variables missing?
On 2016-12-05 15:26, Stephan Bosch wrote: > Op 12/6/2016 om 12:23 AM schreef MRob: >>>>>> I don't know how I managed to compile only using direct access of >>>>>> ${imap.user} before since now I get an unknown namespace error on >>>>>> my >>>>>> test script. >>>>>> >>>>>> But doing
2017 Feb 10
15
Replacement for antispam plugin
Hi! Since antispam plugin is deprecated and we would really prefer people not to use it, we wrote instructions on how to replace it with IMAPSieve. Comments and suggestions are most welcome. https://wiki.dovecot.org/HowTo/AntispamWithSieve --- Aki Tuomi Dovecot oy
2016 Dec 05
2
imapsieve environment variables missing?
>>>> I don't know how I managed to compile only using direct access of >>>> ${imap.user} before since now I get an unknown namespace error on my >>>> test script. >>>> >>>> But doing it this way compiles: >>>> >>>> require ["environment", "variables", "vnd.dovecot.debug"];
2017 Aug 22
2
imapsieve: failed to read mailbox attribute
On Tue, Aug 22, 2017 at 01:55:45PM +0300, Aki Tuomi wrote: > > >On 22.08.2017 13:37, Darac Marjal wrote: >> Hello all, >> >> Hopefully this is something fairly simple. >> >> I've been trying to set up the Sieve Antispam system as detailed at >> https://wiki2.dovecot.org/HowTo/AntispamWithSieve, but at the moment, >> whenever I change mailboxes
2017 Feb 28
0
Replacement for antispam plugin
Greetings to the list :) I've been meaning to ask a couple of questions about the imapsieve for antispam. Firstly, I guess that the example at the bottom of the page "https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve" is meant to link to the new example at "https://wiki2.dovecot.org/HowTo/AntispamWithSieve" now? Also... in "imapsieve_mailboxX_name
2018 Aug 14
2
imapsieve wrong matches on APPEND cause
Hi, > Can you enable mail_log plugin, try again, and send updated logs? > Aki Sure, but logs contain same info. 1. When I move a message from Inbox to Spam it matches both rules and sieve executing both scripts in sequence: Debug: Spam: Mailbox opened because: SELECT Debug: imapsieve: mailbox Spam: APPEND event Debug: sieve: Pigeonhole version 0.4.21 (92477967) initializing Debug: sieve:
2017 Dec 11
1
sieve problem config antispam
Hello, I like to configure the antispam with sieve from this site https:// wiki2.dovecot.org/HowTo/AntispamWithSieve#For_rspamd But when I compile the scripts I have this Errors sievec /usr/lib64/dovecot/sieve/report-ham.sieve report-ham: line 1: error: require command: unknown Sieve capability `vnd.dovecot.pipe'. report-ham: line 1: error: require command: unknown Sieve capability
2017 Sep 22
0
Fwd: Bug#876364: dovecot-sieve: Just discovered imap_sieve/sieve_imapsieve is not set up to work with virtual mailboxes.
Hi... The output of my doveconf -n is as folllows. # 2.2.32 (dfbe293d4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.20 (7cd71ba) doveconf: Warning: /etc/dovecot/dovecot.conf line 105: Global setting mail_plugins won't change the setting inside an earlier filter at /etc/dovecot/conf.d/15-lda.conf line 47 (if this is intentional, avoid this warning by moving the global setting before
2018 Nov 14
2
Trying to do antispam with Sieve
On 2018-11-14 13:51, Adi Pircalabu wrote: > On 2018-11-14 13:11, Adi Pircalabu wrote: >> Hi, >> >> Using https://wiki.dovecot.org/HowTo/AntispamWithSieve I'm trying to >> execute scripts when moving to/from Spam folder, however nothing's >> happening. The actions are: >> 1. Move to Spam: redirect :copy "spamcop_spam at domain.local";