When I did upgrade, 2.2.7 was the latest release. When I ran into the problem,
I checked back and found 2.2.8 and 2.2.9 were released shortly one after
another. It seemed these releases were sort of buggy. I would like to know if
what I described in my previous email was an known issue and was a
Am 17.01.2014 18:52, schrieb Benny Pedersen:
> Robert Schetterer skrev den 2014-01-17 18:47:
>
>> why you didnt upgrade to recent 2.2.10 version, the problem may allready get
>> fixed there
>
> package maintainers are seldom ahead of realeases
then i would call the maintainer names and ask him
Robert Schetterer skrev den 2014-01-17 18:47:
why you didnt upgrade to recent 2.2.10 version, the problem may
allready get fixed there
package maintainers are seldom ahead of realeases
Am 17.01.2014 18:38, schrieb morrison:
> I used to use dovecot 2.2.4. I saw lots of warnings saying 'Extension header
> update points outside header size'.
> I upgraded to dovecot 2.2.7, based on the discussion in mail list
why?
current is 2.2.10
http://www.dovecot.org/download.html
i don't get
Am 17.01.2014 18:38, schrieb morrison:
> Hi,
>
> I used to use dovecot 2.2.4. I saw lots of warnings saying 'Extension header
> update points outside header size'.
> I upgraded to dovecot 2.2.7, based on the discussion in mail list. Now, I see
> lots of imap aborts around:
>
> src/lib-index
Hi,
I used to use dovecot 2.2.4. I saw lots of warnings saying 'Extension header
update points outside header size'.
I upgraded to dovecot 2.2.7, based on the discussion in mail list. Now, I see
lots of imap aborts around:
src/lib-index/mail-index-transaction-export.c:203: i_assert(u32