Re: Sieve GLOBAL + Sieve LOCAL

Doesn't 'keep' imply 'stop'? What if your users want the email in a different folder that the INBOX? Leave the 'else' clause off. Bill On 5/17/2017 4:07 PM, dove...@pallissard.net wrote: But what I would need is execute a global sieve_before for all users to apply some spam selection

Re: 10-ssl.conf: Unknown setting: ssl / debian 1:2.2.13-12~deb8u

Hi Sophie did you try the following steps? 1. rename /etc/dovecot/conf.d/10-ssl.conf to /etc/dovecot/conf.d/10-ssl.conf.bak 2. copy /usr/share/dovecot/conf.d/10-ssl.conf to /etc/dovecot/conf.d/ 3. restart dovecot what happens? start dovecot normally? if so make a new cert with

Re: per user procmail filtering and dovecot-lda

Quoting Kenneth Porter : On 5/17/2017 11:26 AM, Adam Shostack wrote: Also, procmail is way out of date, no longer maintained, and there are "semi" known vulnerabilities that haven't been fixed.  See http://marc.info/?l=openbsd-ports=141634350915839=2  & the wikipedia

10-ssl.conf: Unknown setting: ssl / debian 1:2.2.13-12~deb8u

Hi, I've been trying to get dovecot2 running and kept having this error message: May 13 13:38:32 mail systemd[1]: Started Dovecot IMAP/POP3 email server. May 13 13:38:32 mail dovecot[2178]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 61: Unknown setting:

Re: per user procmail filtering and dovecot-lda

On 5/18/17, 3:06 PM, "dovecot on behalf of Kenneth Porter" wrote: On 5/17/2017 11:26 AM, Adam Shostack wrote: > Also, procmail is way out of date, no longer maintained, and there are > "semi" known vulnerabilities that

Re: per user procmail filtering and dovecot-lda

On 5/17/2017 11:26 AM, Adam Shostack wrote: Also, procmail is way out of date, no longer maintained, and there are "semi" known vulnerabilities that haven't been fixed. See http://marc.info/?l=openbsd-ports=141634350915839=2 & the wikipedia page. What alternatives exist for server-side

Re: lmtp segfault after upgrade

On 18.05.2017 11:56, Tom Sommer wrote: > > > --- > Tom > > On 2017-05-18 10:05, Teemu Huovila wrote: >> On 18.05.2017 10:55, Tom Sommer wrote: >>> On 2017-05-18 09:36, Teemu Huovila wrote: Hello Tom On 02.05.2017 11:19, Timo Sirainen wrote: > On 2 May 2017, at 10.41, Tom

Re: lmtp segfault after upgrade

--- Tom On 2017-05-18 10:05, Teemu Huovila wrote: On 18.05.2017 10:55, Tom Sommer wrote: On 2017-05-18 09:36, Teemu Huovila wrote: Hello Tom On 02.05.2017 11:19, Timo Sirainen wrote: On 2 May 2017, at 10.41, Tom Sommer wrote: (gdb) bt full #0 i_stream_seek

Re: lmtp segfault after upgrade

On 2017-05-18 09:36, Teemu Huovila wrote: Hello Tom On 02.05.2017 11:19, Timo Sirainen wrote: On 2 May 2017, at 10.41, Tom Sommer wrote: (gdb) bt full #0 i_stream_seek (stream=0x21, v_offset=0) at istream.c:298 _stream = #1 0x7fe98391ff32 in

Re: lmtp segfault after upgrade

On 18.05.2017 10:55, Tom Sommer wrote: > On 2017-05-18 09:36, Teemu Huovila wrote: >> Hello Tom >> >> On 02.05.2017 11:19, Timo Sirainen wrote: >>> On 2 May 2017, at 10.41, Tom Sommer wrote: (gdb) bt full #0 i_stream_seek (stream=0x21, v_offset=0) at

Re: lmtp segfault after upgrade

On 2017-05-18 09:36, Teemu Huovila wrote: Hello Tom On 02.05.2017 11:19, Timo Sirainen wrote: On 2 May 2017, at 10.41, Tom Sommer wrote: (gdb) bt full #0 i_stream_seek (stream=0x21, v_offset=0) at istream.c:298 _stream = #1 0x7fe98391ff32 in

Re: lmtp segfault after upgrade

Hello Tom On 02.05.2017 11:19, Timo Sirainen wrote: > On 2 May 2017, at 10.41, Tom Sommer wrote: >> >> (gdb) bt full >> #0 i_stream_seek (stream=0x21, v_offset=0) at istream.c:298 >>_stream = >> #1 0x7fe98391ff32 in i_stream_concat_read_next (stream=0x1efe6c0)