search for: mbox_dirty_sync

...MAP(m6933192-4): file mbox-sync.c: line 1262 (mbox_sync_do): assertion failed: (sync_ctx->ibox->mbox_sync_dirty) dovecot: May 04 09:56:58 Error: child 10721 (imap) killed with signal 6 This occurs sporadically and vanishes after some time. Is this something to worry about or not. I have mbox_dirty_syncs = yes Or does this just say "I am falling back to reading the whole mailbox"? Yours, Jakob Curdes

...connections use only a small number of blocks (due to Dovecot indexes, presumably) but occassionally a process will read lots of blocks, sometimes even more than a UW-IMAP session. Is this expected, or is something going wrong with the index updates? I have the default sync settings, I think (mbox_dirty_syncs = yes, mbox_very_dirty_syncs = no, mbox_lazy_writes = yes) My INBOX is an extreme example with ~10,000 messages and most processes reading a few hundred blocks but a couple using 20,000 or so! Also, Dovecot seems to be dropping connections, sometimes, for no good reason (putting some extra i_...

...ages weren't saved via Dovecot (deliver or IMAP). - Several bugfixes to handling sort indexes - deliver: Boolean settings that were supposed to default to "yes" were set to "no" unless explicitly defined in dovecot.conf: dotlock_use_excl, maildir_copy_with_hardlinks, mbox_dirty_syncs, mbox_lazy_writes. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://dovecot.org/pipermail/dovecot-news/attachments/20080609/f87d3eef/attac...

http://dovecot.org/test/ - Recent flag fixes - saving/copying mails into maildir which didn't have index files was broken - output stream fix - pop3 crashfix - mbox_dirty_syncs fixes, also disabling it didn't work before - etc. There are still some crashes and I don't remember if I fixed a problem with mboxes where expunging mails while new mails were coming caused some breakages.. but I can't reproduce it anymore. Anyway I think that could be fixed with...

...ages weren't saved via Dovecot (deliver or IMAP). - Several bugfixes to handling sort indexes - deliver: Boolean settings that were supposed to default to "yes" were set to "no" unless explicitly defined in dovecot.conf: dotlock_use_excl, maildir_copy_with_hardlinks, mbox_dirty_syncs, mbox_lazy_writes. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://dovecot.org/pipermail/dovecot-news/attachments/20080609/f87d3eef/attac...

With 1.2.11 and mbox storage, the delay time in pulling new mail headers to the client from imap folders seems to be directly proportional to mailbox size, regardless of the number of new messages. At present, if the mailbox is large, pulling new headers is rather painfully slow. Is this expected behavior? Especially given that the client already has all the "old" mails in the folder

...ot; command (and it gets informed of the flag change in the response). I've tried and tried to find a "formula" for re-creating the problem "on demand", but it only goes wrong occassionaly. My guess is it's some sort of timing thing with mbox sync (BTW we have "mbox_dirty_syncs = yes" and "mbox_very_dirty_syncs = no"). Has anybody else seen this? I'm hoping to roll out this version to our wider group of testers soon and would like to get this issue solved first if possible (it counts as an annoyance rather than a serious problem). Best Wishes, Chr...

...login_dir: /var/run/dovecot/login > login_executable: /usr/local/libexec/dovecot/imap-login > login_processes_count: 12 > login_max_processes_count: 774 > verbose_proctitle: yes > first_valid_uid: 200 > mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u:INDEX=/var/dcindx/%u > mbox_dirty_syncs: no > mbox_lazy_writes: no > auth default: > passdb: > driver: pam > userdb: > driver: passwd Suggestions? -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean at bard.edu voice:...

...gin_greeting_capability(imap): yes login_greeting_capability(pop3): no verbose_proctitle: yes first_valid_uid: 200 mail_location: mbox:/home/%u/mail/:INBOX=/var/mail/%u:INDEX=/home/%u/mail/.imap mail_debug: yes mail_full_filesystem_access: yes maildir_copy_with_hardlinks: no mbox_write_locks: fcntl mbox_dirty_syncs: no mbox_lazy_writes: no dbox_rotate_days: 0 mail_executable(default): /packages/run.64/dovecot-1.1.2/libexec/dovecot/imap mail_executable(imap): /packages/run.64/dovecot-1.1.2/libexec/dovecot/imap mail_executable(pop3): /packages/run.64/dovecot-1.1.2/libexec/dovecot/pop3 mail_plugins(default): an...

...ar/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_processes_count: 12 login_max_processes_count: 774 max_mail_processes: 1024 verbose_proctitle: yes first_valid_uid: 200 mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u:INDEX=/var/dcindx/%u mbox_write_locks: fcntl mbox_dirty_syncs: no auth default: passdb: driver: pam userdb: driver: passwd This is happening during peak load; the error msgs I'm seeing look like: Nov 5 15:01:47 mercury mail:err|error dovecot: IMAP(olson): Corrupted transaction log file /var/dci ndx/olson/.imap/INBOX/dovecot.index.log seq 7...

...= 100 verbose_proctitle = yes auth_verbose = yes mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u #default_mail_env = mbox:~/mail:INBOX=/var/spool/mail/%u mail_cache_min_mail_count = 30 mmap_disable=no mail_debug=no lock_method = flock mbox_read_locks = dotlock mbox_write_locks = dotlock fcntl mbox_dirty_syncs = yes mbox_very_dirty_syncs = yes mbox_lazy_writes = no ## ## IMAP specific settings ## protocol imap { login_executable = /usr/libexec/dovecot/imap-login imap_client_workarounds = outlook-idle netscape-eoh tb-extra-mailbox-sep delay-newmail mail_plugins = mail_log } ## ## POP3 specifi...

...S exports the user homedir and mailbox to a) a login shell host and b) a mailing list services host. It runs UWIMAP on the usual ports and dovecot on a arbitrary port number. Because of concern with NFS and file access contention. I have the following dovecot.conf file access parms set: a) mbox_dirty_syncs = no b) mbox_lazy_writes = no 1) I am seeing these errmsgs. Are they anything I should be concerned about, or are they just the inevitable result of lock contention for mailboxes and folders by procmail, imap/dovecot and NFS? > In syslog, I am seeing this: > > Apr 23 18:46:34 mer...

