similar to: v2.3.3 release candidate released

It should work if you add it to apt. Directory listing is denied, which causes 403 if you access with browser. Aki -------- Original message --------From: Michael Marley <michael at michaelmarley.com> Date: 21/09/2018 18:00 (GMT+02:00) To: Dovecot Mailing List <dovecot at dovecot.org> Subject: Re: v2.3.3 release candidate released On 2018-09-21 09:45, Timo Sirainen wrote: >

https://dovecot.org/releases/2.3/dovecot-2.3.3.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.3.tar.gz.sig * doveconf hides more secrets now in the default output. * ssl_dh setting is no longer enforced at startup. If it's not set and non-ECC DH key exchange happens, error is logged and client is disconnected. + Added log_debug=<filter> setting. + Added

https://dovecot.org/releases/2.3/dovecot-2.3.3.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.3.tar.gz.sig * doveconf hides more secrets now in the default output. * ssl_dh setting is no longer enforced at startup. If it's not set and non-ECC DH key exchange happens, error is logged and client is disconnected. + Added log_debug=<filter> setting. + Added

On 25/09/2018 22:39, Stephan Bosch wrote: > Something mightily weird is going on at your end. It doesn't fail here > (see below). First of all, what is your configuration (output from > `dovecot -n`)? You have dovecot.conf but... $ dovecot -c dovecot.conf -n # 2.3.3.rc1 (14e4920d8): dovecot.conf # Pigeonhole version 0.5.2 (7704de5e) # OS: SunOS 5.11 i86pc # Hostname: mailhost

On Thu, Sep 27, 2018 at 10:42:16 +0100, James wrote: > On 25/09/2018 22:39, Stephan Bosch wrote: > > > Something mightily weird is going on at your end. It doesn't fail here > > (see below). First of all, what is your configuration (output from > > `dovecot -n`)? > > You have dovecot.conf but... > > $ dovecot -c dovecot.conf -n > # 2.3.3.rc1

Op 27-9-2018 om 11:42 schreef James: > On 25/09/2018 22:39, Stephan Bosch wrote: > >> Something mightily weird is going on at your end. It doesn't fail here >> (see below). First of all, what is your configuration (output from >> `dovecot -n`)? > > You have dovecot.conf but... > > $ dovecot -c dovecot.conf -n > # 2.3.3.rc1 (14e4920d8): dovecot.conf > #

On 24/09/2018 11:51, Stephan Bosch wrote: > Can you try with the sieve-test command-line tool, in particular with > trace debugging enabled? Thank you for the debugging tip, is this useful? $ sieve-test -D -c dovecot.conf sieve message sieve-test(james): Debug: sieve: Pigeonhole version 0.5.3.rc1 (716b1b49) initializing sieve-test(james): Debug: sieve: include: sieve_global is not set;

Looks like dovecot is not sending stuff to syslog anymore I am getting some message in /tmp/dovecot.log. However the lmtp log files are not even created. bash-5.0# doveconf | grep log_ auth_policy_log_only = no debug_log_path = deliver_log_format = msgid=%m: %$ doveadm_http_rawlog_dir = imapc_rawlog_dir = info_log_path = lmtp_proxy_rawlog_dir = /tmp/lmtp-proxy.log lmtp_rawlog_dir =

Hello Dovecot users, Here is the Pigeonhole release candidate that goes with the Dovecot v2.3.3 release candidate. It consists only of bugfixes. Changelog v0.5.3: - Fix assertion panic occurring when managesieve service fails to open INBOX while saving a Sieve script. This was caused by a lack of cleanup after failure. - Fix specific messages causing an assert panic with actions that

Hello Dovecot users, Here's the Pigeonhole release that goes with Dovecot v2.3.3. Only two insignificant memory leak fixes were added since the release candidate (not mentioned in the changelog). Changelog v0.5.3: - Fix assertion panic occurring when managesieve service fails to open INBOX while saving a Sieve script. This was caused by a lack of cleanup after failure. - Fix

