Re: Replacing antispam plugin with IMAPSieve not 100% correct?

On 2022-09-25 14:35, Christian Kivalo wrote: On September 25, 2022 1:27:23 PM GMT+02:00, Marc wrote: I think this page[1] is not correct If you configure this option: imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve the file report-spam.svbin cannot be created

Re: Replacing antispam plugin with IMAPSieve not 100% correct?

On September 25, 2022 1:27:23 PM GMT+02:00, Marc wrote: > >I think this page[1] is not correct > >If you configure this option: > >imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve > >the file report-spam.svbin cannot be created because users cannot write there. You

Replacing antispam plugin with IMAPSieve not 100% correct?

I think this page[1] is not correct If you configure this option: imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve the file report-spam.svbin cannot be created because users cannot write there. [1]

Re: Antispam plugin

Den 17.01.2021 02:15, skrev Toni Mueller: Hi, On Tue, Sep 22, 2020 at 02:01:21PM +0300, Aki Tuomi wrote: You don't need antispam plugin: https://doc.dovecot.org/configuration_manual/howto/antispam_with_sieve/ I also don't see any docs about the plugin on the wiki. Does it mean

Re: Antispam plugin

Hi, On Tue, Sep 22, 2020 at 02:01:21PM +0300, Aki Tuomi wrote: > You don't need antispam plugin: > > https://doc.dovecot.org/configuration_manual/howto/antispam_with_sieve/ I also don't see any docs about the plugin on the wiki. Does it mean that this plugin is deprecated? Thanks, Toni

antispam plugin again

Hello I have a problem with migrating dovecot from 2.2.36 to 2.3.8 - everything works fine, but a problem with migrating anti-spam plugins New dovecot 2.3.x has implemented own antispam-plugin like: new from dovecot 2.3.8 - # From elsewhere to Spam folder   imapsieve_mailbox1_name

Re: Antispam plugin

> >  I need "Antispam plugin". What antispam-plugin I must use ? > > In older version dovecot-2.2.36.4 i use "dovecot-antispam-plugin" but in > centos I had a problem with configure  - probably toold wersion > > "./configure: line 3193: DC_DOVECO

Antispam plugin

Hi System centos8 + dovecot-2.3.8 from repo # 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.8 (b7b03ba2) # OS: Linux 4.18.0-193.19.1.el8_2.x86_64 x86_64 CentOS Linux release 8.2.2004 (Core)  I need "Antispam plugin". What antispam-plugin I must use ? In old

Re: Dovecot With DSpam AntiSpam Plugin Replacement With Sieve

Thank you for this. I have a DSPAM setup that did work with the suggested scrips, but I used the old dovecot antispam plugin and enjoyed the signature method. I am going to try this out next week to see if it works for me. If it does, I will love this. Thanks again. Trever On 02/24/2018 02:02 PM

Dovecot With DSpam AntiSpam Plugin Replacement With Sieve

it to Dovecot 2.2.33.2 with PigeonHole 4.21, it runs DSpam 3.10.2 to scan and tag all incoming mails as Spam or not then a Sieve rule to put the Spam emails into the Spam folder, I was also using the DSpam Antispam plugin to enable moving messages from one folder to another to teach failures to DSpam

Re: antispam plugin with IMAPSieve

Op 31-10-2017 om 15:33 schreef j.emerlik: Hi, my dovecot is configured with IMAP Sieve antispam plugin (sa-learn), everything seems to be working correctly but in debug mode in my log file I noticed "dovecot: imap: Error". Last 14 lines od my log file: Oct 31 15:05:25 mnode1 dov

antispam plugin with IMAPSieve

Hi, my dovecot is configured with IMAP Sieve antispam plugin (sa-learn), everything seems to be working correctly but in debug mode in my log file I noticed "dovecot: imap: Error". Last 14 lines od my log file: Oct 31 15:05:25 mnode1 dovecot: imap: Error: Oct 31 15:05:25.040 [10743]

