similar to: Released Pigeonhole v0.4.16 for Dovecot v2.2.26.0.

Displaying 20 results from an estimated 3000 matches similar to: "Released Pigeonhole v0.4.16 for Dovecot v2.2.26.0."

2016 Oct 21
0
Released Pigeonhole v0.4.16.rc1 for Dovecot v2.2.26.rc1.
Hello Dovecot users, The upcoming release includes quite a few new features for a change. The most important ones are the Sieve discard-script feature and the new vnd.dovecot.config environment items. Documentation for these features can be found in the package itself. Please test these thoroughly. Changelog v0.4.16: * Part of the Sieve extprograms implementation was moved to Dovecot,
2016 Oct 21
0
Released Pigeonhole v0.4.16.rc1 for Dovecot v2.2.26.rc1.
Hello Dovecot users, The upcoming release includes quite a few new features for a change. The most important ones are the Sieve discard-script feature and the new vnd.dovecot.config environment items. Documentation for these features can be found in the package itself. Please test these thoroughly. Changelog v0.4.16: * Part of the Sieve extprograms implementation was moved to Dovecot,
2020 Sep 25
1
[EXT] How do I make "vnd.dovecot.environment" available?
On 24 Sep 2020, at 22:07, Sami Ketola <sami.ketola at dovecot.fi> wrote: > I think this should be > > require ["environment"]; > > instead. I eventually stumbled on a syntax that worked. Putting all of this in one place: - You need to turn on the sieve_extprograms plugin: sieve_plugins = sieve_extprograms - Then you need to enable vnd.dovecot.environment:
2016 Nov 01
2
v2.2.26.0 released
OpenSSL v1.0.1 is enough. Aki > On November 1, 2016 at 7:46 PM Ruga <ruga at protonmail.com> wrote: > > > Hello, > > We cannot upgrade from 2.2.24, because we use libressl and the newer > dovecot versions demand openssl v1.1. > > Please add the new library requirement to the INSTALL file. > > All the best. > > > > > > > >
2016 Nov 02
2
v2.2.26.0 released
Hi! Those are used if #if OPENSSL_VERSION_NUMBER >= 0x10100000L So (your) libressl is providing this define. We compile our code using GCC and CLANG regularly, with OpenSSL v1.0.x which is the currently officially supported one. Aki On 02.11.2016 12:34, Ruga wrote: > dovecot 2.2.26.0 uses the following functions, which are not available on libressl 2.4.3: > > HMAC_CTX_new >
2016 Oct 28
3
v2.2.26.0 released
http://dovecot.org/releases/2.2/dovecot-2.2.26.0.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.26.0.tar.gz.sig v2.2.26 had a couple of nasty bugs left in it, so here's a fixup release. The version number is also a little bit weird, but had to be done this way (although 2.2.26.0.1 could have been another possibility). - Fixed some compiling issues. - auth: Fixed
2016 Oct 28
3
v2.2.26.0 released
http://dovecot.org/releases/2.2/dovecot-2.2.26.0.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.26.0.tar.gz.sig v2.2.26 had a couple of nasty bugs left in it, so here's a fixup release. The version number is also a little bit weird, but had to be done this way (although 2.2.26.0.1 could have been another possibility). - Fixed some compiling issues. - auth: Fixed
2016 Nov 02
3
v2.2.26.0 released
Standard way to fix it (on the LibreSSL page) is to check for LIBRESSL_VERSION_NUMBER - e.g. the patch attached which I think catches them all where needed. Note the word think. It certainly appears to be working anyway with it. On 11/02/2016 04:07 AM, Aki Tuomi wrote: > After doing some testing by myself, I noticed that libressl, for some > unknown reason, defines > > #define
2016 Nov 02
2
v2.2.26.0 released
They have stated they are going to remain API compatible with 1.0.1h (or g, forget which they forked) - their new stuff is outside of libcrypto. On 11/02/2016 04:25 AM, Aki Tuomi wrote: > It does work today, I am just bit worried that it will keep on breaking > with libressl as they evolve their API. I would personally like to avoid > more ifdef hell if possible... > > Aki >
2017 Aug 02
2
rawlog
Hi, Trying to get rawlog working on dovecot 2.2.31 configured as per https://wiki2.dovecot.org/Debugging/Rawlog but a) it doesnt appear to be loggin anything b) rawlog_dir which is supposed to be v2.2.26+ seems no where in site .. in fact complains about unknown variable So does rawlog still do anything ???? Or am I missing something ... config is below .... # 2.2.19:
2016 Nov 02
2
v2.2.26.0 released
libressl is a leaner and safer openssl Sent from ProtonMail Mobile On Wed, Nov 2, 2016 at 12:39 PM, Michael A. Peters <'mpeters at domblogger.net'> wrote: IMHO it would be acceptable to have a LibreSSL patch that is maintained by the people who want it. It's free software, and that kind of is the point of Open Source. On 11/02/2016 04:36 AM, Michael A. Peters wrote: >
2017 Aug 03
1
rawlog
> On August 3, 2017 at 8:57 PM Alexander Dalloz <ad+lists at uni-x.org> wrote: > > > Am 03.08.2017 um 01:04 schrieb Matt Bryant: > > Hi, > > > > Trying to get rawlog working on dovecot 2.2.31 configured as per > > > > https://wiki2.dovecot.org/Debugging/Rawlog > > > > but > > > > a) it doesnt appear to be loggin anything
2016 Dec 10
2
mail_location in userdb inconsistent with imap and pigeonhole
Hi! I'm still fighting with lost mails and what I think is a locking problem. As I've lost some pretty important mails already, I decided to mitigate my troubles by moving to maildir format, which should not be susceptible to these problems. I read the docs and wanted to test on my account, before I mess with all the others and possibly break something. The way to do it seems to be to
2020 Sep 24
2
How do I make "vnd.dovecot.environment" available?
On 24 Sep 2020, at 20:45, Sami Ketola <sami.ketola at dovecot.fi> wrote: > can you link your doveconf -n and the sieve script? The user?s detail are: [root at gatekeeper ~]# doveadm user minfrin at example.com field value uid vmail gid vmail home /home/vmail/minfrin at example.com/ mail maildir:~/mail mail_auto_reply_mode reply mail_auto_reply_text I am truly away... The sieve script
2017 Jan 12
3
Pigeonhole External pipe script going zombie?
I?m running dovecot 2.2.27 and pigeonhole 0.4.16 on FreeBSD 11. I?m using the pigeonhole/sieve external pipe plugin to run a Perl program to send a Pushover notification when certain messages are received. The Perl script is executed, and the notification is sent. But then the script task seems to go zombie until it is killed after a timeout. In the user?s sieve log, I get a message like
2016 Nov 02
0
v2.2.26.0 released
dovecot 2.2.26.0 uses the following functions, which are not available on libressl 2.4.3: HMAC_CTX_new HMAC_CTX_free EVP_PKEY_get0_EC_KEY EVP_PKEY_get0_RSA OBJ_length EVP_MD_CTX_new EVP_MD_CTX_free The result of calling a non-existent function is a runtime error, and we do not want that on production servers. There are additional problems. I recommend compiling with clang-llvm 3.9.0 to
2016 Nov 02
0
v2.2.26.0 released
After doing some testing by myself, I noticed that libressl, for some unknown reason, defines #define OPENSSL_VERSION_NUMBER 0x20000000L No idea why they decided to advertise that they are OpenSSL v2.0.0. A local fix, if you need one, is to use #if OPENSSL_VERSION_NUMBER == 0x20000000L #define OPENSSL_VERSION_NUMBER 0x1000100L #endif in dcrypt-openssl.c after includes. Aki On
2016 Nov 02
0
v2.2.26.0 released
It does work today, I am just bit worried that it will keep on breaking with libressl as they evolve their API. I would personally like to avoid more ifdef hell if possible... Aki On 02.11.2016 13:22, Michael A. Peters wrote: > Standard way to fix it (on the LibreSSL page) is to check for > LIBRESSL_VERSION_NUMBER - e.g. the patch attached which I think > catches them all where
2016 Nov 01
0
v2.2.26.0 released
Hello, We cannot upgrade from 2.2.24, because we use libressl and the newer dovecot versions demand openssl v1.1. Please add the new library requirement to the INSTALL file. All the best. -------- Original Message -------- Subject: v2.2.26.0 released Local Time: 28 October 2016 6:51 PM UTC Time: 28 October 2016 16:51 From: tss at iki.fi To: dovecot-news at dovecot.org, Dovecot Mailing
2016 Nov 02
0
v2.2.26.0 released
IMHO it would be acceptable to have a LibreSSL patch that is maintained by the people who want it. It's free software, and that kind of is the point of Open Source. On 11/02/2016 04:36 AM, Michael A. Peters wrote: > They have stated they are going to remain API compatible with 1.0.1h (or > g, forget which they forked) - their new stuff is outside of libcrypto. > > On 11/02/2016