search for: mbox_lazy_writes

...contains a pretty large mbox code cleanup, fixing several problems (especially related to X-IMAP/X-IMAPbase headers) and making it a bit faster. Maybe I'll backport it to 1.0-stable too when it looks like it's stable.. BTW. mbox code is slower than necessary when updating message flags and mbox_lazy_writes=yes, because it reads message headers for each message whose flag is to be changed (in index). Should fix that one soon too.. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally...

Hello all, I'm having problems with setting custom flags on a dovecot imap setup, with mbox mail store. I was running v1.0rc15 on a Debian Etch box, upgraded recently to v1.0.15, but nothing changed. The problem : I read my mail using IMAP. In Thunderbird (various versions, current one being v2.0.0.19), I can set various message flags (Important, Personal, Work, ... mapped to IMAP as

...a message in Mail.app, the message gets marked as deleted in the spool and it disappears from the mail listing in Mail. However, the message number does not change until I either manually flush the deleted messages through mail, or I go offline which deletes the messages from the spool. I have mbox_lazy_writes set to 'no' but this didn't seem to have any effect on the behavior. I never saw this type of behavior with UW-IMAP either, which is what I migrated from. Thanks.

...d 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/attachment.bin

Hello, When a message is copied or newly-delivered to a folder, it does not have the "recent" flag set. Is there something in the configuration to activate it ? Thanks. # dovecot -n # 1.0.9: /usr/local/etc/dovecot.conf protocols: imap login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login mail_location:

I have a problem where an e-mail will be marked as unread even though it has been read. When I click on the message the status changes to "read" however, when I go to check for new mail the status changes back to "unread." If I move the message to the trash folder and then move it back to my inbox, the problems stops. Unfortunately, a different e-mail is affected by

...d 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/attachment.bin

...n_dir: /usr/ladmin2/var/run/dovecot/login login_executable: /usr/ladmin2/libexec/dovecot/imap-login login_greeting: Dovecot ready. login_processes_count: 30 max_mail_processes: 4096 mail_location: mbox:%h/new:INBOX=/var/spool/mail/14/%u mmap_disable: yes dotlock_use_excl: no mbox_write_locks: fcntl mbox_lazy_writes: no mail_plugins: mbox_snarf imap_client_workarounds: delay-newmail auth default: mechanisms: plain gssapi krb5_keytab: /etc/krb5/dovecot.keytab gssapi_hostname: $ALL verbose: yes debug: yes passdb: driver: pam userdb: driver: passwd plugin: mbox_snarf: /gpfs/inbox...

Dear Dovecot list, I recently switched from uw-imapd to dovecot to manage my huge mbox files (about 1 GB). I now observe a very strange behavior, difficult to reproduce reliably, which might be related to some misunderstanding on my part on how either dovecot works or imap labeling works. What I call "labeling" is the fact of marking some e-mail, in my e-mail client (currently

...ogin_dir: /var/run/dovecot/login login_executable: /usr/local/dovecot/libexec/dovecot/imap-login login_user: nobody login_chroot: no login_max_processes_count: 30 max_mail_processes: 30 first_valid_uid: 1 mail_uid: smmsp mail_gid: smmsp mail_location: mbox:%h/Mail:INBOX=/var/mail/%u mail_debug: yes mbox_lazy_writes: no auth default: failure_delay: 1 verbose: yes debug: yes worker_max_request_count: 1 passdb: driver: pam args: imap -- Dmitry Samersoff dms at samersoff.net, http://devnull.samersoff.net * There will come soft rains ...

...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_info lines suggests for "inactivity"). Thun...

..... built on Debian9 with: > > # apt-get build-dep dovecot-core > > # bash configure --prefix=/scratch/dovecot-test > > > > Tried with both mailbox over NFS (backed by ext4), and also mailbox on ext4. > > > > On my test systems, I am only able to reproduce it with mbox_lazy_writes=no, > > but with production settings on a Ubuntu 14.04 with 1:2.2.9-1ubuntu2.4 that has > > mbox_lazy_writes=yes it is still reproducable with mutt. > > > > I have found two different ways to reproduce it with netcat + cut'n'paste, > > below is done with 2.2.34...