Re: Replacement for antispam plugin

On Wed Mar 01 2017 03:11:48 GMT-0500 (Eastern Standard Time), Aki Tuomi wrote: >> But, if the imapsieve is only matching to literal foldernames, should >> I just duplicate the trigger lines for each type of junk folder or is >> there a method to have the sieve script

Re: Replacement for antispam plugin

ipt enumerate all the options > listed by 'special use' or is there a better method for this? I want > to put the spam-mail-filing script as a global sieve script as all > users will need it, rather than duplicating out for each user. > There is no way to match special use folders at

Re: Replacement for antispam plugin

thanks , Andy R On 10/02/2017 09:06, Aki Tuomi 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 suggestions are most welcome. https://wiki.dovecot.org/HowTo/AntispamWithSieve --- Aki Tuomi Dovecot oy

Re: Replacement for antispam plugin

..@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 suggestions are most welcome. https://wiki.dovecot.org/HowTo/AntispamWithSieve --- Aki Tuomi Dovecot oy Hi everyo

Re: Replacement for antispam plugin

; For DSPAM, with --client, one also needs a --user set. http://hg.dovecot.org/dovecot-antispam-plugin/file/5ebc6aae4d7c/src/dspam.c did this. Is there a way to feed this into the scripts mentioned? I imagine this is imap.user or imap.email, but how would one pass it to the script? Thank you.

Re: Replacement for antispam plugin

Den 12. feb. 2017 23:56, skrev Marcus Rueckert: > On 2017-02-12 23:00:49 +0100, Håkon Alstadheim wrote: >> Just follow the wiki and replace sa-learn scripts with calling dspam. >> Dspam direct pipe needs mail-line-endings (\r\n) translated into unix >> line-endings (\r). I had a typo here,

Re: Replacement for antispam plugin

Op 2/12/2017 om 11:00 PM schreef Håkon Alstadheim: > > Den 12. feb. 2017 21:44, skrev ebr...@whitehorsetc.com: >> >> Any opinion on dspam's interoperability with this? >> >> > Just follow the wiki and replace sa-learn scripts with calling dspam. > Dspam direct pipe needs mail-line-endings (\r\n)

Re: Replacement for antispam plugin

On 2017-02-12 23:00:49 +0100, Håkon Alstadheim wrote: > Just follow the wiki and replace sa-learn scripts with calling dspam. > Dspam direct pipe needs mail-line-endings (\r\n) translated into unix > line-endings (\r). tbh ... what do you do about mails which just use \r as separator? s|\r\n|\n|

Re: Replacement for antispam plugin

Den 12. feb. 2017 21:44, skrev ebr...@whitehorsetc.com: > > > Any opinion on dspam's interoperability with this? > > Just follow the wiki and replace sa-learn scripts with calling dspam. Dspam direct pipe needs mail-line-endings (\r\n) translated into unix line-endings (\r). like so:

Re: Replacement for antispam plugin

Den 12. feb. 2017 15:12, skrev Ralph Seichter: > On 12.02.2017 13:25, Stephan Bosch wrote: > >> The "imap.mailbox" environment is the empty string in this case. Why? >> Well, the Sieve interpreter does not know about it, since the >> "imapsieve" extension is not activated in the require line. >

Re: Replacement for antispam plugin

Any opinion on dspam's interoperability with this? On Fri, Feb 10, 2017 at 1:07 AM -0700, "Aki Tuomi" <aki.tu...@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 i

Re: Replacement for antispam plugin

Aki Tuomi <aki.tu...@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

Re: Replacement for antispam plugin

On 12.02.17 19:05, George Kontostanos wrote: > Actually I think that sa-learn is invoked as user vmail. But of course > I might be wrong. It might depend on system configuration. On my servers, Sieve scripts are definitely executed as the OS user that matches the current IMAP user. > Do you

Re: Replacement for antispam plugin

