Displaying 20 results from an estimated 50000 matches similar to: "v2.2.30.2 released"
2017 Jun 22
1
Trouble after Upgrade to v2.2.30.2 missing value for DOVECOT_
Hi,
I keep getting these errors after upgraded to 2.2.30.2. I can't seems to
find what is going on. This is running a Freebsd 10.3-RELEASE-p11 :(
Can someone please assist ?
Jun 22 14:45:23 starlite2 dovecot: auth: Debug: Loading modules from
directory: /usr/local/lib/dovecot/auth
Jun 22 14:45:23 starlite2 dovecot: auth: Debug: Module loaded:
2017 Jun 21
2
Dovecot 2.2.30* compiling error
Timo Sirainen wrote:
> On 21 Jun 2017, at 16.03, Mart Pirita <sysadmin at e-positive.ee> wrote:
>>>> ltest_lib-test-bits.o: In function `bits_required64':
>>>> /usr/src/redhat/BUILD/dovecot-2.2.30/src/lib/bits.h:33: undefined
>>>> reference to `__builtin_clzll'
> This can be fixed with the attached patch.
Thanks, got this time new error, do
2018 Jun 29
9
v2.3.2 released
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/
* old-stats plugin: Don't temporarily enable PR_SET_DUMPABLE while
opening
2017 Jun 01
0
v2.2.30 released
On 30 May 2017 at 21:16, Timo Sirainen <tss at iki.fi> wrote:
> https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz
> https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz.sig
>
> * auth: Use timing safe comparisons for everything related to
> passwords. It's unlikely that these could have been used for
> practical attacks, especially because Dovecot delays
2018 Jun 29
9
v2.3.2 released
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/
* old-stats plugin: Don't temporarily enable PR_SET_DUMPABLE while
opening
2011 Apr 16
2
doveadm mailbox status 2.0.12 crashes
My gdb won't cooperate and produce a backtrace so I hope this dbx stack
trace gives sufficient clues as to why it crashed. It happended when
I was testing a doveadm command for a user which a large collection
of mboxs:
# dbx doveadm
(dbx) run mailbox status -u user messages \*
... long list ...
igel messages=1
INBOX messages=231
doveadm(user): Panic: Trying to deinit storage
2017 May 30
7
v2.2.30 released
https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz
https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz.sig
* auth: Use timing safe comparisons for everything related to
passwords. It's unlikely that these could have been used for
practical attacks, especially because Dovecot delays and flushes all
failed authentications in 2 second intervals. Also it could have
worked only
2017 May 30
7
v2.2.30 released
https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz
https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz.sig
* auth: Use timing safe comparisons for everything related to
passwords. It's unlikely that these could have been used for
practical attacks, especially because Dovecot delays and flushes all
failed authentications in 2 second intervals. Also it could have
worked only
2017 Jun 01
3
v2.2.30 released
At least doveconf -n output would help. I guess related to authentication settings. Are there any errors in logs?
> On 1 Jun 2017, at 12.14, Odhiambo Washington <odhiambo at gmail.com> wrote:
>
>> On 30 May 2017 at 21:16, Timo Sirainen <tss at iki.fi> wrote:
>>
>> https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz
>>
2017 Apr 06
2
v2.2.29.rc1 released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.29.rc1.tar.gz
http://dovecot.org/releases/2.2/rc/dovecot-2.2.29.rc1.tar.gz.sig
Planning to release v2.2.29 on Monday. Please find and report any bugs before that.
* When Dovecot encounters an internal error, it logs the real error and
usually logs another line saying what function failed. Previously the
second log line's error message was
2017 Apr 06
2
v2.2.29.rc1 released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.29.rc1.tar.gz
http://dovecot.org/releases/2.2/rc/dovecot-2.2.29.rc1.tar.gz.sig
Planning to release v2.2.29 on Monday. Please find and report any bugs before that.
* When Dovecot encounters an internal error, it logs the real error and
usually logs another line saying what function failed. Previously the
second log line's error message was
2018 Jun 18
0
v2.3.2 release candidate released
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
2018 Jun 18
0
v2.3.2 release candidate released
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
2017 May 31
0
v2.2.30 released
Le 30/05/2017 ? 20:16, Timo Sirainen a ?crit :
> https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz
> https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz.sig
>
> * auth: Use timing safe comparisons for everything related to
> passwords. It's unlikely that these could have been used for
> practical attacks, especially because Dovecot delays and flushes all
2018 Sep 21
0
v2.3.3 release candidate released
It should work if you add it to apt. Directory listing is denied, which causes 403 if you access with browser.
Aki
-------- Original message --------From: Michael Marley <michael at michaelmarley.com> Date: 21/09/2018 18:00 (GMT+02:00) To: Dovecot Mailing List <dovecot at dovecot.org> Subject: Re: v2.3.3 release candidate released
On 2018-09-21 09:45, Timo Sirainen wrote:
>
2018 Sep 21
1
v2.3.3 release candidate released
https://dovecot.org/releases/2.3/rc/dovecot-2.3.3.rc1.tar.gz
https://dovecot.org/releases/2.3/rc/dovecot-2.3.3.rc1.tar.gz.sig
Binary packages are also available in https://repo.dovecot.org/ in ce-2.3.3 repository (not ce-2.3-latest).
* doveconf hides more secrets now in the default output.
* ssl_dh setting is no longer enforced at startup. If it's not set and
non-ECC DH key exchange
2018 Sep 21
1
v2.3.3 release candidate released
https://dovecot.org/releases/2.3/rc/dovecot-2.3.3.rc1.tar.gz
https://dovecot.org/releases/2.3/rc/dovecot-2.3.3.rc1.tar.gz.sig
Binary packages are also available in https://repo.dovecot.org/ in ce-2.3.3 repository (not ce-2.3-latest).
* doveconf hides more secrets now in the default output.
* ssl_dh setting is no longer enforced at startup. If it's not set and
non-ECC DH key exchange
2018 Dec 11
1
Dovecot IMAP connections
What exactly means "deinit".
Yesterday I had all IMAP processes with word "deinit" in brackets and
dovecot reached the limit of processes.
I had to do a restart of the process.
eg.:
dovecot 32482 0.0 0.0 24832 4256 ? S 03:29 0:00
dovecot_host1/imap [pierrot xxx.xxx.xx.xx (deinit)]
Dovecot version 2.2.32.
Regards,
Jack
-------------- next part
2016 Jul 23
4
Doveadm error
Il 15.07.2016 16:03 aki.tuomi at dovecot.fi ha scritto:
>> On July 12, 2016 at 4:30 PM L?szl? K?rolyi <laszlo at karolyi.hu> wrote:
>>
>>
>> Hey everyone,
>>
>> I've got a weird error since I upgraded to the latest dovecot on my
>> FreeBSD box:
>>
>> root at postfixjail /# doveadm quota recalc -u xxx at xxx.com
>>
2017 May 24
0
v2.2.30 release candidate released
https://dovecot.org/releases/2.2/rc/dovecot-2.2.30.rc1.tar.gz
https://dovecot.org/releases/2.2/rc/dovecot-2.2.30.rc1.tar.gz.sig
There are a couple of changes still coming, but now would be a good time to make sure anything unexpected hasn't broken. The final release should be out early next week.
* auth: Use timing safe comparisons for everything related to
passwords. It's unlikely