similar to: v2.3.2 released

Hi: I have been using Dovecot for well over a year now and it has always worked with few problems. The mail setup is not simple... Postfix+MailScanner+ClamAV+Docvecot+MySql+postfix.admin... just to mention the major things. The system is CentOS 5.3 on VMware. The maildir is on an NFS share, index and control is local. About a month ago I thought I upgraded from 1.1.x to 1.2.x. by doing an

On 29 Jun 2018, at 15.05, Tom Sommer <mail at tomsommer.dk> wrote: > > On 2018-06-29 14:51, Timo Sirainen wrote: > >> v2.3.2 is mainly a bugfix release. It contains all the changes in >> v2.2.36, as well as a bunch of other fixes (mainly for v2.3-only >> bugs). Binary packages are already in https://repo.dovecot.org/ > > A simple "yum update"

On 29 Jun 2018, at 15.28, Tom Sommer <mail at tomsommer.dk> wrote: > > On 2018-06-29 15:20, Timo Sirainen wrote: >> On 29 Jun 2018, at 15.05, Tom Sommer <mail at tomsommer.dk> wrote: >>> On 2018-06-29 14:51, Timo Sirainen wrote: >>>> v2.3.2 is mainly a bugfix release. It contains all the changes in >>>> v2.2.36, as well as a bunch of other

On 24.06.2019 8:21, Aki Tuomi wrote: > On 22.6.2019 22.00, Reio Remma via dovecot wrote: >> Hello! >> >> I finally took the time and spent two days to set up replication for >> my server and now I have a question or two. >> >> I initially set noreplicate userdb field to 1 for all but a test user, >> but I could still see in the logs that all mailboxes

Le mardi 25 avril 2017 ? 10:04 +0200, Robert Moskowitz a ?crit : > I thought I had this fixed, but I do not. I was away from this problem > working on other matters, and came back (after a reboot) and it is still > there, so I suspect when I thought I had it 'fixed' I was running with > setenforce 0 from another problem (that is fixed). > > So anyone know how to get

Following a hard drive corruption I have reinstalled the latest version of CentOS and all current patch files. For most applications I selected the default options. By doing this I expected that the packages would play nice with one another and I could customize as necessary. Setting SELinux to enforce I encountered all sorts of problems - but most were resolvable, save for Dovecot,

I have been getting the following on my new mailserver: Apr 7 10:17:27 z9m9z dovecot: dict: Error: mysql(localhost): Connect failed to database (postfix): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13) - waiting for 25 seconds before retry They go away when I setenforce 0. So I googled dovecot mysql selinux and the only worthwhile hit was:

On 06.08.2019 23:17, Reio Remma via dovecot wrote: > On 24.06.2019 16:25, Reio Remma wrote: >> On 24.06.2019 8:21, Aki Tuomi wrote: >>> On 22.6.2019 22.00, Reio Remma via dovecot wrote: >>>> Jun 22 16:55:22 host dovecot: dsync-local(user at host.ee)<>: Error: >>>> Remote command returned error 84: ssh -i /home/vmail/.ssh/vmail.pem -l >>>>

Hello! I finally took the time and spent two days to set up replication for my server and now I have a question or two. I initially set noreplicate userdb field to 1 for all but a test user, but I could still see in the logs that all mailboxes were trying to connect to the other server via SSH. Is that normal? Jun 22 16:55:22 host dovecot: dsync-local(user at host.ee)<>: Error: Remote

On Wed, Jul 11, 2018 at 10:46 AM, Timo Sirainen <tss at iki.fi> wrote: > On 11 Jul 2018, at 8.41, Wolfgang Rosenauer <wrosenauer at gmail.com> wrote: > > > > I'm running 2.2.36 (as provided by openSUSE in their server:mail > repository) and at least at one of my systems LMTP is crashing regularly on > certain messages (apparently a lot of them). > > >

On 2018-06-29 15:20, Timo Sirainen wrote: > On 29 Jun 2018, at 15.05, Tom Sommer <mail at tomsommer.dk> wrote: >> >> On 2018-06-29 14:51, Timo Sirainen wrote: >> >>> v2.3.2 is mainly a bugfix release. It contains all the changes in >>> v2.2.36, as well as a bunch of other fixes (mainly for v2.3-only >>> bugs). Binary packages are already in

On 2018-06-29 14:51, Timo Sirainen wrote: > v2.3.2 is mainly a bugfix release. It contains all the changes in > v2.2.36, as well as a bunch of other fixes (mainly for v2.3-only > bugs). Binary packages are already in https://repo.dovecot.org/ A simple "yum update" will result in a ton of these errors: Jun 29 15:02:19 stats: Error: stats: Socket supports major version 2, but

> Le 29 juin 2018 ? 14:51, Timo Sirainen <tss at iki.fi> a ?crit : > > https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz > https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz.sig > > v2.3.2 is mainly a bugfix release. It contains all the changes in v2.2.36, as well as a bunch of other fixes (mainly for v2.3-only bugs). > Binary packages are already in

On 29.06.2018 15:51, Timo Sirainen wrote: > https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz > https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz.sig > > v2.3.2 is mainly a bugfix release. It contains all the changes in v2.2.36, as well as a bunch of other fixes (mainly for v2.3-only bugs). Binary packages are already in https://repo.dovecot.org/ Has something been changed in

https://dovecot.org/releases/2.3/rc/dovecot-2.3.2.rc1.tar.gz https://dovecot.org/releases/2.3/rc/dovecot-2.3.2.rc1.tar.gz.sig v2.3.2 is mainly a bugfix release. It contains all the changes in v2.2.36, as well as a bunch of other fixes (mainly for v2.3-only bugs). * old-stats plugin: Don't temporarily enable PR_SET_DUMPABLE while opening /proc/self/io. This may still cause security

https://dovecot.org/releases/2.3/rc/dovecot-2.3.2.rc1.tar.gz https://dovecot.org/releases/2.3/rc/dovecot-2.3.2.rc1.tar.gz.sig v2.3.2 is mainly a bugfix release. It contains all the changes in v2.2.36, as well as a bunch of other fixes (mainly for v2.3-only bugs). * old-stats plugin: Don't temporarily enable PR_SET_DUMPABLE while opening /proc/self/io. This may still cause security

On 04/26/2017 12:29 AM, Robert Moskowitz wrote: > But the policy generates errors. I will have to submit a bug report, > it seems A bug report would probably be helpful. I'm looking back at the message you wrote describing errors in ld-2.17.so. I think what's happening is that the policy on your system includes a silent rule that somehow breaks your system. You'll need

https://dovecot.org/releases/2.2/rc/dovecot-2.2.36.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.36.rc1.tar.gz.sig v2.2.36 is hopefully going to be the last v2.2.x release. Please test this RC well, so we'll have a good final release! v2.3.2 is still going to take a couple of months before it's ready. * login-proxy: If ssl_require_crl=no, allow revoked certificates.

https://dovecot.org/releases/2.2/rc/dovecot-2.2.36.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.36.rc1.tar.gz.sig v2.2.36 is hopefully going to be the last v2.2.x release. Please test this RC well, so we'll have a good final release! v2.3.2 is still going to take a couple of months before it's ready. * login-proxy: If ssl_require_crl=no, allow revoked certificates.

Hello Dovecot users, Here's the Pigeonhole release that goes with Dovecot v2.3.2. You will need this release for Dovecot v2.3.2, because the previous v0.5.1 release will not work. No changes were performed since the release candidate. Much like version 0.4.24 for Dovecot v2.2, this release consists mostly of fixes that accumulated over the last few months. Beyond that, this release