Displaying 20 results from an estimated 700 matches similar to: "v2.2.29.rc1 released"
2017 Apr 07
2
[Dovecot-news] v2.2.29.rc1 released
On 7 Apr 2017, at 2.25, Daniel J. Luke <dluke at geeklair.net> wrote:
>
> On Apr 6, 2017, at 1:33 PM, Timo Sirainen <tss at iki.fi> wrote:
>> Planning to release v2.2.29 on Monday. Please find and report any bugs before that.
>
> I'm seeing still seeing the assert that started showing up for me with 2.2.28
2017 Apr 07
2
[Dovecot-news] v2.2.29.rc1 released
On Apr 7, 2017, at 3:01 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote:
>> On April 7, 2017 at 9:38 AM Timo Sirainen <tss at iki.fi> wrote:
>> On 7 Apr 2017, at 2.25, Daniel J. Luke <dluke at geeklair.net> wrote:
>>>
>>> On Apr 6, 2017, at 1:33 PM, Timo Sirainen <tss at iki.fi> wrote:
>>>> Planning to release v2.2.29 on Monday.
2017 Apr 07
3
[Dovecot-news] v2.2.29.rc1 released
On Apr 7, 2017, at 11:17 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote:
>> On April 7, 2017 at 6:00 PM "Daniel J. Luke" <dluke at geeklair.net> wrote:
>> On Apr 7, 2017, at 3:01 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote:
>>>> On April 7, 2017 at 9:38 AM Timo Sirainen <tss at iki.fi> wrote:
>>>> On 7 Apr 2017, at 2.25, Daniel
2017 Apr 07
0
[Dovecot-news] v2.2.29.rc1 released
> On April 7, 2017 at 6:00 PM "Daniel J. Luke" <dluke at geeklair.net> wrote:
>
>
> On Apr 7, 2017, at 3:01 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote:
> >> On April 7, 2017 at 9:38 AM Timo Sirainen <tss at iki.fi> wrote:
> >> On 7 Apr 2017, at 2.25, Daniel J. Luke <dluke at geeklair.net> wrote:
> >>>
>
2017 Apr 07
0
[Dovecot-news] v2.2.29.rc1 released
> On April 7, 2017 at 6:48 PM "Daniel J. Luke" <dluke at geeklair.net> wrote:
>
>
> On Apr 7, 2017, at 11:17 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote:
> >> On April 7, 2017 at 6:00 PM "Daniel J. Luke" <dluke at geeklair.net> wrote:
> >> On Apr 7, 2017, at 3:01 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote:
>
2017 Apr 06
0
[Dovecot-news] v2.2.29.rc1 released
On Apr 6, 2017, at 1:33 PM, Timo Sirainen <tss at iki.fi> wrote:
> Planning to release v2.2.29 on Monday. Please find and report any bugs before that.
I'm seeing still seeing the assert that started showing up for me with 2.2.28 (https://www.dovecot.org/pipermail/dovecot/2017-February/107250.html)
Below I generate it using doveadm with dovecot 2.2.29rc1 (output slightly cleaned up
2017 Apr 07
0
[Dovecot-news] v2.2.29.rc1 released
> On April 7, 2017 at 9:38 AM Timo Sirainen <tss at iki.fi> wrote:
>
>
> On 7 Apr 2017, at 2.25, Daniel J. Luke <dluke at geeklair.net> wrote:
> >
> > On Apr 6, 2017, at 1:33 PM, Timo Sirainen <tss at iki.fi> wrote:
> >> Planning to release v2.2.29 on Monday. Please find and report any bugs before that.
> >
> > I'm seeing still
2017 Apr 10
2
v2.2.29 released
https://dovecot.org/releases/2.2/dovecot-2.2.29.tar.gz
https://dovecot.org/releases/2.2/dovecot-2.2.29.tar.gz.sig
* passdb/userdb dict: Don't double-expand %variables in keys. If dict
was used as the authentication passdb, using specially crafted
%variables in the username could be used to cause DoS (CVE-2017-2669)
* When Dovecot encounters an internal error, it logs the real error
2017 Apr 10
2
v2.2.29 released
https://dovecot.org/releases/2.2/dovecot-2.2.29.tar.gz
https://dovecot.org/releases/2.2/dovecot-2.2.29.tar.gz.sig
* passdb/userdb dict: Don't double-expand %variables in keys. If dict
was used as the authentication passdb, using specially crafted
%variables in the username could be used to cause DoS (CVE-2017-2669)
* When Dovecot encounters an internal error, it logs the real error
2018 Sep 18
1
dovecot (2.2.13) panic on imap-login from iphone se
Hi to all,
we have trouble with one user account, when using imap-login with iphone
se. The user can login and use the account from webmail (roundcube) and
from thunderbird without any errors and without any restrictions.
But if we use the account on an iphone se and try to use imap based
emails, there comes the following error (look at the end of the mail).
I have no idea, what for an error it
2017 Apr 10
1
[Dovecot-news] v2.2.29.rc1 released
On Apr 7, 2017, at 11:54 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote:
> So.. as workaround, you *could* move indexes to separate directory, using INDEXES= parameter. And move the lucene-indexes to this folder. But thank you, this helps a bit.
I'm happy to do anything else to test if you'd like.
I did go ahead and set INDEXES and can confirm that this does work around the bug.
2014 Jul 01
1
indexer failure: lucene: while doing doveadm commands
I have the following script:
#!/bin/sh
PATH=$PATH:/usr/local/bin
#Expects to be run after midnight on the first of the month
# to archive all the previous months mail
#Date Run:
TODAY=`date "+%Y-%m-%d"`
#last month in YYYY/MM
YEAR_LAST_MONTH=`date -v-1d "+%Y/%m"`
#1st of last month as 01-Mon-YYYY
FIRST_LAST_MONTH=`date -v-1d "+01-%b-%Y"`
echo 'TODAY='
2017 Feb 27
0
indexer-worker assert in v2.2.28 (fts-lucene)
I upgraded to 2.2.28 and started seeing this logged:
indexer-worker(dluke): Panic: file mailbox-list.c: line 1158 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0)
indexer-worker(dluke): Error: Raw backtrace:
2 libdovecot.0.dylib 0x000000010ec63d24 default_fatal_finish + 36
-> 3 libdovecot.0.dylib
2018 Sep 18
1
dovecot (2.2.13) panic on imap-login from iphone se
here is our config: (doveconf -n)
# 2.2.13: /etc/dovecot/dovecot.conf
# OS: Linux 3.6.11-gentoo x86_64 Gentoo Base System release 2.2
auth_cache_size = 10 M
auth_mechanisms = plain login
default_client_limit = 1024
default_process_limit = 256
hostname = HOSTNAME
imap_client_workarounds = delay-newmail tb-extra-mailbox-sep
info_log_path = /var/log/dovecot.log
listen = *
mail_location =
2017 Apr 09
0
Released Pigeonhole v0.4.18.rc1 for Dovecot v2.2.29.rc1.
Hello Dovecot users,
This is a rather small release. It fixes one important bug in the new
discard script feature. It also adds a couple of new features for IMAPSieve.
Changelog v0.4.18:
+ imapsieve plugin: Implemented the copy_source_after rule action. When
this is enabled for a mailbox rule, the specified Sieve script is
executed for the message in the source mailbox during a
2017 Apr 12
0
Released Pigeonhole v0.4.18 for Dovecot v2.2.29.
Hello Dovecot users,
Here's the definitive 0.4.18 release. There were no changes since the
release candidate.
Changelog v0.4.18:
+ imapsieve plugin: Implemented the copy_source_after rule action. When
this is enabled for a mailbox rule, the specified Sieve script is
executed for the message in the source mailbox during a "COPY" event.
This happens only after the Sieve script
2017 Apr 09
0
Released Pigeonhole v0.4.18.rc1 for Dovecot v2.2.29.rc1.
Hello Dovecot users,
This is a rather small release. It fixes one important bug in the new
discard script feature. It also adds a couple of new features for IMAPSieve.
Changelog v0.4.18:
+ imapsieve plugin: Implemented the copy_source_after rule action. When
this is enabled for a mailbox rule, the specified Sieve script is
executed for the message in the source mailbox during a
2017 Apr 10
0
2.2.29 failing tests (was: Re: v2.2.29 released)
It's failing tests on CentOS 6, it looks like it's expecting the IMAP
server to be running when it isn't, perhaps this test should soft-fail?
Making check in lib-imap-client
make[2]: Entering directory
`/builddir/build/BUILD/dovecot-2.2.29/src/lib-imap-client'
for bin in test-imapc-client; do \
if ! ./$bin; then exit 1; fi; \
done
Warning: imapc(127.0.0.1:0):
2017 Apr 11
3
2.2.29 failing tests (was: Re: v2.2.29 released)
On 11 Apr 2017, at 0.39, Peter <peter at pajamian.dhs.org> wrote:
>
> It's failing tests on CentOS 6, it looks like it's expecting the IMAP
> server to be running when it isn't, perhaps this test should soft-fail?
The test is itself running both the client and the server. Most of those errors are expected. Does it work if you run it a couple of times?
2017 Apr 11
0
2.2.29 failing tests (was: Re: v2.2.29 released)
On 11 Apr 2017, at 9.54, Timo Sirainen <tss at iki.fi> wrote:
>
> On 11 Apr 2017, at 0.39, Peter <peter at pajamian.dhs.org> wrote:
>>
>> It's failing tests on CentOS 6, it looks like it's expecting the IMAP
>> server to be running when it isn't, perhaps this test should soft-fail?
>
> The test is itself running both the client and the