Re: PDFs getting mangled

2018-01-20 Thread Adam Weinberger
On 20 Jan, 2018, at 10:05, Adam Weinberger wrote: On 19 Jan, 2018, at 4:39, Aki Tuomi 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

Re: PDFs getting mangled

2018-01-20 Thread Adam Weinberger
On 19 Jan, 2018, at 4:39, Aki Tuomi 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

Re: PDFs getting mangled

2018-01-19 Thread Adam Weinberger
On 19 Jan, 2018, at 4:39, Aki Tuomi 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

PDFs getting mangled

2018-01-19 Thread Adam Weinberger
gofilter_filter looks like this: #!/bin/sh cat /dev/stdin | /usr/local/bin/bogofilter -p -e -c /path/to/bogofilter.cf Images seem to come through fine. I didn't have this problem before the upgrade. It could easily be a problem with bogofilter, but I figured that I'd

zlib plugin aborts without zlib_save

2017-12-26 Thread Adam Weinberger
killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) Removing the (unused) zlib plugin made the errors disappear, at least. # Adam -- Adam Weinberger ad...@adamw.org http://www.adamw.org

zlib plugin producing errors on 2.3.0

2017-12-24 Thread Adam Weinberger
Hello, I use the zlib and imap_zlib plugins on FreeBSD. As of 2.3.0, my logs are producing these errors every so often, but AFAICT the messages themselves aren't getting corrupted. Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): assertion failed: (zstream->ostream.finished || zstream-

Re: Pigeonhole implicit keep gets unfiltered message

2017-12-23 Thread Adam Weinberger
>> (2017/12/23 @ 1051 EST): Stephan Bosch said, in 2.0K: << > Op 12/22/2017 om 3:43 AM schreef Adam Weinberger: > >> On 21 Dec, 2017, at 14:37, Stephan Bosch wrote: > >> > >> Op 12/19/2017 om 8:41 AM schreef Adam Weinberger: > >>> I'm

Re: Pigeonhole implicit keep gets unfiltered message

2017-12-21 Thread Adam Weinberger
On 21 Dec, 2017, at 14:37, Stephan Bosch 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 &q

Pigeonhole implicit keep gets unfiltered message

2017-12-18 Thread Adam Weinberger
misinterpreting the spec? # Adam -- Adam Weinberger ad...@adamw.org http://www.adamw.org

Re: kqueue crash on FreeBSD with 2.2.25

2016-07-01 Thread Adam Weinberger
> On 1 Jul, 2016, at 18:30, Adam Weinberger wrote: > >> On 1 Jul, 2016, at 10:52, Timo Sirainen wrote: >> >> On 01 Jul 2016, at 19:39, Adam Weinberger wrote: >>> >>> Hi, >>> >>> 2.2.25 crashes on FreeBSD with a kqueue-related me

Re: kqueue crash on FreeBSD with 2.2.25

2016-07-01 Thread Adam Weinberger
> On 1 Jul, 2016, at 10:52, Timo Sirainen wrote: > > On 01 Jul 2016, at 19:39, Adam Weinberger wrote: >> >> Hi, >> >> 2.2.25 crashes on FreeBSD with a kqueue-related message. I see references to >> something similar (http://www.dovecot.org/list/dovec

kqueue crash on FreeBSD with 2.2.25

2016-07-01 Thread Adam Weinberger
x27;s not dumping core, and I get the message even with "protocols =" Downgrading back to 2.2.24 fixes it. What info would be helpful for me to provide here? # Adam -- Adam Weinberger ad...@adamw.org http://www.adamw.org