search for: dovecot2.3

I am a little confused here. I have been running 2.2.34 which I installed in /opt/dovecot2.2 I installed 2.3.0.1 to /opt/dovecot23 I then used config files from /opt/dovecot2.2/etc/dovecot to /opt/dovecot2.3/etc/dovecot and all I did was sed -i.BAK 's/dovecot2.2/dovecot2.3/g'. Dovecot started and was running file. Next, I manually crafted config files for 2.3.0.1 based on the example

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 <dovecot at dovecot.org> > 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 > > > >

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 <dovecot at dovecot.org> > 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 > > > >

pull the patches from the port..... On Tue, Feb 5, 2019 at 2:28 PM Odhiambo Washington via dovecot < dovecot at 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 <doctor at doctor.nl2k.ab.ca> wrote: > >> On Tue, Feb 05, 2019 at 11:18:45PM +0300, Odhiambo

> On 08 March 2018 at 10:00 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > On 8 March 2018 at 10:09, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > > > > > On 07.03.2018 22:07, Odhiambo Washington wrote: > > > > I am a little confused here. > > > > I have been running 2.2.34 which I installed in /opt/dovecot2.2

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 <https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz.sig> Binary packages in https://repo.dovecot.org/ * CVE-2019-3814: If

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 <https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz.sig> Binary packages in https://repo.dovecot.org/ * CVE-2019-3814: If

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 <odhiambo at gmail.com> wrote: > 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. >

2.3.4 had the same compile issues.... On Tue, Feb 5, 2019 at 2:44 PM Odhiambo Washington <odhiambo at gmail.com> 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 12) which I have > built in preparation for the

On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot <dovecot at dovecot.org> 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 > https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz.sig >

On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot <dovecot at dovecot.org> 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 > https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz.sig >

Testing a compile on FreeBSD. gmake[2]: Entering directory '/usr/home/wash/Tools/Dovecot/fts-xapian/src' /bin/sh ../libtool --tag=CXX --mode=compile c++ -DHAVE_CONFIG_H -I. -I.. -I/opt/dovecot2.3/include/dovecot -I/opt/dovecot2.3/include/dovecot -g -O2 -MT fts-backend-xapian.lo -MD -MP -MF .deps/fts-backend-xapian.Tpo -c -o fts-backend-xapian.lo fts-backend-xapian.cpp libtool:

On Fri, Nov 23, 2018 at 04:06:53PM +0300, Odhiambo Washington wrote: > On Fri, 23 Nov 2018 at 15:29, Timo Sirainen <tss at iki.fi> wrote: > > > https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz > > https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz.sig > > Binary packages in https://repo.dovecot.org/ > > > > * The default postmaster_address is now

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 <doctor at doctor.nl2k.ab.ca> 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 <dovecot at dovecot.org> > > wrote: > > > > > Due to

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 <doctor at doctor.nl2k.ab.ca> 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 <dovecot at dovecot.org> > > wrote: > > > > > Due to

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 <larryrtx at gmail.com> wrote: > pull the patches from the port..... > > > On Tue, Feb 5, 2019 at 2:28 PM Odhiambo Washington via dovecot < > dovecot at dovecot.org> 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 12) which I have built in preparation for the upgrade of all the servers I currently have (except the 11.2). So for now, they have to run with 2.3.4, because of that reason - I am not using the port. And yes, I

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 <larryrtx at gmail.com> wrote: > 2.3.4 had the same compile issues.... > > > On Tue, Feb 5, 2019 at 2:44 PM Odhiambo Washington <odhiambo at gmail.com> > wrote: > >> Noted. >> >> I will wait for dovecot-2.3.4.2

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> <br> </div> <blockquote type="cite"> <div> On 05 February 2019 at 22:18 Odhiambo Washington via dovecot < <a href="mailto:dovecot@dovecot.org">dovecot@dovecot.org</a>> wrote:

Op 14-1-2019 om 13:40 schreef Aki Tuomi: > > Just to remind that now that there is a github repo for fts-xapian, > you could maybe open these issues there instead? > Although README.md currently says: "Please feel free to send your questions, together with the dovecot log file, to jom at grosjo.net <mailto:jom at grosjo.net> or to the dovecot ML dovecot at dovecot.org