Op 2/12/2017 om 5:36 PM schreef George Kontostanos: > On Sun, Feb 12, 2017 at 3:52 PM, Aki Tuomi <aki.tu...@dovecot.fi> wrote: > >>> On February 10, 2017 at 10:06 AM Aki Tuomi <aki.tu...@dovecot.fi> wrote: >>> >>> >>> Hi! >>> Since

Re: Replacement for antispam plugin

On Sun, Feb 12, 2017 at 7:52 PM, Ralph Seichter wrote: > On 12.02.2017 17:36, George Kontostanos wrote: > >> it automatically creates a .spamassassin/ folder in the user > > That happens because sa-learn is invoked as the user who is logged into > IMAP. If you want all

Re: Replacement for antispam plugin

On 12.02.2017 17:36, George Kontostanos wrote: > it automatically creates a .spamassassin/ folder in the user That happens because sa-learn is invoked as the user who is logged into IMAP. If you want all users to contribute to a global SpamAssassin database (like I do), you'll need to create

Re: Replacement for antispam plugin

On Sun, Feb 12, 2017 at 3:52 PM, Aki Tuomi <aki.tu...@dovecot.fi> wrote: > > > On February 10, 2017 at 10:06 AM Aki Tuomi <aki.tu...@dovecot.fi> wrote: > > > > > > Hi! > > Since antispam plugin is deprecated and we would really prefer people &g

Re: Replacement for antispam plugin

On 12.02.2017 13:25, Stephan Bosch wrote: > The "imap.mailbox" environment is the empty string in this case. Why? > Well, the Sieve interpreter does not know about it, since the > "imapsieve" extension is not activated in the require line. Now there's a facepalm moment. ;-) Thank you, with a

Re: Replacement for antispam plugin

> On February 10, 2017 at 10:06 AM Aki Tuomi <aki.tu...@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 suggestions a

Re: Replacement for antispam plugin

Op 2/10/2017 om 10:15 PM schreef George Kontostanos: > On Fri, Feb 10, 2017 at 9:59 PM, Ralph Seichter > wrote: > > > Same problem here. As a workaround I tried the following: > > # From Spam folder to Inbox > imapsieve_mailbox2_name = Inbox > imapsieve_mailbox2_from =

Re: Replacement for antispam plugin

Op 2/10/2017 om 8:59 PM schreef Ralph Seichter: > On 10.02.17 20:34, Michael Slusarz wrote: > >> When you move a message to a new mailbox, that is a "new message" >> event (a new UID in the target mailbox is created; the message count >> increases). So imap.mailbox is set to the name of the

Re: antispam plugin pipe backend error when moving multiple emails

bumping this because it still occurs with dovecot 2.2.22. my dovecot-antispam plugin configuration : antispam_allow_append_to_spam = no antispam_backend = pipe antispam_pipe_program = /usr/bin/rspamc antispam_pipe_program_args = -h;127.0.0.1:11334;-P

Re: Replacement for antispam plugin

Op 2/10/2017 om 8:46 PM schreef David Mehler: > Hello, > > Chiming in on this with a question, and will be getting to it over the > weekend or later this evening time permitting. > > Does retraining a message as either spam or ham alter message headers > for example x-spam or the

Re: Replacement for antispam plugin

> On February 12, 2017 at 1:32 PM Stephan Bosch <step...@rename-it.nl> wrote: > > > Op 2/10/2017 om 2:20 PM schreef Alessio Cecchi: > > Il 10/02/2017 09:06, Aki Tuomi ha scritto: > >> Hi! > >> Since antispam plugin is deprecated and we would really

Re: Replacement for antispam plugin

Op 2/10/2017 om 2:20 PM schreef Alessio Cecchi: > Il 10/02/2017 09:06, Aki Tuomi ha scritto: >> 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 s

Re: Replacement for antispam plugin

On Fri, Feb 10, 2017 at 9:59 PM, Ralph Seichter wrote: > On 10.02.17 20:34, Michael Slusarz wrote: > > > When you move a message to a new mailbox, that is a "new message" > > event (a new UID in the target mailbox is created; the message count > > increases). So

