similar to: zlib errors after upgrading to 2.3.11.3

On 10. Sep 2020, at 14.07, Robert Nowotny <rnowotny1966 at gmail.com> wrote: > > > On 9. Sep 2020, at 11.14, Robert Nowotny <rnowotny1966 at gmail.com <mailto:rnowotny1966 at gmail.com>> wrote: >> >>>> Sep 3 08:33:25 lxc-imap dovecot: imap(mpaul)<48684><2/9E5mKuAezAqKjk>: Error: Mailbox Sent: UID=2171:

Dear Aki, I switched to "gz" now, since "zstd" also gave some errors on writing to files. I dont know if "xz" compression or "zstd" shreddered my MDBOX Files, but I lost 4 days of mail. (a couple of thousand mails). After restoring the backup (what was made after switching to version 2.3.11.3) I still have some broken mdfiles, but not too many. Interestingly

On 8. Sep 2020, at 12.35, Robert Nowotny <rnowotny1966 at gmail.com> wrote: Dear Aki, I switched to "gz" now, since "zstd" also gave some errors on writing to files. What kind of errors? Probably this? : Panic: file ostream.c: line 287 (o_stream_sendv_int): assertion failed: (!stream->blocking) can be - unfortunately I do not have the log files anymore... Sep

> > On 8. Sep 2020, at 12.35, Robert Nowotny <rnowotny1966 at gmail.com <mailto:rnowotny1966 at gmail.com>> wrote: >> >> >> Dear Aki, >> I switched to "gz" now, since "zstd" also gave some errors on writing to files. > > What kind of errors? Probably this? : Panic: file ostream.c: line 287 (o_stream_sendv_int): assertion

On 8. Sep 2020, at 12.35, Robert Nowotny <rnowotny1966 at gmail.com> wrote: > > > Dear Aki, > I switched to "gz" now, since "zstd" also gave some errors on writing to files. What kind of errors? > I dont know if "xz" compression or "zstd" shreddered my MDBOX Files, but I lost 4 days of mail. (a couple of thousand mails). > After

Dear Aki, I switched to "gz" now, since "zstd" also gave some errors on writing to files. I dont know if "xz" compression or "zstd" shreddered my MDBOX Files, but I lost 4 days of mail. (a couple of thousand mails). After restoring the backup (what was made after switching to version 2.3.11.3) I still have some broken mdfiles, but not too many.

unfortunately after re-installing 2.3.11.3, those broken-pipe errors appear again. (on different, new files) so for sure there is something broken with zlib. I will go back to2.3.10.1 now. attached is the configuration file, though it did not change between 2.3.10.1 and 2.3.11.3 Robert Am 26.08.2020 um 09:42 schrieb Robert Nowotny: > I had 4 broken mdbox files for 4 different users. >

I get ZLIB Errors after dovecot upgrade from 2.3.10.1 to 2.3.11.3 Thunderbird reports some error when try to save/open a bigger attachment. Aug 21 15:27:34 lxc-imap dovecot: imap(acsida)<63870><jZk...>: Error: Mailbox Sent: UID=40826: read(zlib(/home/vmail/virtualmailboxes/acsida/storage/m.2409)) failed: read(/home/vmail/virtualmailboxes/acsida/storage/m.2409) failed: Broken

Hello, Im having problems getting Dovecot to read the quota info from MySQL. My current dovecot.conf file is below. If I run the user_query of: user_query = SELECT 1000 AS uid, 1000 AS gid, maildir AS home FROM mailbox WHERE username = '%u' AND active = '1' Everything works fine but if I run the user_query of: user_query = SELECT 1000 AS uid, 1000 AS gid, maildir AS home,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am trying to implement public folders on my Fedora 8 + Postfix 2.5.1 + MySQL + Dovecot 1.0.13. I have Public folder shown in for my users but when they choose the folder "Public" they receive the error "The mail server responded: Mailbox doesn't exist: Public" (in Thunderbird) or just simply "Mailbox doesn't exist:

ok, I did install zstd (zstd command line interface 64-bits v1.4.4, by Yann Collet) reconfigured & compiled dovecot 2.3.10.1 again with option : with-zstd changed the configuration file to : zlib_save = zstd and restarted dovecot - now I have following log file errors : Aug 28 16:17:39 lxc-imap dovecot: imap(rnowotny)<237930><H1kft/CtENRUclcc>: Error: zlib_save: Unknown

On 2020-09-07 11:21:13 [+1000], Darren Tucker wrote: > The zstd part would be a larger discussion because we would need to > either carry it as a Portable patch or have zstd added to OpenBSD > base, and I don't know if that would be accepted. Do you have any > performance numbers for zstd in this application? A key stroke is here 10 bytes of raw data which zstd compresses usually

https://bugzilla.samba.org/show_bug.cgi?id=14338 Bug ID: 14338 Summary: ZSTD support Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayne at opencoder.net Reporter: Rsync at ml.breakpoint.cc

> On 25/08/2020 14:35 Robert Nowotny <rnowotny at rotek.at> wrote: > > > I get ZLIB Errors after dovecot upgrade from 2.3.10.1 to 2.3.11.3 > > > Aug 21 15:27:34 lxc-imap dovecot: imap(acsida)<63870><jZk...>: Error: Mailbox Sent: UID=40826: read(zlib(/home/vmail/virtualmailboxes/acsida/storage/m.2409)) failed:

https://bugzilla.mindrot.org/show_bug.cgi?id=2888 Bug ID: 2888 Summary: Consider adding other compression schemes (lz4, zstd) Product: Portable OpenSSH Version: 7.7p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: Miscellaneous Assignee:

I added ZSTD support to OpenSSH roughly three years ago and I've been playing with it ever since. The nice part is that ZSTD achieves reasonable compression (like zlib) but consumes little CPU so it is unlikely that compression becomes the bottle neck of a transfer. The compression overhead (CPU) is negligible even when uncompressed data is tunneled over the SSH connection (SOCKS proxy, port

From: Sebastian Andrzej Siewior <sebastian at breakpoint.cc> The "zstd at breakpoint.cc" compression algorithm enables ZSTD based compression as defined in RFC8478. The compression is delayed until the server sends the SSH_MSG_USERAUTH_SUCCESS which is the same time as with the "zlib at openssh.com" method. Signed-off-by: Sebastian Andrzej Siewior <sebastian at

I hacked zstd support into OpenSSH a while ago and just started to clean it up in the recent days. The cleanup includes configuration support among other things that I did not have. During testing I noticed the following differences compared to zlib: - highly interactive shell output (as in refreshed at a _very_ high rate) may result in higher bandwidth compared to zlib. Since zstd is quicker

I added ZSTD support to OpenSSH roughly over a year and I've been playing with it ever since. The nice part is that ZSTD achieves reasonable compression (like zlib) but consumes little CPU so it is unlikely that compression becomes the bottle neck of a transfer. The compression overhead (CPU) is negligible even when uncompressed data is tunneled over the SSH connection (SOCKS proxy, port

On 2020-08-06 08:45, J Martin Rushton via CentOS wrote: > You'll need to upgrade to CentOS8. > > C7 is at rsync 3.1.2-10, and will not go above 3.1.2 ever. > > C8.2 is at 3.1.3-7, C8 will always be on 3.1.3 > > Martin Another option is to build rsync from source, which is what I did to try out the zstd compression. centos7$ rsync --version rsync? version 3.2.2? protocol