Re: Release notify (2.2.36.1 and 2.3.4.1)

Oh, so manual compile should NOT work and it's okay or am I missing something? On Tue, 5 Feb 2019 at 23:26, The Doctor wrote: > On Tue, Feb 05, 2019 at 11:18:45PM +0300, Odhiambo Washington via dovecot > wrote: > > On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot > > wrote: > > > > > Due to

Re: Release notify (2.2.36.1 and 2.3.4.1)

the patches are already in git master. I've pulled them into the mail/dovecot port. The dovecot guys/gals will release it eventually, but the port works TODAY. On Tue, Feb 5, 2019 at 2:33 PM Odhiambo Washington wrote: > I have always been able to compile manually, even from RCs so I believe

Re: Release notify (2.2.36.1 and 2.3.4.1)

2.3.4 had the same compile issues On Tue, Feb 5, 2019 at 2:44 PM Odhiambo Washington wrote: > Noted. > > I will wait for dovecot-2.3.4.2 tarball then. > > In all the servers I listed (+2 more), I never use the mail/dovecot port. > > I rely on mail/dovecot port on my own prototype (FreeBSD

Re: Release notify (2.2.36.1 and 2.3.4.1)

You're welcome. (From your friendly FreeBSD Dovecot maintainer). On Tue, Feb 5, 2019 at 2:26 PM The Doctor via dovecot wrote: > On Tue, Feb 05, 2019 at 11:18:45PM +0300, Odhiambo Washington via dovecot > wrote: > > On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot > > wrote: > > > > > Due to

Re: Release notify (2.2.36.1 and 2.3.4.1)

pull the patches from the port. On Tue, Feb 5, 2019 at 2:28 PM Odhiambo Washington via dovecot < dovecot@dovecot.org> wrote: > Oh, so manual compile should NOT work and it's okay or am I missing > something? > > On Tue, 5 Feb 2019 at 23:26, The Doctor wrote: > >> On Tue, Feb 05, 2019 at

Re: Release notify (2.2.36.1 and 2.3.4.1)

that was a MySQL issue and mmokhi fixed it in Ports. I really do try to be conscientious about making sure it works (I use it for my mailserver). I really don't understand your hangup about using ports/pkg/poudriere/etc to build the ports and install them. On Tue, Feb 5, 2019 at 2:53 PM

Re: Dovecot v2.2.36.1 released (Pigeonhole 0.4.24.1)

On 2019-02-05 13:07, Stephan Bosch via dovecot wrote: Hi, Here is the associated release for Pigeonhole: https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.24.1.tar.gz https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.24.1.tar.gz.sig Binary packages

Re: Release notify (2.2.36.1 and 2.3.4.1)

On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot wrote: > Due to DMARC issues some people have failed to receive the latest security > information, so here it is repeated for both releases: > > 2.3.4.1 > > https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz >

Re: Release notify (2.2.36.1 and 2.3.4.1)

On Tue, Feb 05, 2019 at 11:18:45PM +0300, Odhiambo Washington via dovecot wrote: > On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot > wrote: > > > Due to DMARC issues some people have failed to receive the latest security > > information, so here it is repeated for both releases: > > > >

Re: Release notify (2.2.36.1 and 2.3.4.1)

I have always been able to compile manually, even from RCs so I believe I should be able to compile from the tarball as well. Something is broken, On Tue, 5 Feb 2019 at 23:29, Larry Rosenman wrote: > pull the patches from the port. > > > On Tue, Feb 5, 2019 at 2:28 PM Odhiambo Washington

Really solved - Re: Solved - Re: SELinux policy to allow Dovecot to connect to Mysql

This is an old issue, but I am building a new system and hit this problem all over again. This time, I asked for help from the SELinux list, as googling did not find anything new.  What resulted was a policy to allow dovecot to connect to mysql.sock: yum install policycoreutils cat >

Re: Release notify (2.2.36.1 and 2.3.4.1)

On 05 February 2019 at 22:18 Odhiambo Washington via dovecot < dovecot@dovecot.org> wrote: On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot < dovecot@dovecot.org> wrote: Due to

Re: Release notify (2.2.36.1 and 2.3.4.1)

Did I say so? It's known issue and will be fixed in future release. Aki On 05 February 2019 at 22:27 Odhiambo Washington via dovecot < dovecot@dovecot.org> wrote: Oh, so manual compile should NOT work and it's

Re: Release notify (2.2.36.1 and 2.3.4.1)

Noted. I will wait for dovecot-2.3.4.2 tarball then. In all the servers I listed (+2 more), I never use the mail/dovecot port. I rely on mail/dovecot port on my own prototype (FreeBSD 12) which I have built in preparation for the upgrade of all the servers I currently have (except the 11.2). So

Re: Dovecot v2.2.36.1 released (Pigeonhole 0.4.24.1)

Op 05/02/2019 om 20:27 schreef Michael Marley via dovecot: On 2019-02-05 13:07, Stephan Bosch via dovecot wrote: Hi, Here is the associated release for Pigeonhole: https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.24.1.tar.gz

Re: Release notify (2.2.36.1 and 2.3.4.1)

Bueno. I don't even remember well. Wasn't that issue about mysql-8.0.12 to 8.0.13?? On Tue, 5 Feb 2019 at 23:46, Larry Rosenman wrote: > 2.3.4 had the same compile issues > > > On Tue, Feb 5, 2019 at 2:44 PM Odhiambo Washington > wrote: > >> Noted. >> >> I will wait for dovecot-2.3.4.2

Re: acl_groups in LDAP

Am 05.02.19 um 08:23 schrieb Christian Rößner via dovecot: > Hi, > > I found a 9 year old thread > (https://www.dovecot.org/list/dovecot/2010-October/054407.html) concerning > acl_groups in OpenLDAP. In this thread someone asked, if it is possible to > provide ACLs as multi value in OpenLDAP.

Re: mbox 2 Maildir

Hi, I am experimenting with the migration. I unset mail_location, thus it is empty and dovecot performs automatic mailbox detection. Therefore I do not need per-user set of mail location. I login as a testuser and do: doveadm sync maildir:~/Maildir It seems for me that in this situation the

Dovecot v2.2.36.1 released

https://dovecot.org/releases/2.2/dovecot-2.2.36.1.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.36.1.tar.gz.sig     * CVE-2019-3814: If imap/pop3/managesieve/submission client has       trusted certificate with missing username field       (ssl_cert_username_field), under some

CVE-2019-3814: Suitable client certificate can be used to login as other user

Dear subscribers, we're sharing our latest advisory with you and would like to thank everyone who contributed in finding and solving those vulnerabilities. Feel free to join our bug bounty programs (open-xchange, dovecot, powerdns) at HackerOne. Please find patches for v2.2.36 and v2.3.4

Dovecot 2.3.4.1 released

https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz.sig Binary packages in https://repo.dovecot.org/     * CVE-2019-3814: If imap/pop3/managesieve/submission client has      

Re: Dovecot v2.2.36.1 released

Aki, What's the difference between 2.2.x and 2.3.x version of Dovecot? And why do you maintain both? I stopped building RPM's of the 2.2.x version and now only build 2.3.x. Should I be maintaining both? Eric On 2/5/2019 6:01 AM, Aki Tuomi wrote:

problem using different dovecot versions

Hi All, I'm new to the list and may be it's a known issue. I have a set of servers with RHEL6 and dovecot-2.2.10-1_14.el6.x86_64 and another set of servers with RHEL7 and, now, with dovecot-2.2.36-3.el7.x86_64. Both sets write to the same NFS. Since I updated RHEL7 servers (from

Re: Dovecot v2.2.36.1 released

Hi, as per our EOL statement 2.2.36 receives security and critical updates. That said, we decided to flush few annoying bugs with .1 release. You do not need to build releases for 2.2. Aki On 05 February 2019 at

Re: Dovecot v2.2.36.1 released

> On February 5, 2019 at 8:36 AM Eric Broch wrote: > > What's the difference between 2.2.x and 2.3.x version of Dovecot? And > why do you maintain both? https://dovecot.org/pipermail/dovecot-news/2018-August/000386.html michael

Re: Dovecot v2.2.36.1 released

Hello Aki, > https://dovecot.org/releases/2.2/dovecot-2.2.36.1.tar.gz > https://dovecot.org/releases/2.2/dovecot-2.2.36.1.tar.gz.sig > > - pop3_no_flag_updates=no: Don't expunge RETRed messages without QUIT is this in any way related to the problem that has first been reported in march

Re: Dovecot v2.2.36.1 released

Thank you! On 2/5/2019 8:43 AM, Aki Tuomi wrote: Hi, as per our EOL statement 2.2.36 receives security and critical updates. That said, we decided to flush few annoying bugs with .1 release. You do not need to build releases for 2.2. Aki On 05 February 2019 at 17:36 Eric Broch <

Re: Dovecot v2.2.36.1 released

for some reason Aki's posts are not making it to my GMail account from this list. Any idea why? On Tue, Feb 5, 2019 at 10:04 AM Eric Broch wrote: > Thank you! > On 2/5/2019 8:43 AM, Aki Tuomi wrote: > > Hi, > > as per our EOL statement 2.2.36 receives security and critical updates. > That

Re: Dovecot v2.2.36.1 released

On 5 Feb 2019, at 7.48, Gerald Galster wrote: > > Hello Aki, > >> https://dovecot.org/releases/2.2/dovecot-2.2.36.1.tar.gz >> https://dovecot.org/releases/2.2/dovecot-2.2.36.1.tar.gz.sig >> >>- pop3_no_flag_updates=no: Don't expunge RETRed messages without QUIT > > is this in any way

Release notify (2.2.36.1 and 2.3.4.1)

Due to DMARC issues some people have failed to receive the latest security information, so here it is repeated for both releases: 2.3.4.1 https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz.sig

Re: Dovecot v2.2.36.1 released

On 5-2-2019 17:06, Larry Rosenman wrote: for some reason Aki's posts are not making it to my GMail account from this list. Any idea why? Authentication-Results: cloud.webmeneer.net; dmarc=fail (p=reject dis=none) header.from=open-xchange.com

Re: mbox 2 Maildir

Sorry. I had wrong syntax. Missing "mbox:" It is OK with this: doveadm sync -RD mbox:~/mail/ On 02/05/2019 10:48 AM, Tamas Hegedus wrote: Hi, I am experimenting with the migration. I unset mail_location, thus it is empty and dovecot performs automatic mailbox detection. Therefore I do not

Re: Dovecot v2.2.36.1 released

Hi, It's probably because gmail. They refuse emails for random reasons occasionally. Sami > On 5 Feb 2019, at 17.06, Larry Rosenman wrote: > > for some reason Aki's posts are not making it to my GMail account from this > list. > > Any idea why? > > On Tue, Feb 5, 2019 at 10:04 AM Eric

Re: Dovecot v2.2.36.1 released (Pigeonhole 0.4.24.1)

Hi, Here is the associated release for Pigeonhole: https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.24.1.tar.gz https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.24.1.tar.gz.sig Binary packages included in https://repo.dovecot.org/ + imapsieve:

Re: [Dovecot-news] Release notify (2.2.36.1 and 2.3.4.1)

On 05 February 2019 at 22:18 Odhiambo Washington via dovecot < dove...@dovecot.org> wrote: On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot < dove...@dovecot.org> wrote: Due to

Re: [Dovecot-news] Release notify (2.2.36.1 and 2.3.4.1)

Did I say so? It's known issue and will be fixed in future release. Aki On 05 February 2019 at 22:27 Odhiambo Washington via dovecot < dove...@dovecot.org> wrote: Oh, so manual compile should NOT work and it's

[Dovecot-news] Dovecot v2.2.36.1 released

https://dovecot.org/releases/2.2/dovecot-2.2.36.1.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.36.1.tar.gz.sig     * CVE-2019-3814: If imap/pop3/managesieve/submission client has       trusted certificate with missing username field       (ssl_cert_username_field), under some

Re: [Dovecot-news] Dovecot v2.2.36.1 released (Pigeonhole 0.4.24.1)

Hi, Here is the associated release for Pigeonhole: https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.24.1.tar.gz https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.24.1.tar.gz.sig Binary packages included in https://repo.dovecot.org/ + imapsieve:

[Dovecot-news] Release notify (2.2.36.1 and 2.3.4.1)

Due to DMARC issues some people have failed to receive the latest security information, so here it is repeated for both releases: 2.3.4.1 https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz.sig