...ot.log listen: *removed* ssl_cert_file: /etc/pki/dovecot/certs/dovecot.pem ssl_key_file: /etc/pki/dovecot/private/dovecot.pem login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login mail_privileged_group: mail mail_location: mbox:~/mail:INBOX=/var/mail/%u mbox_lazy_writes: no imap_client_workarounds: outlook-idle delay-newmail auth default: cache_size: 1024 passdb: driver: pam args: session=yes cache_key=%u dovecot userdb: driver: passwd I want to start out by saying that Dovecot works 100% when viewing/moving mail (on our company mail server tha...

...gz https://dovecot.org/releases/2.2/dovecot-2.2.35.tar.gz .. built on Debian9 with: # apt-get build-dep dovecot-core # bash configure --prefix=/scratch/dovecot-test Tried with both mailbox over NFS (backed by ext4), and also mailbox on ext4. On my test systems, I am only able to reproduce it with mbox_lazy_writes=no, but with production settings on a Ubuntu 14.04 with 1:2.2.9-1ubuntu2.4 that has mbox_lazy_writes=yes it is still reproducable with mutt. I have found two different ways to reproduce it with netcat + cut'n'paste, below is done with 2.2.34/35. All servers are VMs in Ganeti/kvm clusters...

...Maildir/.test/tmp/1672326456.M737812P15507.<HOSTNAME>", "/home/test/Maildir/.test/cur/1672326456.M737813P15507.<HOSTNAME>,S=2498,W=2551:2,S") = 0 15507 unlink("/home/test/Maildir/cur/1672326270.M619318P11927.<HOSTNAME>,S=2498,W=2551:2,Sa") = 0 Setting mbox_lazy_writes to yes and/or unsetting mail_cache_fields doesn't change anything. Any idea of what I am missing? Could this be a bug in Dovecot? Thanks in advance, -- Alexis Ben Miloud--Josselin <abenmiloud at evolix.fr> Evolix - H?bergement et Infog?rance Open Source Marseille (37 rue Guibal, P?le...

...ot/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: 845-758-7475, fax: 845-758...

....2/dovecot-2.2.35.tar.gz > .. built on Debian9 with: > # apt-get build-dep dovecot-core > # bash configure --prefix=/scratch/dovecot-test > > Tried with both mailbox over NFS (backed by ext4), and also mailbox on ext4. > > On my test systems, I am only able to reproduce it with mbox_lazy_writes=no, > but with production settings on a Ubuntu 14.04 with 1:2.2.9-1ubuntu2.4 that has > mbox_lazy_writes=yes it is still reproducable with mutt. > > I have found two different ways to reproduce it with netcat + cut'n'paste, > below is done with 2.2.34/35. > > All server...

Dear Dovecot users, I'm a sysadmin in a company that recently migrated the IMAP from courier-imap to dovecot :-) *urray* Everything with the perl migrating scripts (version 1.0) went with OKs and it was a lot of fun (and pray) to move 400Gb of mails and migrate.. and everything is working even better :-) The problem is for some outside users that use webmails, like: - Squirrel -

...ty(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): antispam mail_plugins(im...

.../imap-login login_executable(pop3): /opt/dovecot/libexec/dovecot/pop3-login login_processes_count: 32 login_max_processes_count: 4096 max_mail_processes: 8192 first_valid_uid: 100 default_mail_env: mbox:~/:INBOX=/var/mail/%u mail_location: mbox:~/:INBOX=/var/mail/%u mail_full_filesystem_access: yes mbox_lazy_writes: no mail_executable(default): /opt/dovecot/libexec/dovecot/imap mail_executable(imap): /opt/dovecot/libexec/dovecot/imap mail_executable(pop3): /opt/dovecot/libexec/dovecot/pop3 mail_plugin_dir(default): /opt/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /opt/dovecot/lib/dovecot/imap mail_plugin_...