Re: Replacement for antispam plugin

On 10.02.17 20:34, Michael Slusarz wrote: > When you move a message to a new mailbox, that is a "new message" > event (a new UID in the target mailbox is created; the message count > increases). So imap.mailbox is set to the name of the *target* mailbox. My tests seem to indicate otherwise.

Re: Replacement for antispam plugin

Hello, Chiming in on this with a question, and will be getting to it over the weekend or later this evening time permitting. Does retraining a message as either spam or ham alter message headers for example x-spam or the spamassassin-modified subject header? If not is it possible to do so after

Re: Replacement for antispam plugin

> On February 10, 2017 at 12:13 PM Ralph Seichter wrote: > > On 10.02.17 18:34, Michael Slusarz wrote: > > > Can we add an exception for the Trash folder? > > This is handled in the sieve script. E.g.: > > > > require "environment"; > > if environment "imap.mailbox" "Trash" { > > stop; > > } >

Re: Replacement for antispam plugin

On 10.02.17 18:34, Michael Slusarz wrote: > > Can we add an exception for the Trash folder? > > This is handled in the sieve script. E.g.: > > require "environment"; > if environment "imap.mailbox" "Trash" { > stop; > } This does not work for me, and I don't really expect it to work either.

Re: Replacement for antispam plugin

On 10.02.17 18:22, Zhang Huangbin wrote: > My concern is, will you experience any lag while moving message? I don't use direct calls to sa-learn, but store the piped e-mails on disk, and a periodic cron-job picks them up and invokes sa-learn. This way, there is no noticeable lag. -Ralph

Re: Replacement for antispam plugin

> On February 10, 2017 at 9:25 AM George Kontostanos > wrote: [snip] > I think that this needs some change: > > # From Spam folder to elsewhere > imapsieve_mailbox2_name = * > imapsieve_mailbox2_from = Spam > imapsieve_mailbox2_causes = COPY >

Re: Replacement for antispam plugin

backend of old “antispam” plugin, when you move a message from INBOX to Junk, the antispam plugin calls sa-learn, and you will experience noticeable lag on webmail (i used Roundcube webmail for testing) until sa-learn finished. It's much worse if you move multiple emails at the same time, because

Re: Replacement for antispam plugin

On 10.02.2017 16:09, Darac Marjal wrote: > Check out https://wiki.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve, > which explains that sieve is normally only used at delivery time, but > the sieve_imapsieve plugin runs a *different* sieve script based on > IMAP actions (for example, COPY).

Re: Replacement for antispam plugin

gt;>> 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 u

Re: Replacement for antispam plugin

On Fri, Feb 10, 2017 at 5:09 PM, Darac Marjal <mailingl...@darac.org.uk> wrote: > 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 peop

Re: 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

Re: Replacement for antispam plugin

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

Re: Replacement for antispam plugin

Il 10/02/2017 09:06, Aki Tuomi ha scritto: 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 Hi

Re: Replacement for antispam plugin

Aki Tuomi wrote on 10.02.2017 15:06: 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

Re: Replacement for antispam plugin

