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

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 >

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

Re: Replacement for antispam plugin

Glad I poked around on the list today! Thanks to all for the suggestions about integration with dspam. I'll definitely have to look into this, as I rely on moving messages to a specific folder with various IMAP clients to retrain dspam false positives and negatives. A quick pair of questions:

Re: Replacement for antispam plugin

On 02/12/2017 05:28 PM, Stephan Bosch wrote: > > Actually, Pigeonhole should be able to do that too: > > https://github.com/dovecot/pigeonhole/blob/master/doc/plugins/sieve_extprograms.txt#L112 > > Yes, I need to update the wiki. > > > Regards, > > Stephan. > For DSPAM, with --client, one also

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" 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.

Re: Replacement for antispam plugin

On Sun, Feb 12, 2017 at 8:56 PM, Stephan Bosch wrote: > Op 2/12/2017 om 5:36 PM schreef George Kontostanos: >> On Sun, Feb 12, 2017 at 3:52 PM, Aki Tuomi wrote: >> On February 10, 2017 at 10:06 AM Aki Tuomi wrote:

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 wrote: > >>> On February 10, 2017 at 10:06 AM Aki Tuomi wrote: >>> >>> >>> Hi! >>> Since antispam plugin is deprecated and we would really prefer people

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 wrote: > > > On February 10, 2017 at 10:06 AM 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

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 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. > >

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: 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 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 prefer people > >> not to use it, we wrote

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 suggestions are most welcome. >>

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

> On Feb 11, 2017, at 12:50 AM, Ralph Seichter wrote: > > Check out https://wiki.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve, My concern is, will you experience any lag while moving message? According to the doc, this plugin works like “pipe” backend of old

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

On Fri, Feb 10, 2017 at 6:25 PM, George Kontostanos wrote: > > > On Fri, Feb 10, 2017 at 5:09 PM, Darac Marjal > wrote: > >> On Fri, Feb 10, 2017 at 03:52:52PM +0100, Ralph Seichter wrote: >> >>> On 10.02.2017 09:06, Aki Tuomi wrote: >>> >>>

Re: Replacement for antispam plugin

On Fri, Feb 10, 2017 at 5:09 PM, Darac Marjal 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 people >>> not to use it, we wrote

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-Flag" "YES" {

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. 2017 09:06,

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 are most welcome. >> >>

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/AntispamWithSieve >

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