Re: status of test code

2021-01-10 Thread Aki Tuomi
Thanks for the update, we'll check it out and see if there is something to do. Aki > On 10/01/2021 23:34 st...@keptprivate.com wrote: > > > Update: > > I was finally able to build 2.3.13 on centos 8 (8.3). I managed this by going > back to the qmailtoaster spec file, removing a few things

Re: migration with doveadm backup to new cluster running dovecot 2.2.36 and replicator

2021-01-10 Thread Thomas Winterstein
we were able to narrow down the cause of the problem. After the initial dsync migration process the mailbox GUIDs are the same for each mailbox-name across all users. Is this intended behaviour of dsync? If not, how can this be changed? After the first replication process

Re: status of test code

2021-01-10 Thread st...@keptprivate.com
Update:I was finally able to build 2.3.13 on centos 8 (8.3). I managed this by going back to the qmailtoaster spec file, removing a few things no longer relevant (vpopmail) and disabling all the tests. Most tests were still running but there were also many that did not. The good news is the

Re: lzma mdboxes with unexpected EOF

2021-01-10 Thread Bjoern Franke
Hi, > > But I'm wondering why that happened at all. I stumpled upon [1] but > there was no further discussion about it. > it seems it was caused by a bug mentioned in 2.3.13's changelog: - lib-compression: Using xz/lzma compression in v2.3.11 could have written truncated output in some

auth error log format change

2021-01-10 Thread Adrian Minta
Hi, we recently upgraded to 2.3.13 from 2.3.11 and the log format for auth errors seems to have change. This change may have an adverse effect on fail2ban rules. Is there a way to revert to old format ? Thank you ! Old log example: Jan 10 00:32:37 mail dovecot: auth-worker(50806):

lzma mdboxes with unexpected EOF

2021-01-10 Thread Bjoern Franke
Hi, I'm running dovecot 2.3.13 (until 05.01. it was 2.3.11.3) on Arch Linux and used lzma compressed mdboxes. Yesterday a user called me that she is missing all mails from the beginning of the month until now. I took a look into the logs and saw several "lzma.read [...] unexpected EOF at <>".