similar to: v2.3.0 release candidate released

Displaying 20 results from an estimated 20000 matches similar to: "v2.3.0 release candidate released"

2017 Dec 18
1
v2.3.0 release candidate released
On 18 Dec 2017, at 23.16, Mark Moseley <moseleymark at gmail.com> wrote: > > doveadm(test1-shared at test.com): Panic: file buffer.c: line 97 > (buffer_check_limits): assertion failed: (buf->used <= buf->alloc) .. > /usr/lib/dovecot/modules/doveadm/lib10_doveadm_sieve_plugin.so(+0x43fe) > [0x6ba6997c33fe] -> Since the panic is coming from pigeonhole, did you
2017 Dec 18
0
v2.3.0 release candidate released
On Mon, Dec 18, 2017 at 7:23 AM, Timo Sirainen <tss at iki.fi> wrote: > https://dovecot.org/releases/2.3/rc/dovecot-2.3.0.rc1.tar.gz > https://dovecot.org/releases/2.3/rc/dovecot-2.3.0.rc1.tar.gz.sig > > It's finally time for v2.3 release branch! There are several new and > exciting features in it. I'm especially happy about the new logging and > statistics code,
2017 Dec 18
2
v2.3.0 release candidate released
Hi From reeBSD 9.3-RELEASE amd64: Compiles ok Installs ok On startup 1: Error about new config settings (adjusted) On startup 2: doveadm(root): Error: net_connect_unix(/var/run/dovecot//stats-writer) failed: Connection refused It seems to work so far. I get messages from fetchmail being delivered to the mailbox, yet that stale error is there. Quick search did not showed any results. Not looked
2017 Dec 22
2
Fwd: v2.3.0 release candidate released
Hi Goetz, I don't seem to understand what you mean by 'remove the last entry'. Do you mind clarifying please? On 18 December 2017 at 23:12, Goetz Schultz <email at suelze.de> wrote: > Found the guide .... Can you remove last entry please ... works with TLSv1. > > > Thanks and regards > > Goetz R. Schultz > > On 18/12/17 20:05, Goetz Schultz wrote:
2019 Apr 02
4
sieve scripts not synching for 2.3.5.1 pre-built
On 2 Apr 2019, at 22.37, Timo Sirainen via dovecot <dovecot at dovecot.org> wrote: > > On 2 Apr 2019, at 17.03, Jan-Pieter Cornet via dovecot <dovecot at dovecot.org <mailto:dovecot at dovecot.org>> wrote: >> >> Hi, >> >> We're synching mailboxes, changing format from maildir to mdbox, using doveadm backup/doveadm sync. >> >> When
2017 Dec 22
1
Fwd: v2.3.0 release candidate released
Okay, I was hoping it has something to do with where I am stuck compiling. Could you kindly share your configure options? Mine which has always worked with Dovecot versions prior to 2.3 is refusing to work on FreeBSD i386. <cut> mv -f .deps/test_auth_cache-test-auth-cache.Tpo .deps/test_auth_cache-test-auth-cache.Po clang -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-auth
2017 Dec 28
7
dovecot-pigeonhole problems after upgrade to v2.3.0
Hello, After upgrading to dovecot 2.3.0, my sieve filtering is broken. I managed it via roundcube's managesieve plugin. my emails are not being filtered accordingly into their folders and when i attempt to access the filter interface in roundcube, my maillog reports: Dec 28 12:05:07 mail roundcube: <gs7miohh> PHP Error: Unable to connect to managesieve on 127.0.0.1:4190 in
2018 Aug 07
4
Message delivered twice caused by an LMTP error "Got unexpected reply" during upgrade to 2.3
Hi all, we are upgrading our dovecot platform from: # dovecot --version 2.2.15.14 (39f57c379ded+) to # dovecot --version 2.3.2.1 (0719df592) Our platform is debian based and it is configured as director and backend proxy. We have just upgrade only 4 servers (2 directors and 2 backends) and when the lmtp traffic flow goes through an upgraded director and a not-upgraded backend sometimes the
2018 Mar 27
3
Release 2.3.1
Hi! We are releasing v2.3.1, which mostly consists of bug fixes for 2.3.0, and few improvements. This is also available via https://repo.dovecot.org if you want packages. libsodium support didn't get into this build, due to build environment issues, but 2.3.2 will contain it. * Submission server support improvements and bug fixes - Lots of bug fixes to submission server * API CHANGE:
2018 Mar 27
3
Release 2.3.1
Hi! We are releasing v2.3.1, which mostly consists of bug fixes for 2.3.0, and few improvements. This is also available via https://repo.dovecot.org if you want packages. libsodium support didn't get into this build, due to build environment issues, but 2.3.2 will contain it. * Submission server support improvements and bug fixes - Lots of bug fixes to submission server * API CHANGE:
2017 Dec 27
4
Ubuntu Auth Issues with new repository code..
?? Saw the new repository notification, and figured what the heck I would try letting it upgrade me from the current v2.2.22 release that apparently is in the Ubuntu 16.04 packages, to the new repository release of v2.3.0. ?I followed the info on repo.dovecot.org, and first it started bitching about lmtp (dovecot: master: Fatal: service(lmtp) access(/usr/lib/dovecot/lmtp) failed: No such
2014 May 11
5
v2.2.13 released
http://dovecot.org/releases/2.2/dovecot-2.2.13.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.13.tar.gz.sig A few minor changes since v2.2.13.rc1, mainly making the Pigeonhole tests pass. * Fixed a DoS attack against imap/pop3-login processes. If SSL/TLS handshake was started but wasn't finished, the login process attempted to eventually forcibly disconnect the client, but failed
2014 May 11
5
v2.2.13 released
http://dovecot.org/releases/2.2/dovecot-2.2.13.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.13.tar.gz.sig A few minor changes since v2.2.13.rc1, mainly making the Pigeonhole tests pass. * Fixed a DoS attack against imap/pop3-login processes. If SSL/TLS handshake was started but wasn't finished, the login process attempted to eventually forcibly disconnect the client, but failed
2017 Dec 28
5
dovecot-pigeonhole problems after upgrade to v2.3.0
December 28, 2017 2:52 PM, "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote: > December 28, 2017 1:21 PM, "Aki Tuomi" <aki.tuomi at dovecot.fi> wrote: > >>> On December 28, 2017 at 7:43 PM "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote: >>> >>> December 28, 2017 12:14 PM, "Aki
2006 May 25
1
save() saves extra stuff if object is not evaluated
Hi, it looks like save() is saving all contents of the calling environments if the object to be saved is *not* evaluated, although it is not that simple either. After many hours of troubleshooting, I'm still confused. Here is a reproducible example (also attached) with output. I let the code and the output talk for itself: peek <- function(file, from=1, to=500) {
2019 Dec 13
2
BUG: panic when using fs:posix as dict for acl_shared_dict
Hi Aki, I'm not sure if this bug was worked on?? Sadly I ran into it too recently, on version 2.3.4.1. Regards, Aragon On 2018/02/07 13:23, Aki Tuomi wrote: > Hi! > > Thank you for reporting this issue. We'll look into it. Maybe you can > use sqlite3 instead as workaround? > > Aki > > > On 07.02.2018 14:22, Marco Giunta wrote: >> Hi, >>
2019 May 04
1
sieve scripts not synching for 2.3.5.1 pre-built
Hi, same here, this doesn't seeem to be fixed with latest pigeonhole and dovecot release. Regards, Marcel Am 03.05.2019 um 08:20 schrieb Piper Andreas via dovecot: > Hello, > > Am 02.04.19 um 21:51 schrieb Timo Sirainen via dovecot: >> On 2 Apr 2019, at 22.37, Timo Sirainen via dovecot <dovecot at dovecot.org >> <mailto:dovecot at dovecot.org>> wrote:
2019 Apr 02
2
sieve scripts not synching for 2.3.5.1 pre-built
Hi, We're synching mailboxes, changing format from maildir to mdbox, using doveadm backup/doveadm sync. When still running 2.2.36, 'doveadm backup' also synched the sieve scripts, without issues. After the upgrade to 2.3.5.1, the sieve sync stopped working. We're using the pre-built 2.3 packages from https://repo.dovecot.org/ce-2.3-latest/debian/stretch In fact, when I now
2000 Aug 31
2
'ssh -f' option, interoperability with ssh v2.3.0
i'm trying to use the ssh command's -f option with OpenSSH v2.1.1p4 on linux (RedHat v6.2). this option doesn't seem to be working properly on my system - the specified is run succesfully but it isn't put to the background. is this a known problem? also, OpenSSH doesn't seem to interoperate with SSH Communications Security's ssh v2.3.0 (apparently because of different
2018 Aug 21
2
lmtp Panic Buffer write out of range
Hi all, as described here: https://www.dovecot.org/pipermail/dovecot/2018-July/112173.html we are experiencing the same error on dovecot version 2.3.2.1 while it never occurs on an old version as 2.2.15 It followings the error logs: On an upgraded dovecot backend: Aug 21 12:03:51 backend20 dovecot: lmtp(test1 at internalinboundcm.eu)<SONkAYfje1veGgAAu8+/vw>: Panic: Buffer write out of