Displaying 20 results from an estimated 3000 matches similar to: "Dovecot v2.2.36.1 released"
2019 Feb 05
2
Dovecot v2.2.36.1 released
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Hi,
</div>
<div>
<br>
</div>
<div>
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.
</div>
<div>
<br>
2019 Feb 05
2
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 <ebroch at whitehorsetc.com> 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 said, we decided to flush few annoying bugs
2019 Feb 05
1
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 included in https://repo.dovecot.org/
>
> + imapsieve: Added
2019 Feb 05
0
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: Added imapsieve_expunge_discarded setting which causes
discarded messages to be expunged
2019 Feb 05
0
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: Added imapsieve_expunge_discarded setting which causes
discarded messages to be expunged
2019 Feb 05
0
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 < ebroch at whitehorsetc.com
>> <mailto:ebroch at
2019 Feb 05
0
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:
> 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
>
>
2019 Feb 05
0
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 configurations Dovecot
??? ? mistakenly trusts the username provided via authentication instead
??? ? of failing.
2019 Feb 05
3
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
<https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz.sig>
Binary packages in https://repo.dovecot.org/
* CVE-2019-3814: If
2019 Feb 05
3
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
<https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz.sig>
Binary packages in https://repo.dovecot.org/
* CVE-2019-3814: If
2019 Feb 05
4
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 <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
> >
> >
2019 Feb 05
4
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 <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
> >
> >
2019 Feb 05
0
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 last year:
"Duplicate mails on pop3 expunge with dsync replication on 2.2.35
2019 Feb 05
2
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 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
2019 Feb 05
2
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 <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.
>
2019 Feb 05
2
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 <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
2018 Nov 23
9
v2.3.4 released
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 "postmaster@<user domain or
server hostname>". If username contains the @domain part, that's
used. If not, then the server's hostname is used.
* "doveadm stats
2018 Nov 23
9
v2.3.4 released
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 "postmaster@<user domain or
server hostname>". If username contains the @domain part, that's
used. If not, then the server's hostname is used.
* "doveadm stats
2018 Nov 23
3
v2.3.4 released
On 23.11.2018 15.20, Brad Smith wrote:
> On Fri, Nov 23, 2018 at 02:29:22PM +0200, Timo Sirainen 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 "postmaster@<user domain or
>>
2018 Nov 24
2
v2.3.4 released
On Sat, 24 Nov 2018 at 10:56, Aki Tuomi <aki.tuomi at open-xchange.com> wrote:
>
> > On 23 November 2018 at 17:46 Brad Smith <brad at comstyle.com> wrote:
> >
> >
> > On 11/23/2018 9:39 AM, Odhiambo Washington wrote:
> >
> > >
> > >
> > > On Fri, 23 Nov 2018 at 17:30, The Doctor <doctor at doctor.nl2k.ab.ca
> > >