similar to: Moving mboxes around

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

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

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

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,

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

Hi, on my small Xen-virtualised server with 48 MiB RAM I use Postfix and Dovecot, because the Debian administrators dislike qmail [1], which is in my opinion despite some maintainability and code quality issues a quite well designed software, because it mostly follows the UNIX principles. Postfix is not able to sort my E-Mail into different Maildir folders and after I looked at procmail's

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

> 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

Hi, what is the point of adding an empty argument to the command called by the "executable = script ..." setting in a service? I guess that would be the call to array_append_space at line 57 in util/script.c. Background is that I'm trying to run bogofilter through the extprograms Pigeonhole plugin. So I've defined a service entry with a unix_listener and wondered why my test

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

# 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

Can someone suggest anything that will help with the following ext3 performance problem? (It's a Berkeley db issue at bottom, but the ext3 part is worth looking at, I think.) First, two paragraphs of background: A Bayesian spam filter called bogofilter uses Berkeley db to maintain two database files of identical format: one containing words found in spam email and for each word the number

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?

I use bogofilter and a script or two to manage junk mail on my home box (fetchmail from POP3, postfix and procmail to local maildirs, mutt for MUA). Since these mails are just files I figured it never mattered that I moved them from one folder to another via a bash script, but some posts on this list make me think I shouldn't do that on a server running dovecot (IMAP). What I currently have

i'm trying to backup the dovecot Maildir files over a cifs share. source is a debian build, share is a readynas. i've been getting rsync: mkstemp 'filename goes here' failed: Not a directory (20) errors. rsync is v3.0. i believe this is related to the dovecot file naming convention that includes characters such as ':' in the filename. anyone else seeing

Package: dovecot Version: 0.99.10.4-2 I am accessing my IMAP folder on my ~/Maildir using mutt via Dovecot and I have this problem whereby mutt incorrectly reports I have new mail in a "mailboxes" polled mailbox. This happens all the time when I press the key bound to change mailbox. I use courier IMAP at school, and I have not experienced this problem. A bug with dovecot or mutt?

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