<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">On 28. Aug 2020, at 12.10, Robert Nowotny <<a href="mailto:rnowotny@rotek.at" class="">rnowotny@rotek.at</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" class="">
<div class="">
<font face="Courier New" class="">unfortunately after re-installing </font><font face="Courier New" class="">2.3.11.3, those broken-pipe errors appear
again. (on different, new files) <br class="">
so for sure there is something broken with zlib.<br class="">
I will go back to</font><font face="Courier New" class=""><font face="Courier New" class=""> 2.3.10.1 now.<br class="">
attached is the configuration file, though it did not change
between </font></font><font face="Courier New" class=""><font face="Courier New" class=""><font face="Courier New" class=""><font face="Courier
New" class="">2.3.10.1</font></font></font> </font><font face="Courier New" class="">and </font><font face="Courier New" class=""><font face="Courier New" class="">2.3.11.3<br class=""></font></font></div></div></blockquote><div><br class=""></div><div>Oh, this is with xz, not with gz like we first thought. There are some known problems with xz, which is why we are planning on removing it entirely. I'm not sure why v2.3.11 breaks it, although there are some changes related to it but it might be coincidence. I can't reproduce this problem though.</div><div><br class=""></div><div>In any case, I'd recommend switching to zlib or to zstd in v2.3.12. (In theory you could leave the existing mails xz-compressed, but best would be to re-compress everything via dsync so old mails can be read when we eventually remove xz support.)</div></div><br class=""></body></html>