Nice. Finally got around to switching. Had to add filter to my dspam pipe (another one I'm overdue for replacing) . Antispam plugin seems to have automatically converted line endings from "mail-type" '\r\n' into linux plain '\n' . Like so: sed -e 's/\r$//' | dspam ... Den 10. feb.

Re: Replacement for antispam plugin

On 10.02.2017 10:35, Tom Hendrikx wrote: > > On 10-02-17 09:06, Aki Tuomi 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 suggestions

Re: Replacement for antispam plugin

On 10-02-17 09:06, Aki Tuomi 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 suggestions are most welcome. > > https://wiki.dovecot.org/HowTo

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

Re: Antispam plugin: insufficent error messages

is found. This wasn't > the behavior in 2.2.24, though I'm not sure if it was in .25 or .26. > I haven't tracked down the details further. > > Anyway, the antispam plugin uses this API to find the X-DSPAM-Signature > header, and the change causes the plugin to abort. This happens in the > pl

Re: Antispam plugin: insufficent error messages

is wasn't > the behavior in 2.2.24, though I'm not sure if it was in .25 or .26. > I haven't tracked down the details further. > > Anyway, the antispam plugin uses this API to find the X-DSPAM-Signature > header, and the change causes the plugin to abort. This happens in the > plugin's antispa

Re: Antispam plugin: insufficent error messages

copy: src spam: 0, dst spam: 1, src unsure: 0 There are no log entries about how dspam is called, or what goes on. Indeed, dspam doesn't get called at all. I know, because I've examined the antispam- plugin source code. There would be a log message if dspam was called. It's hard to study the s

Re: Antispam plugin: insufficent error messages

Am Mittwoch, 30. November 2016, 16:23:13 CET schrieb Volker Wysk: > Do you know any documentation about the Dovecot > plugin API? I couldn't find any. I've found it. No need to tell me. Volker

Re: Antispam plugin: insufficent error messages

in the past and contributed a few small > fixes, but nothing more. Also, it doesn't look like it is actively > maintained at the moment. So, if I would debug the antispam plugin, adding more log messages, finding the reason it doesn't work now, would my changes be included in the antispam distrib

Re: Antispam plugin: insufficent error messages

Op 28-11-2016 om 21:28 schreef Volker Wysk: Hi! "Dovecot always logs a detailed error message if something goes wrong. If it doesn't, it's considered a bug and will be fixed." (http:// wiki2.dovecot.org/Logging) Yes, that is indeed what Dovecot and Pigeonhole do. However, AntiSpam is not

Re: Antispam plugin: insufficent error messages

One more point: The spam message, which has been moved to the Spam folder for training dspam, doesn't get moved. When I refresh (in KMail), the message reappears in INBOX. Bye V.W.

Antispam plugin: insufficent error messages

unsure: 0 There are no log entries about how dspam is called, or what goes on. Indeed, dspam doesn't get called at all. I know, because I've examined the antispam- plugin source code. There would be a log message if dspam was called. It's hard to study the source code, because there are hardly any co

Patch for dovecot-antispam-plugin to support IMAP Flags indicating Junk status

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear list, I made a patch which extends dovecot-antispam-plugin with support to take the addition and removal of a specific set of flags as trigger for learning. This allows for very tight integration with Thunderbird and KMail, which both set

antispam plugin not working correctly

Hi, I've configured the antispam plugin like in the wiki to use the sa- learn-pipe.sh shell script. But it's not creating the log file in /tmp. Even if I add a "touch /tmp/x" in sa-learn-pipe.sh it's not created. So how I can check if it works correctly? dovecot version 2.2.26.0 /var

Re: dovecot-antispam plugin not work

rting dovecot (via systemctl): dovecot.service. >> root@vsrv78105:/etc/dovecot# tail -f /var/log/syslog | grep imap >> Nov 3 20:02:45 vsrv78105 dovecot: imap-login: Warning: Killed with >> signal 15 (by pid=1 uid=0 code=kill) >> Nov 3 20:02:48 vsrv78105 dovecot: master:

Re: dovecot-antispam plugin not work

03:03 vsrv78105 dovecot: imap-login: Login: user=, > method=PLAIN, rip=xxx, lip=xxx, mpid=14954, TLS, session= > Nov 3 20:03:03 vsrv78105 imap: antispam: plugin initialising (2.0-notgit) > Nov 3 20:03:03 vsrv78105 imap: antispam: verbose debug enabled > Nov 3 20:03:03 vsrv78105 imap:

dovecot-antispam plugin not work

v78105 imap: antispam: mail copy: src spam: 0, dst spam: 0, src unsure: 0 Nov 3 20:03:14 vsrv78105 dovecot: imap-login: Login: user=, method=PLAIN, rip=xxx, lip=xxx, mpid=14959, TLS, session= Nov 3 20:03:14 vsrv78105 imap: antispam: plugin initialising (2.0-notgit) Nov 3 20:03:14 vsrv78105 imap: an

Re: [patch] Improved error checking for the dovecot-antispam-plugin

Hi, Has this slipped off the radar or is it somehow not suitable for inclusion? Thanks, Robert On Thu, Aug 18, 2016 at 6:16 PM, Robert Munteanu wrote: > (snip) > >> I have no issue in resending a new version of the patch with better >> error reporting, will do so in

Re: [patch] Improved error checking for the dovecot-antispam-plugin

Robert, First, thanks! Second, I'm not a committer on the dovecot project. But I've written a lot of software where if an end user has a problem and either they want to know why or if they report it and ask for help, I've found it is MUCH better to have enough info in the message given to the

Re: antispam plugin pipe script seems not to be called when it "should be"

Sent from my iPhone > On Aug 19, 2016, at 11:17 AM, b...@indietorrent.org wrote: > >> On 2016-08-18 22:58, Edgar Pettijohn wrote: >>> On 16-08-18 22:43:32, Ben Johnson wrote: >>> On 8/18/2016 10:26 PM, Ben Johnson wrote: >>> > Hello, >>> > >>> > (Full "doveconf -n" output is at the end of this

Re: antispam plugin pipe script seems not to be called when it "should be"

On 2016-08-18 22:58, Edgar Pettijohn wrote: On 16-08-18 22:43:32, Ben Johnson wrote: On 8/18/2016 10:26 PM, Ben Johnson wrote: > Hello, > > (Full "doveconf -n" output is at the end of this message.) > > I'm attempting to recreate a "recipe" I had used successfully for quite > some time (in

Re: antispam plugin pipe script seems not to be called when it "should be"

On 16-08-18 22:43:32, Ben Johnson wrote: > On 8/18/2016 10:26 PM, Ben Johnson wrote: > > Hello, > > > > (Full "doveconf -n" output is at the end of this message.) > > > > I'm attempting to recreate a "recipe" I had used successfully for quite > > some time (in Ubuntu 12.04 LTS), which allowed me

Re: antispam plugin pipe script seems not to be called when it "should be"

On 8/18/2016 10:26 PM, Ben Johnson wrote: > Hello, > > (Full "doveconf -n" output is at the end of this message.) > > I'm attempting to recreate a "recipe" I had used successfully for quite > some time (in Ubuntu 12.04 LTS), which allowed me to train > SpamAssassin's Bayes database when someone

antispam plugin pipe script seems not to be called when it "should be"

Hello, (Full "doveconf -n" output is at the end of this message.) I'm attempting to recreate a "recipe" I had used successfully for quite some time (in Ubuntu 12.04 LTS), which allowed me to train SpamAssassin's Bayes database when someone dragged an email message from one sub-folder of the

Re: [patch] Improved error checking for the dovecot-antispam-plugin

(snip) > I have no issue in resending a new version of the patch with better > error reporting, will do so in the following days. > > Robert I've attached a second version of the patch, feel free to consider any of them for inclusion. Thanks, Robert -- http://robert.muntea.nu/ changeset:

Re: [patch] Improved error checking for the dovecot-antispam-plugin

Hi Harlan, On Wed, Aug 17, 2016 at 2:18 AM, Harlan Stenn <har...@pfcs.com> wrote: > On 8/16/16 1:24 PM, Robert Munteanu wrote: >> Hi, >> >> Hopefully this is the right channel for such a patch. I have a minor >> enhancement to submit for the antispam plugin >

Re: [patch] Improved error checking for the dovecot-antispam-plugin

On 17.08.2016 02:18, Harlan Stenn wrote: > On 8/16/16 1:24 PM, Robert Munteanu wrote: >> Hi, >> >> Hopefully this is the right channel for such a patch. I have a minor >> enhancement to submit for the antispam plugin >> >> http://hg.dovecot.org/doveco

Re: [patch] Improved error checking for the dovecot-antispam-plugin

On 8/16/16 1:24 PM, Robert Munteanu wrote: > Hi, > > Hopefully this is the right channel for such a patch. I have a minor > enhancement to submit for the antispam plugin > > http://hg.dovecot.org/dovecot-antispam-plugin > > It adds minimal error checking for the se

[patch] Improved error checking for the dovecot-antispam-plugin

Hi, Hopefully this is the right channel for such a patch. I have a minor enhancement to submit for the antispam plugin http://hg.dovecot.org/dovecot-antispam-plugin It adds minimal error checking for the sendmail_binary, otherwise the reported error in case of a missing binary or one

Suggested improvement for antispam plugin documentation

Hello, I struggled a bit with getting the antispam plugin to work, because the plugin configuration in http://wiki2.dovecot.org/Plugins/Antispam is incomplete. After some twiddling, I ended up with this: # /etc/dovecot/conf.d/90-plugin.conf plugin { antispam_backend = mailtrain

Re: antispam plugin pipe backend error when moving multiple emails

Hello, I'm bumping this because it still occurs with dovecot 2.2.22. my dovecot-antispam plugin configuration : antispam_allow_append_to_spam = no antispam_backend = pipe antispam_pipe_program = /usr/bin/rspamc antispam_pipe_program_args = -h;127.0.0.1:11334;-P

Re: antispam plugin, pipe backend, how to make it work?

mod 660 /var/log/sa-learn-pipe.log cat > /etc/logrotate.d/sa-learn-pipe.log << EOFLOG /var/log/sa-learn-pipe.log { daily missingok rotate 10 compress delaycompress notifempty create 660 ${VMAIL_ID} dovecot } EOFLOG fi # spamassassin #

Re: antispam plugin, pipe backend, how to make it work?

> Am 13.04.2016 um 12:14 schrieb Johannes Rohr : > > Yikes! Our server is running a fairly dated Ubuntu Precise, what's your > version? Did an upgrade fail to fix it? I am not seeing this error on Debian > Sid but I am not using virtual users over here, so that might be the

Re: antispam plugin, pipe backend, how to make it work?

Am 13.04.2016 um 11:54 schrieb Florian Mutter: Am 13.04.2016 um 10:35 schrieb Johannes Rohr : tweaked the wrapper script to make it work. It seems like the sa-learn call silently fails: "/usr/local/bin/sa-learn-pipe.sh" 10L, 350C geschrieben root@vm10:/etc/dovecot/conf.d#

Re: antispam plugin, pipe backend, how to make it work?

Am 13.04.2016 um 11:54 schrieb Florian Mutter: Am 13.04.2016 um 10:35 schrieb Johannes Rohr : tweaked the wrapper script to make it work. It seems like the sa-learn call silently fails: "/usr/local/bin/sa-learn-pipe.sh" 10L, 350C geschrieben root@vm10:/etc/dovecot/conf.d#

Re: antispam plugin, pipe backend, how to make it work?

away by upgrading Cheers, Johannes Cheers, Johannes Am 13.04.2016 um 09:45 schrieb Johannes Rohr: Am 13.04.2016 um 09:17 schrieb Tom Hendrikx: On 13-04-16 08:27, Johannes Rohr wrote: Hi List, does the antispam plugin any way of actually seeing how it is calling the pipe program and

Re: antispam plugin, pipe backend, how to make it work?

Am 13.04.2016 um 10:35 schrieb Johannes Rohr : > > tweaked the wrapper script to make it work. It seems like the sa-learn call > silently fails: > > "/usr/local/bin/sa-learn-pipe.sh" 10L, 350C geschrieben > root@vm10:/etc/dovecot/conf.d# cat /tmp/sa-learn-pipe.log > starting

Re: antispam plugin, pipe backend, how to make it work?

nes Rohr wrote: Hi List, does the antispam plugin any way of actually seeing how it is calling the pipe program and how it is failing? I can't reproduce the failure when I call sa-learn manually. Can someone tell me, with which UID the call happens, is it the UID the current dovecot process is ru

Re: antispam plugin, pipe backend, how to make it work?

09:45 schrieb Johannes Rohr: Am 13.04.2016 um 09:17 schrieb Tom Hendrikx: On 13-04-16 08:27, Johannes Rohr wrote: Hi List, does the antispam plugin any way of actually seeing how it is calling the pipe program and how it is failing? I can't reproduce the failure when I call sa-learn manually. Can s

Re: antispam plugin, pipe backend, how to make it work?

Am 13.04.2016 um 09:17 schrieb Tom Hendrikx: On 13-04-16 08:27, Johannes Rohr wrote: Hi List, does the antispam plugin any way of actually seeing how it is calling the pipe program and how it is failing? I can't reproduce the failure when I call sa-learn manually. Can someone tell me

Re: antispam plugin, pipe backend, how to make it work?

On 13-04-16 08:27, Johannes Rohr wrote: > Hi List, > > does the antispam plugin any way of actually seeing how it is > calling the pipe program and how it is failing? I can't reproduce the > failure when I call sa-learn manually. Can someone tell me, with > which UI

Re: antispam plugin, pipe backend, how to make it work?

Hi List, does the antispam plugin any way of actually seeing how it is calling the pipe program and how it is failing? I can't reproduce the failure when I call sa-learn manually. Can someone tell me, with which UID the call happens, is it the UID the current dovecot process is running under

Re: antispam plugin, pipe backend, how to make it work?

Hi Tom, Am 12.04.2016 um 22:26 schrieb Tom Hendrikx: On 12-04-16 20:14, Johannes Rohr wrote: Hi, my setup is a dovecot 2.0.19 IMAP server on Ubuntu Precise with the antispam plugin in version 2.0+20120225-2 and spamassassin at version 3.2.2 I have been trying and failed to get the pipe

Re: antispam plugin, pipe backend, how to make it work?

On 12-04-16 20:14, Johannes Rohr wrote: > Hi, my setup is a dovecot 2.0.19 IMAP server on Ubuntu Precise with > the antispam plugin in version 2.0+20120225-2 and spamassassin at > version 3.2.2 > > I have been trying and failed to get the pipe backend of the antispam &

Re: antispam plugin, pipe backend, how to make it work?

to it via stdout? This is what I find in the syslog: Apr 12 21:54:32 vm10 imap: antispam: plugin initialising (2.0-notgit) Apr 12 21:54:32 vm10 imap: antispam: verbose debug enabled Apr 12 21:54:32 vm10 imap: antispam: "SPAM" is exact match spam folder Apr 12 21:54:32 vm10 imap: antis

Re: antispam plugin, pipe backend, how to make it work?

> antispam_mail_spam = --spam > antispam_mail_notspam = --ham > } > > to dovecot.conf > > Cheers > > Jürgen > > Am 12.04.2016 um 20:14 schrieb Johannes Rohr: >> Hi, my setup is a dovecot 2.0.19 IMAP server on Ubuntu Precise with >> the antispam

antispam plugin, pipe backend, how to make it work?

Hi, my setup is a dovecot 2.0.19 IMAP server on Ubuntu Precise with the antispam plugin in version 2.0+20120225-2 and spamassassin at version 3.2.2 I have been trying and failed to get the pipe backend of the antispam plugin to work. Spamassin by itself works, a manual call of sa-learn

Re: antispam plugin, pipe backend, how to make it work?

:14 schrieb Johannes Rohr: > Hi, my setup is a dovecot 2.0.19 IMAP server on Ubuntu Precise with > the antispam plugin in version 2.0+20120225-2 and spamassassin at > version 3.2.2 > > I have been trying and failed to get the pipe backend of the antispam > plugin to work. S

  1   2   3   4   5   >