Hello Dovecot users, Here is the Pigeonhole release candidate that goes with the Dovecot v2.3.3 release candidate. It consists only of bugfixes. Changelog v0.5.3: - Fix assertion panic occurring when managesieve service fails to open INBOX while saving a Sieve script. This was caused by a lack of cleanup after failure. - Fix specific messages causing an assert panic with actions that

Can you try with the sieve-test command-line tool, in particular with trace debugging enabled? Op 24-9-2018 om 12:03 schreef James: > I have a sieve problem with dovecot v2.3.3 rc1 with either of > pigeonhole 0.5.2 or 0.5.3.rc1.? The the change that triggers this is > in dovecot not pigeonhole.? Sieve filtering has been working with > v2.3.2 and many earlier versions. > >

Hello Dovecot users, Here's the Pigeonhole release that goes with Dovecot v2.3.3. Only two insignificant memory leak fixes were added since the release candidate (not mentioned in the changelog). Changelog v0.5.3: - Fix assertion panic occurring when managesieve service fails to open INBOX while saving a Sieve script. This was caused by a lack of cleanup after failure. - Fix

On 24/09/2018 12:34, James wrote: > $ cat sieve > require ["vacation"]; > vacation > # Reply at most once a day to a same sender > :days 1 ...removing the ":days 1" stops the corruption: $ sieve-test -D -c dovecot.conf sieve.2 message sieve-test(james): Debug: Effective uid=1001, gid=10, home=/home/james sieve-test(james): Debug: maildir++:

You can enable `-d -' and `-t - -Tlevel=matching' as well. Op 24-9-2018 om 13:34 schreef James: > On 24/09/2018 11:51, Stephan Bosch wrote: > >> Can you try with the sieve-test command-line tool, in particular with >> trace debugging enabled? > > Thank you for the debugging tip, is this useful? > > > $ sieve-test -D -c dovecot.conf sieve message >

> On 27 Sep 2018, at 16.53, James <list at xdrv.co.uk> wrote: > > On 27/09/2018 13:40, Stephan Bosch wrote: > >>> Address Line Code >>> 00000000: DEBUG BLOCK: 3 >>> 00000001: EXTENSIONS [1]: >>> 00000002: vacation >>> 00000004: 2: VACATION >>> 00000007: 4: seconds: NUM 5 >>> 00000009:

On 28.09.2018 12:38, James wrote: > On 27/09/2018 16:14, Sami Ketola wrote: > >>> It was studio cc.? gcc doesn't make it through configure and I >>> didn't ask why. >> >> Can you share a little bit more info on how did the compile (or >> configure even) fail with gcc on Solaris 11? > > > $ ./configure $ARGS > ... > checking Linux

On 25/09/2018 22:39, Stephan Bosch wrote: Hello, > Something mightily weird is going on at your end. It doesn't fail here This is correct. I believe there to be a compiler problem. Removing optimisation from sieve-binary-code.c gives success. Thank you to Stephan Bosch for testing this for me and pointing me in the right direction. My debugging was confused because dovecot flags

Op 1-10-2018 om 10:43 schreef James: > On 25/09/2018 22:39, Stephan Bosch wrote: > > Hello, > >> Something mightily weird is going on at your end. It doesn't fail here > > This is correct.? I believe there to be a compiler problem. Removing > optimisation from sieve-binary-code.c gives success. > > Thank you to Stephan Bosch for testing this for me and

I have a sieve problem with dovecot v2.3.3 rc1 with either of pigeonhole 0.5.2 or 0.5.3.rc1. The the change that triggers this is in dovecot not pigeonhole. Sieve filtering has been working with v2.3.2 and many earlier versions. Log report: Sep 24 10:36:13 mailhost dovecot: [ID 702911 mail.error] lmtp(user at domain.tld)<15816><RnikKw2wqFvIPQAAs831Jw>: Error: sieve: !!BUG!!: