search for: maildir_check_content_changes

Quick question: How does dovecot keep the message headers index file updated? Eg: if my MDA delivers an extra 10 messages while I'm logged in. How does the message index get updated? At what points is it regenerated? Thanks, Paul

...tra_groups = mail client_workarounds = outlook-idle outlook-pop3-no-nuls mailbox_check_interval = 0 mailbox_idle_check_interval = 30 mail_full_filesystem_access = no mail_max_flag_length = 50 mail_save_crlf = no mail_read_mmaped = no maildir_stat_dirs = no maildir_copy_with_hardlinks = no maildir_check_content_changes = no mbox_lock_timeout = 300 mbox_dotlock_change_timeout = 30 umask = 0077 imap_executable = /usr/lib/dovecot/imap imap_process_size = 256 imap_use_modules = no imap_modules = /usr/lib/dovecot/imap pop3_executable = /usr/lib/dovecot/pop3 pop3_process_size = 256 pop3_use_modules = no pop3...

...in login_chroot = yes login_processes_count = 1 max_logging_users = 256 imap_executable = /usr/local/lib/dovecot/imap max_imap_processes = 1024 first_valid_uid = 1000 #last_valid_uid = 0 first_valid_gid = 101 last_valid_gid = 101 valid_chroot_dirs = /var/run/dovecot maildir_copy_with_hardlinks = no maildir_check_content_changes = no overwrite_incompatible_index = yes umask = 0077 auth = default auth_methods = plain #auth_realms = auth_userinfo = shadow auth_executable = /usr/local/lib/dovecot/imap-auth auth_user = root auth_chroot = /var/run/dovecot auth_count = 1 #auth = digest_md5 #auth_methods = digest-md5 #auth_realms...

...&& + !create_directories(full_home_dir, set->parent_dir_umask)) + i_fatal("mkdir(%s) failed: %m", full_home_dir); if (chdir(full_home_dir) < 0) i_fatal("chdir(%s) failed: %m", full_home_dir); } *************** *** 188,194 **** env_put("MAILDIR_CHECK_CONTENT_CHANGES=1"); if (set->mail_full_filesystem_access) env_put("FULL_FILESYSTEM_ACCESS=1"); - (void)umask(set->umask); env_put(t_strconcat("MBOX_LOCKS=", set->mbox_locks, NULL)); env_put(t_strdup_printf("MBOX_LOCK_TIMEOUT=%u", --- 229,234 ---- *** ./sr...

...ith_hardlinks = no # Check if mails' content has been changed by external programs. This slows # down things as extra stat() needs to be called for each file. If changes are # noticed, the message is treated as a new message, since IMAP protocol # specifies that existing message are immutable. maildir_check_content_changes = yes # Which locking methods to use for locking mbox. There's three available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory....

...ecutable = /usr/libexec/dovecot/pop3 verbose_ssl = no default_mail_env = /var/MailRoot/domains/%d/%n/Maildir mail_cache_fields = Envelope MessagePart client_workarounds = outlook-idle mailbox_check_interval = 5 mailbox_idle_check_interval = 30 maildir_stat_dirs = no maildir_copy_with_hardlinks = no maildir_check_content_changes = yes auth_mechanisms = plain auth_userdb = static uid=97 gid=97 home=/var/MailRoot/domains/%d/%n/Maildir auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth_passdb = passwd-file /var/MailRoot/dovecotusers.tab 3. Isnatll Xmail >From Source : http://ww...

Hi, I've got an 'interesting' problem with a dovecot 0.99.10.4 setup on NetBSD/i386 1.6ZK. dovecot is serving imap only at the moment, using mbox format mailboxes. '/etc/dovecot.conf' is pretty vanilla - among the modified settings, mail_read_mmaped = yes maildir_check_content_changes = yes mbox_lock = fcntl could be relevant. Anyway - from time to time when I move a bunch of mails ( < 1) from a mailbox to another (or to the trash), the client (I've seen it with Eudora 6 on a Mac, with Mozilla 1.6 and Sylpheed on NetBSD) reports an "internal error" and the...

...> > client_workarounds = oe6-fetch-no-newmail outlook-idle outlook-pop3-no-nuls > > #mail_full_filesystem_access = no > #mail_max_flag_length = 50 > #mail_save_crlf = no > #mail_read_mmaped = no > > #maildir_stat_dirs = no > maildir_copy_with_hardlinks = yes > #maildir_check_content_changes = no > > #umask = 0077 > > mail_drop_priv_before_exec = no > > #imap_executable = /usr/local/libexec/dovecot/imap > #imap_process_size = 256 > #imap_use_modules = no > #imap_modules = /usr/local/lib/dovecot/imap > > #pop3_executable = /usr/local/libexec/dovecot/...

hi there, I?m getting such a headache today, I?ve added myself to three mailing lists trying to figure this out, okay here it goes. I?ve got a Fedora Core 4 box running dovecot imap, squirrel mail, postfix, samba/winbind. I?m running winbind to authenticate against Active Directory, I?ve edited my ?/etc/pam.d/dovecot? pam module so to let my users login with there Active directory password, but

...verbose_proctitle = yes verbose_ssl = yes first_valid_uid = 5000 last_valid_uid = 65535 first_valid_gid = 5000 last_valid_gid = 65535 default_mail_env = maildir:/mail/%d/%u mail_save_crlf = yes maildir_copy_with_hardlinks = no maildir_check_content_changes = no mbox_locks = fcntl umask = 0077 imap_executable = /usr/libexec/dovecot/imap imap_process_size = 256 auth = default auth_mechanisms = plain auth_userdb = pgsql /etc/dovecot-pgsql.conf auth_passdb = pgsql /etc/dovecot-pgsql.conf...

...th_hardlinks = no # Check if mails' content has been changed by external programs. This slows # down things as extra stat() needs to be called for each file. If changes are # noticed, the message is treated as a new message, since IMAP protocol # specifies that existing message are immutable. #maildir_check_content_changes = no # Which locking methods to use for locking mbox. There's three available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory....

...th_hardlinks = no # Check if mails' content has been changed by external programs. This slows # down things as extra stat() needs to be called for each file. If changes are # noticed, the message is treated as a new message, since IMAP protocol # specifies that existing message are immutable. #maildir_check_content_changes = no # Which locking methods to use for locking mbox. There's three available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory....

...th_hardlinks = no # Check if mails' content has been changed by external programs. This slows # down things as extra stat() needs to be called for each file. If changes are # noticed, the message is treated as a new message, since IMAP protocol # specifies that existing message are immutable. #maildir_check_content_changes = no # Which locking methods to use for locking mbox. There's three available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory....

...th_hardlinks = no # Check if mails' content has been changed by external programs. This slows # down things as extra stat() needs to be called for each file. If changes are # noticed, the message is treated as a new message, since IMAP protocol # specifies that existing message are immutable. #maildir_check_content_changes = no # Which locking methods to use for locking mbox. There's three available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory....

...ith_hardlinks = no # Check if mails' content has been changed by external programs. This slows # down things as extra stat() needs to be called for each file. If changes are # noticed, the message is treated as a new message, since IMAP protocol # specifies that existing message are immutable. maildir_check_content_changes = yes # Which locking methods to use for locking mbox. There's three available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory....

..._hardlinks = no # Check if mails' content has been changed by external programs. This slows # down things as extra stat() needs to be called for each file. If changes are # noticed, the message is treated as a new message, since IMAP protocol # specifies that existing messages are immutable. #maildir_check_content_changes = no # Which locking methods to use for locking mbox. There's three available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory....

...h_hardlinks = no # Check if mails' content has been changed by external programs. This slows # down things as extra stat() needs to be called for each file. If changes are # noticed, the message is treated as a new message, since IMAP protocol # specifies that existing messages are immutable. #maildir_check_content_changes = no # Which locking methods to use for locking mbox. There's three available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory....

...th_hardlinks = no # Check if mails' content has been changed by external programs. This slows # down things as extra stat() needs to be called for each file. If changes are # noticed, the message is treated as a new message, since IMAP protocol # specifies that existing message are immutable. #maildir_check_content_changes = no # Which locking methods to use for locking mbox. There's three available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory....