Date: Thu, 29 Mar 2018 12:20:16 +0000 From: Pietro Cerutti <gahr@FreeBSD.org> To: Adam Weinberger <adamw@adamw.org> Cc: Dewayne Geraghty <dewayne.geraghty@heuristicsystems.com.au>, The Doctor <doctor@doctor.nl2k.ab.ca>, freebsd-ports@freebsd.org Subject: Re: DoveCot 2.3 Message-ID: <20180329122016.hco3ylewydgmhey2@ptrcrt.ch> In-Reply-To: <9BD1F338-E9FF-47EC-97BA-C03E224443D7@adamw.org> References: <20180307161745.GA91630@doctor.nl2k.ab.ca> <0BBB5768-18A8-4DA2-8C74-C5DC90E48398@adamw.org> <0dd189d0-ca80-6d9e-16c0-2210e2e62eae@heuristicsystems.com.au> <9BD1F338-E9FF-47EC-97BA-C03E224443D7@adamw.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--5t45vvir6wbro6jx Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mar 28 18 21:29, Adam Weinberger wrote: >>On 7 Mar, 2018, at 15:18, Dewayne Geraghty=20 >><dewayne.geraghty@heuristicsystems.com.au> wrote: >> >>Thanks Adam, its very reassuring to know that you'll "dogfood" the=20 >>update prior to releasing to FreeBSD ports users. This is one of=20 >>those high impact updates that need it - like sendmail, samba,=20 >>heimdal, squid, nginx, apache ... ;) >> >>Kind regards, Dewayne >> >>PS dogfood is a peculiar term where, typically a supplier, uses what=20 >>they provide to others. As an example: I first came across the term=20 >>when HP Management wanted to demonstrate to their external customers=20 >>that they use the same services internally as supplied externally.=20 >>(I could write a short-story=E2=80=A6) >> >Dewayne and The, > >The dovecot and pigeonhole ports for 2.3.1 and 0.5.1 are ready to go.=20 >Larry and I have been dogfooding them, and all the bugs I encountered=20 >in 2.3.0 seem to be fixed now. > >I=E2=80=99m waiting for the next quarterly branch (4 days) and then the po= rts=20 >will be committed. If you=E2=80=99d like to use them before then, you can = grab=20 >them at https://people.freebsd.org/~adamw/dovecot-2.3.1.tar.gz > >If you encounter any problems, please do let us know! > >There=E2=80=99s a pkg-message and there=E2=80=99ll be an UPDATING entry, b= ut it bears=20 >repeating here too: read https://wiki2.dovecot.org/Upgrading/2.3=20 ><https://wiki2.dovecot.org/Upgrading/2.3>; for some of the potentially=20 >breaking changes. Merge the changes from the 2.3 conf files=20 >carefully---Dovecot 2.3 will most likely fail to start with unmodified=20 >2.2 conf files. I copied the 2.3 conf files anew and recreated my=20 >setup, and you might consider doing the same thing. Thanks Adam! I am running 2.3.1/0.5.1 now. Upgrade was smoot - in my=20 simple setup it amounted to this: -ssl_protocols =3D !SSLv2 !SSLv3 -ssl_cipher_list =3D ALL:!LOW:!SSLv2:!EXP:!aNULL +ssl_dh =3D </usr/local/etc/dovecot/dh.pem So far so good - IMAP and ManageSieve both work fine! Thanks! --=20 Pietro Cerutti --5t45vvir6wbro6jx Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQJiBAABCgBMFiEE2m3hBqW4VLhd2G1JrdDTjqGSCJ4FAlq82fwuFIAAAAAAFQAQ cGthLWFkZHJlc3NAZ251cGcub3JnZ2FockBGcmVlQlNELm9yZwAKCRCt0NOOoZII nvZ1EACTrQOoSUSXsW5RlZ8Xb48ehIxvUPSOPBpOgMyyeArOwvBJ2DUP6tNt7tk+ QeBl4OmKXZu3cJDE+HHr/U64cLsyVlfITvVNrjm+cUbS44WXXFJv6OTCo/tlwP5m 2w2DK+zFGzjfkgUwzh7j0fEmwTVKf1a9Ct62QjwaxhX1XgENTJhb1kd3TczFh5E6 27nNWqzsOSyoY1iGCEtvmqW/SJFu9efTh37r3jLXFIp4Ec4VB/LX46qkQqKnaLqd yxFXqgAdyLvC3zKrLic5YobI9V33aGifc9iJkY64oWU5moEDO3MBbyPIW0tp1SX5 l2W+9jR9P0x+LBhFU1ekKTnLGCLQFX01tGacKMAXpUCUOyCZZeyrHlk/cTZHnCVV QRdknxa7hULhB7ubYmojX7YUGfMqm4oeunjXDhTJUnnTHhDqjDE76baNXNt+3K4Z UChO2XQ84xOita846phMaFQz1YIe/KbtwwPeOwl4SSBRuVcMZoprW1MkemdX23VB EWViDBSDuIEINPDsf1mSFJgFs/qf0SfhsyqBE45I1j+z6YYa4TkHpdmui82DB1fX LhLQZZHsuW6tBBdu3exqYl0zYWBvKSrSmZ0NOHRr3spFpJgF97ihf3/iVQMChP8H GultaghBbaW5IB0OrE209hE7woti0pcMtycKkezVWgg6dCOkug== =9wAK -----END PGP SIGNATURE----- --5t45vvir6wbro6jx--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180329122016.hco3ylewydgmhey2>