...box_list_index_disable: yes lock_method: fcntl maildir_stat_dirs: no maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: no maildir_very_dirty_syncs: no mbox_read_locks: fcntl mbox_write_locks: fcntl dotlock mbox_lock_timeout: 300 mbox_dotlock_change_timeout: 120 mbox_min_index_size: 0 mbox_dirty_syncs: yes mbox_very_dirty_syncs: no mbox_lazy_writes: yes dbox_rotate_size: 2048 dbox_rotate_min_size: 16 dbox_rotate_days: 1 mail_drop_priv_before_exec: no mail_executable: /usr/lib/dovecot/pop3 mail_process_size: 256 mail_plugins: mail_plugin_dir: /usr/lib/dovecot/modules/pop3 mail_log_prefix: %Us(%u...

...ar/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_processes_count: 12 login_max_processes_count: 774 max_mail_processes: 1024 verbose_proctitle: yes first_valid_uid: 200 mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u:INDEX=/var/dcindx/%u mbox_write_locks: fcntl mbox_dirty_syncs: no auth default: passdb: driver: pam userdb: driver: passwd -- ==== Once upon a time, the Internet was a friendly, neighbors-helping-neighbors small town, and no one locked their doors. Now it's like an apartment in Bed-Stuy: you need three heavy duty pick-proof locks, one o...

Hi, We are using mbox and UW IMAP, and are having issues because UW IMAP does not support multiple client access when you use NFS for the mail files. I've done some research (see the comments after my 2 questions below), and most of the other major IMAP servers simply don't support it (courier is about the only one that has a positive comment). How much testing have you done

...; mail_location = maildir:~:CONTROL=/var/no-quota/%u At first glance the above looks like it may be wrong or a typo. I don't remember now why I added the following, but it seems like it may be worth a shot: imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags > > mbox_dirty_syncs = no > mbox_lazy_writes = no Pretty sure the above is for mbox if you are using maildir I don't think they apply, but I could be wrong. Good luck. Edgar

On 12 Jun 2017, at 2.09, M. Balridge <dovecot at r.paypc.com> wrote: > >> I think it's just doing a lot of work on the mbox file itself >> (reading/writing/rewriting). Would be nice of course if it logged >> more information, but mbox format is a bit too legacy to spend >> much time on improving. > > I suspect the (heavy) use of procmail on Herr

Hi, i've few problem with uidl with some mailbox. In poplog i've this: Error: POP3(test): Couldn't init INBOX: Can't sync mailbox: Messages keep getting expunged If i delete the first message (with X-IMAP) i read the mailbux but retrieve all email .. If i set to yes pop3_reuse_xuidl i resolv this problem? -- Roberto Tagliaferri Responsabile Progettazione & Produzione

...ered does not work in pine. The status flags for New and Deleted work as always. The Answered flag worked properly in dovecot 0.99, but after upgrading to 1.0rc19 it stopped working. Interestingly, mail that was answered before upgrading to rc19 still shows the proper flag. I have tried with mbox_dirty_syncs turned on and off and I have tried putting "flags" in mail_cache_fields. Obviously I am wandering in the dark. Here is the setup: pine 4.64 dovecot 1.0rc19 (installed from rpm dovecot-1.0-2_40.rc19.el4.at.i386.rpm) Centos 4.4.2 x86 mail_location = mbox:~/mail/:INBOX=%h/.mailspool/...

...visible symptom of this happened every time new spam arrived in my Junk folder [3] --- the new spam would arrive, be flagged as spam by Mail.app, and the earlier pieces of mail would promptly be unflagged! Anyway, Timo's clue in [2] prompted me to turn off both mbox_lazy_writes and mbox_dirty_syncs (the latter just on the off- chance... it's a low-volume server, so I can deal with the inefficiency). Lo and behold, Mail.app started acting sane again *and* the X-Keywords header appeared immediately. Oddly, during all of this, the Status and X-UID keywords would appear in the me...