similar to: Dovecot and Bogofilter

Op 1/20/2018 om 11:01 PM schreef Adam Weinberger: >> On 20 Jan, 2018, at 10:05, Adam Weinberger <adamw at adamw.org> wrote: >> >> >>> On 19 Jan, 2018, at 4:39, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >>> >>> >>> >>> On 19.01.2018 04:35, Adam Weinberger wrote: >>>> Since upgrading to 2.3.0 / 0.5.0.1, incoming

> On 19 Jan, 2018, at 4:39, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > > On 19.01.2018 04:35, Adam Weinberger wrote: >> Since upgrading to 2.3.0 / 0.5.0.1, incoming PDFs are getting mangled. >> It seems to be happening when I use vnd.dovecot.filter. When I comment >> out the block, things come through fine. >> >> My filter block looks like

Since upgrading to 2.3.0 / 0.5.0.1, incoming PDFs are getting mangled. It seems to be happening when I use vnd.dovecot.filter. When I comment out the block, things come through fine. My filter block looks like this: require "vnd.dovecot.filter"; filter "bogofilter_filter"; if header :contains "X-Bogosity" [ "Spam,

> On 21 Dec, 2017, at 14:37, Stephan Bosch <stephan at rename-it.nl> wrote: > > Op 12/19/2017 om 8:41 AM schreef Adam Weinberger: >> I'm getting a behaviour with pigeonhole that I wasn't expecting. Am I >> misunderstanding the design? >> >> I run my messages through a vnd.dovecot.filter. It's essentially this: >> >> filter

# 2.2.12: /etc/dovecot/dovecot.conf # OS: Linux 3.15.4-x86_64-linode45 x86_64 openSUSE 12.3 (x86_64) Short version: 1) I filter out spam by using a dovecot sieve filter to act based on a header inserted by bogofilter 2) In some cases, sieve fails to correctly file based on this header 3) Testing with sieve-test indicates that it's testing the wrong header 4) Suggestions? Am I doing

DEBIAN package information: ii dovecot-common 0.99.11-3 ii dovecot-imapd 0.99.11-3 ii bogofilter 0.93.1-1 Apologies for cross-posting, but I think the problem lies somewhere in here. Maybe someone can tell me something useful. Now, I've confirmed the following: I received a mail message that was not spam, of size 2132 originally. clamav scanned it and bumped the size up to 2356

Hello I have implemented recently in my work bogofilter utility to mark messages as Spam or Ham, currently is working perfectly, but I want to move those messages marked as spam to a folder called spam. I installed dovecot-sieve with the intention of using fileinto to accomplish this. my question is: where I put this: require "fileinto"; if header :contains "X-Bogosity"

Hello, Sorry for a bit offtopic but it seems the bogofilter community is just as dead as dspam is. I trying to switch from DSPAM to bogofilter on a server where if I turn bogofilter on I run into the following issue: Certain users have sender and recipient bcc maps setup in postfix. This is for forwarding copy of an email to other address for example: Incoming lclude at company.com ->

> On 20 Jan, 2018, at 10:05, Adam Weinberger <adamw at adamw.org> wrote: > > >> On 19 Jan, 2018, at 4:39, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >> >> >> >> On 19.01.2018 04:35, Adam Weinberger wrote: >>> Since upgrading to 2.3.0 / 0.5.0.1, incoming PDFs are getting mangled. >>> It seems to be happening when I use

Op 1/21/2018 om 4:34 PM schreef Stephan Bosch: > Op 1/20/2018 om 11:01 PM schreef Adam Weinberger: >>> On 20 Jan, 2018, at 10:05, Adam Weinberger <adamw at adamw.org> wrote: >>> >>> >>>> On 19 Jan, 2018, at 4:39, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >>>> >>>> >>>> >>>> On 19.01.2018 04:35,

----- Forwarded message from Klaus Dittrich <kladit@t-online.de> ----- From: kladit@t-online.de (Klaus Dittrich) Subject: files of length zero Date: Tue, 11 Mar 2003 17:08:47 +0100 To: mbp@samba.org User-Agent: Mutt/1.4i X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=0.10.2 Hi Martin, MS-Windows users here sometimes make the expierience to become files of length zero when

On 19.01.2018 04:35, Adam Weinberger wrote: > Since upgrading to 2.3.0 / 0.5.0.1, incoming PDFs are getting mangled. > It seems to be happening when I use vnd.dovecot.filter. When I comment > out the block, things come through fine. > > My filter block looks like this: > require "vnd.dovecot.filter"; > filter "bogofilter_filter"; > >

I'm getting a behaviour with pigeonhole that I wasn't expecting. Am I misunderstanding the design? I run my messages through a vnd.dovecot.filter. It's essentially this: filter "spam_filter"; if spamheaders { fileinto "spam"; stop; } Mail stored in the spam folder is the filtered version, but the implicit-keep message is the original, unfiltered

Op 12/22/2017 om 3:43 AM schreef Adam Weinberger: >> On 21 Dec, 2017, at 14:37, Stephan Bosch <stephan at rename-it.nl> wrote: >> >> Op 12/19/2017 om 8:41 AM schreef Adam Weinberger: >>> I'm getting a behaviour with pigeonhole that I wasn't expecting. Am I >>> misunderstanding the design? >>> >>> I run my messages through a

I'm using maildrop to filter mail like: xfilter "/usr/bin/spamc" xfilter "/usr/bin/bogofilter -ep" I want to change to deliver (so I can use sieve) but can deliver do this?

for Spam. In the process of setting up a more effective spam filtering system, I just noticed that bogofilter, which implements extensions of the (a?) "Naive Bayes" text classification approach, will dump out R data frames; the man page suggests how to "integrate" it with R for verification. (sort of, that is). Anyway, for those of you looking for silly and perhaps

Hi there, I'm using Dovecot 2.0.9-1 under Arch Linux. Currently, I have Maildir configured, and I move all my emails into dovecot by using this sequence: 1) cron starts fetchmail periodically under user manfred to collect my mails from various email accounts. 2) In ~/.fetchmailrc I have configured /usr/bin/maildrop as MDA. 3) In ~/.mailfilter (used by maildrop) I have extensive filtering in

Op 6/15/2017 om 12:19 PM schreef Luescher Claude: > I have +vnd.dovecot.duplicate plugin enabled but it seems to be > ineffective. Any other tips for a workaround? > Enabling that extension does nothing by itself. You need to add a corresponding rule to your Sieve script. Also, that is the deprecated name for that extension. It is explained fully here:

Hello, Yes but how to activate this for all users, not on a per user basis or without writing out thousands of sieve files to users directories. Thank you. On 2017-06-15 13:33, Stephan Bosch wrote: > Op 6/15/2017 om 12:19 PM schreef Luescher Claude: >> I have +vnd.dovecot.duplicate plugin enabled but it seems to be >> ineffective. Any other tips for a workaround? >> >

Hello, I am developing an LTO instrumentation of programs for fuzzing (for afl++) and I run into the following problem: a lot of open source program have multiple definitons of the same functions. In normal compile mode this is not a problem, however with LTO this only works with the linker option: -Wl,--allow-multiple-definition Now to be able to instrument (it is an "opt"