similar to: [EXT] Re: Corrupted sizes using zlib plugin

Am 06.03.23 um 11:59 schrieb Aki Tuomi: >> On 06/03/2023 12:44 EET Tim Evers <te-ml-ext at artfiles.de> wrote: >> >> >> Am 06.03.23 um 11:42 schrieb Aki Tuomi: >> >>>> On 06/03/2023 12:32 EET Tim Evers <te-ml-ext at artfiles.de> wrote: >>>> >>>> >>>> Hi, >>>> >>>> since I did

> On 06/03/2023 12:44 EET Tim Evers <te-ml-ext at artfiles.de> wrote: > > > Am 06.03.23 um 11:42 schrieb Aki Tuomi: > > >> On 06/03/2023 12:32 EET Tim Evers <te-ml-ext at artfiles.de> wrote: > >> > >> > >> Hi, > >> > >> since I did not get any feedback on my bug report post regarding > >> corrupted

Am 06.03.23 um 11:42 schrieb Aki Tuomi: >> On 06/03/2023 12:32 EET Tim Evers <te-ml-ext at artfiles.de> wrote: >> >> >> Hi, >> >> since I did not get any feedback on my bug report post regarding >> corrupted sizes while using zlib >> (https://dovecot.org/pipermail/dovecot/2023-February/126105.html) I >> would like to confirm that this

Hi, since I did not get any feedback on my bug report post regarding corrupted sizes while using zlib (https://dovecot.org/pipermail/dovecot/2023-February/126105.html) I would like to confirm that this bug report reached someone in charge. Or if not - I would kindly ask for directions on how to post it in a way that spawns some action. Thx Tim

Can you try enabling mail_debug=yes, perform a pop3 session and provide logs? Aki On 25.07.2018 15:53, Jakub L?nsk? wrote: > Here is it > > # 2.3.2.1 (0719df592): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.5.2 (5d6d7c92) > # OS: Linux 4.4.0-112-generic x86_64 Ubuntu 16.04.4 LTS > # Hostname: mda22 > auth_cache_negative_ttl = 2 secs > auth_cache_size = 16 M >

I have old dovecot server: (# 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.14.15-3.el7xen.x86_64 x86_64 CentOS Linux release 7.4.1708 (Core) and new dovecot server: # 2.3.1 (c5a5c0c82): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.devel (61b47828) # OS: Linux 4.14.47-5.el7xen.x86_64 x86_64 CentOS Linux release 7.5.1804 (Core) I try

Here is it # 2.3.2.1 (0719df592): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.2 (5d6d7c92) # OS: Linux 4.4.0-112-generic x86_64 Ubuntu 16.04.4 LTS # Hostname: mda22 auth_cache_negative_ttl = 2 secs auth_cache_size = 16 M auth_cache_ttl = 1 mins auth_master_user_separator = / auth_mechanisms = plain login auth_verbose = yes default_client_limit = 2000 default_process_limit = 2000

Hi, I am struggling with Postfix/SASL/Dovecot-IMAP setup with ~/Maildir/ setup. Receiving the mail works fine, but viewing the mail(+listing) is failing. The setup I use is simple unix users from etc/passwd, (pam thru SASL) as I only host for a few people. The ~/Maildir folder has the ownership of the user, not mail or vmail, as I would have expected from the master.cf from Postfix, the

Hello, We have recently implemented dovecot directors to resolve an ongoing NFS lock/corruption issue. Everything was working great! So we updated our servers from centos 7.3 to 7.7 and dovecot 2.2.10 to 2.3.8 This was a bit of a failure and we were getting spammed with corrupt index files and logs. After we clear the index files with rm rf/mail/d/e/username/Maildir/dovecot*, they just come back

Hello, I have two installations of dovecot configured to replicate mailboxes between them. recently, i upgraded the operating system on one of them (mx2.example.com) and now i'm running one installation on version 2.2.27 (debian stretch) and another on version 2.3.4.1 (mx1.example.com debian buster). My setup includes 3 shared namespaces that point to the mailboxes of 3 accounts. these

It should eventually wind down once all the problems are fixed. Of course if it does not happen, you can always run force-resync for the problem users. Aki On 14.11.2018 10.08, Adrian M wrote: > Hi, > we upgraded our servers from version 2.2.13 to 2.2.27. After the > upgrade we notice a 10x increase in traffic with the nfs storage an > errors like this in the logfile: > > Nov

You should review https://wiki2.dovecot.org/NFS to see that the settings make sense. Aki On 14.11.2018 12.00, Adrian M wrote: > Thank you ! > I was little concerned that the following settings are not in line > with the new version: > > mail_nfs_index = yes > mail_nfs_storage = yes > mail_fsync = always > mailbox_list_index = yes > maildir_stat_dirs = yes >

Hi All, This is my first post to this list. I have recently upgraded to dovecot version 2.2.10. 1. I have one POP3 user who does not want to delete his email on the server. 2. He has accumulated over 19000 messages, and the 'dovecot.uidlist' file has more than 19000 lines! 3. Occasionally now when he has received one or more new emails, and his email client does a

Hi. I'm using exim that delivers email over LMTP to dovecot 2.2.13. I noticed that dovecot LMTP service is sometimes (reare but repeats) mixing users. Example below. There is one mail (msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>) that is going to be delivered to multiple local recipients. Some recipients are delivered properly: Sep 1 05:40:33 host dovecot:

Hi! I'm struggling with the following error: Aug 4 21:32:00 mx02 dovecot: imap(xxx at xxx.tld)<17693><w14vpU+PCCSwPxpo>: Error: Mailbox INBOX: Broken file /home/vmail/xxx.tld/xxx/dovecot-uidlist line 6246: Invalid data: Aug 4 21:49:22 mx02 dovecot: imap(xxx at xxx.tld)<21879><YNhW40+PLoBOGLlU>: Error: Mailbox INBOX: Broken file

Are you connecting to the same mailbox over NFS from multiple IMAP servers? If not and, at any given time, any mailbox will be accessed from a single NFS client, try to "dupe" Dovecot into thinking it's not using NFS. We're running quite successfully such setup with NFSv3 over TCP, which turned out to be the fastest and most reliable throughout the years. Here are the mount

Yes, it should incoming mail to inbox, where replication was requested (and mail was replicated succesfully, of course). After expunge via POP3, replication was not called at all. (It doesn't happens on IMAP connections, if I didn't mentioned in previous message) Log: Jul 26 10:54:11 mda11 dovecot: lmtp(jakub@***)<339><mMJrGzOMWVtTAQAALagawQ>: Debug: INBOX: Mailbox opened

Hi, we upgraded our servers from version 2.2.13 to 2.2.27. After the upgrade we notice a 10x increase in traffic with the nfs storage an errors like this in the logfile: Nov 12 09:48:16 mail dovecot: imap(...): Error: Corrupted index cache file /.../dovecot.index.cache: invalid record size Nov 12 09:48:16 mail dovecot: imap(...): Error: unlink(/.../dovecot.index.cache) failed: No such file or

Thank you ! I was little concerned that the following settings are not in line with the new version: mail_nfs_index = yes mail_nfs_storage = yes mail_fsync = always mailbox_list_index = yes maildir_stat_dirs = yes mmap_disable = yes On Wed, Nov 14, 2018 at 10:19 AM Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > It should eventually wind down once all the problems are fixed. Of

Thanks, they are as in example, except for "mailbox_list_index = yes" witch is from https://wiki.dovecot.org/PerformanceTuning On Wed, Nov 14, 2018 at 12:18 PM Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > You should review https://wiki2.dovecot.org/NFS to see that the settings > make sense. > > Aki > On 14.11.2018 12.00, Adrian M wrote: > > Thank you !