similar to: Fwd: zlib errors after upgrading to 2.3.11.3

Displaying 20 results from an estimated 20000 matches similar to: "Fwd: zlib errors after upgrading to 2.3.11.3"

2020 Sep 08
2
zlib errors after upgrading to 2.3.11.3
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
2020 Aug 22
2
zlib errors after upgrading from 2.3.10.1 to 2.3.11.3
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
2020 Aug 21
0
zlib errors after upgrading from 2.3.10.1 to 2.3.11.3
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
2020 Sep 08
0
zlib errors after upgrading to 2.3.11.3
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
2020 Sep 10
0
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:
2020 Sep 10
2
zlib errors after upgrading to 2.3.11.3
On 9. Sep 2020, at 11.14, Robert Nowotny <rnowotny1966 at gmail.com> wrote: Sep 3 08:33:25 lxc-imap dovecot: imap(mpaul)<48684><2/9E5mKuAezAqKjk>: Error: Mailbox Sent: UID=2171: read(zlib(/home/vmail/virtualmailboxes/mpaul/storage/m.119)) failed: read(/home/vmail/virtualmailboxes/mpaul/storage/m.119) failed: Broken pipe (FETCH BODY[]) Also this way you can see if the broken
2020 Sep 08
1
zlib errors after upgrading to 2.3.11.3
> > 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
2020 Sep 09
1
zlib errors after upgrading to 2.3.11.3
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
2020 Aug 26
0
zlib errors after upgrading
I had 4 broken mdbox files for 4 different users. After deleting them, dovecot re-indexed, now everything is ok again. I can try to update tonight again to 2.3.11.3 and see if some broken files will appear again tomorrow. Am 25.08.2020 um 14:51 schrieb Aki Tuomi: >> On 25/08/2020 14:35 Robert Nowotny <rnowotny at rotek.at> wrote: >> >> >> I get ZLIB Errors after
2020 Aug 25
0
zlib errors after upgrading
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: read(/home/vmail/virtualmailboxes/acsida/storage/m.2409) failed: Broken pipe (FETCH BODY[]).... many of those entries.... after installing 2.3.10.1
2020 Aug 28
3
zlib errors after upgrading
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. >
2020 Aug 25
2
zlib errors after upgrading
> 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:
2009 Mar 24
1
Missing TMP folder - Dovecot 1.2 Beta3
Recently after upgrading to 1.2 Beta3 from 1.1.13, I started to defer mail. After looking into it deeper, it looks like Dovecot/sieve now asks for a tmp folder in the imap (maildir) folder. Once I added the tmp folder as the logs indicants, the mail was processed normally. I have split my Inbox and imap store to different folder. Looking at what it's trying to do, it looks to me that
2020 Aug 28
0
zlib errors after upgrading
zstd support was added in v2.3.11 (not v2.3.12 like I mistakenly tried to say in the earlier mail). > On 28. Aug 2020, at 16.36, Robert Nowotny <rnowotny at rotek.at> wrote: > > > 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
2020 Aug 28
2
zlib errors after upgrading
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
2009 Jan 26
2
No Spaces in Directory names
How can I make it so my users can not create folders with spaces in them? Or allow them to create such folders but rewrite them on the hardrive with a "_" or some other symbol. I have looked threw the wiki but couldn't find anything about folder name restrictions or folder name rewriting (rewrite the space to a "_"). Im having problems with some of the expire and compress
2009 May 21
1
Expire Plug-in stopped
Good evening, While working with Dovecot 1.2rc4 on Fedora 10, I have been trying to get the Expire plug-in to auto delete messages for us. When I run the plug-in with the test flag, I receive the following message: /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool --test Info: amy at example.com/Trash: stop, expire time in future: 1242953758 All messages were
2020 Aug 15
0
2.3.11.3: dsync failure
Hello! dovecot 2.3.11.3 fails to backup/sync my mailbox. The mailbox is currently in mdbox format and is (mostly) lz4-compressed. See the trace below (I've added newlines to the output): # doveadm -v backup -u username mdbox:/var/vmail/username_new/mdbox dsync(username): Panic: file istream.c: line 332 (i_stream_read_memarea): assertion failed: (!stream->blocking) dsync(username): Error:
2009 Jun 06
3
Expire/Quota error
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Using both 1.2rc5 and hg version a9d3108d0cec from today, when I run the expire tools program, I receive the following error. # /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool --test /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool --testError:
2011 Jan 26
1
Permissions issues after dovecot reload
Hello, Today while looking at a different issue (one user couldn't retrieve mail; DNS issue) I set 'mail_debug=yes' then ran `dovecot reload` on our mail server. After running the reload, dovecot started complaning about permission issues with the dict file, and preceded to try to kill it's self. The self reload didn't seem to work, and since this is a production system,