search for: 1.1rc4

Hi. Just got this error (1.1.rc4), is it something to worry about? Corrupted index cache file /.../Maildir/.Sent/dovecot.index.cache: used_file_size too large This is a shared mailbox with concurrent access. In general, can that usage pattern mess up the index? I am guessing "no", which is why I worry slightly about the warning. Cheers, Anders.

Hello again. I am trying to use a master user. The login works. However, a LIST command gives me only the INBOX. Is this to be expected? When logging in normally, I do get the full list of folders. (using Dovecot 1.1 rc3.) Anders.

Emailed about this with 1.1rc3 and didn't get a reply. Tried upgrading to 1.1rc4 and got the same crashing: Centos 5 (in openvz container) 2.6.18-53.1.4.el5.028stab053.4 #1 SMP Fri Jan 18 12:29:44 MSK 2008 x86_64 x86_64 x86_64 GNU/Linux /usr/local/dovecot/sbin/dovecot -n # 1.1.rc4: /usr/local/dovecot/etc/dovecot.conf log_path: /var/log/dovecot.log protocols: imap imaps pop3 pop3s

Is --with-file-offset-size no longer supported in 1.1? # ./configure \ --prefix=/usr/local/dovecot-1.1 \ --with-mysql \ --with-file-offset-size=32 \ --with-ioloop=best \ --with-pop3d \ --with-ssl \ --with-deliver \ ... checking for _FILE_OFFSET_BITS value needed for large files... 64 ... Install prefix ...................... : /usr/local/dovecot-1.1 File

Hello I've noticed a little strange behaviour of that option. For example with following settings: system user: admin, with its home directory as /home/admin dovecot options: as reported by dovecot -n (in attachment) dovecot will try to chroot into /home/home/admin with the following message in logs, in my case: Fatal: chdir(/home/home/admin) failed with uid 1999: No such file or

Hi, it looks like there is a bug (in dovecot or in my config) with quota on maildir mailboxes when accessed via POP3. The maildirsize is not created when not already present (even after a DELE + QUIT command). The quota limit (the first line of maildirsize) is not updated if values are not in sync with those in the database. If maildirsize is present, DELE commands are correctly reported in

Guys, I'm getting strange messages on my new server with dovecot-1.1rc4 + lda + sieve + ldap + postfix + suse10. This server is in production since monday, and worked fine until today. The only thing I had changed was dovecot from 1.1rc3 to 1.1rc4. I already enabled mail_debug, but I got any erros after that. Does anyone have any idea of what is happening? Unable to handle kernel NULL

Hi, I have tested dovecot 1.1.rc4. I seems to works fine with my configuration. I have also tested the downgrade from 1.1rc4 to 1.0.10. It seems to work fine too expect the following messages. Apr 15 14:46:44 dev dovecot: IMAP(lolo at gretel.com): Fixing header counts in index /data/mail/gretel.com/l/o/lolo//dovecot.index: Recent counter wrong Apr 15 14:46:49 dev dovecot: IMAP(lolo at

Hello all, I followed the wiki to configured the expire plugin on dovecot-1.1rc4 and it isn't working. No error messages on logs or on the execution of "dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool". mailserver02:~ # dovecot -n # 1.1.rc4: /etc/dovecot//dovecot.conf syslog_facility: local1 protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no shutdown_clients:

Upon upgrading from 1.0.2 to 1.1rc4 I see this error for many of our users: Getting size of message UID=1 failed Couldn't init INBOX: Can't sync mailbox: Messages keep getting expunged Logging in with IMAP I would see a bunch of messages with no subject or time and blank bodies (usine horde/imp). Removing dovecot.index.log, dovecot.index.log.2, or dovecot-uidlist fixes the problem

I burned some time yesterday over a documentation inconsistency. The dovecot-example.conf file shipped with dovecot (checked with 1.1rc4 and the April 3 nightly), includes an indication at the top that the commented values listed are the defaults for the settings. Line 248 of this file has the inbox setting for a private namespace which indicates that the default value for this setting is true.

I recently switched one of our 30 imap servers to 1.1RC4 from 1.0.x, and the difference is huge. The load on the server dropped from 5+ to 0.3 or so. This means there is no more io waiting going on. Thats on FreeBSD 6.2. Great work Timo! Cor

Hi, ever since i switched a few servers to 1.1RC4 im finding control dirs with the wrong permissions: 80023615 8 drw------- 2 xxxxxxx user 4096 Apr 23 09:46 ./a/an/xxxxxxx/INBOX/.INBOX.Maatschappijen When dovecot then wants to write a file inside, it gets a permission denied. Cor

Hi I am running Dovecot 1.1RC4, built from the source packages at the debian repositories (http://xi.rename-it.nl/debian/). When a message is delivered through the LDA, i get this error: deliver(******@*****): May 02 14:43:28 Fatal: Running as root isn't permitted These are my config files: master.cf: ======================================= # Dovecot dovecot unix - n n - - pipe

Hi! I'm running 1.1rc4 on a system and this happens occasionally: --8<-- mail.info; dovecot: auth(default): client in: AUTH 1 PLAIN service=imap lip=NN.NN.NN.NN rip=NNN.NN.NNN.NN lport=143 mail.info; dovecot: auth-worker(default): pam(XXXXXXXXXXXX,NNN.NN.NNN.NN): lookup service=imap kern.alert; kernel: grsec: From NN.NN.NN.NN: denied resource overstep by requesting

dovecot version: 1.0.13 (RPM from http://atrpms.net/) protocol: IMAP dovecot -n: # 1.0.13: /etc/dovecot.conf log_path: /var/log/dovecot/dovecot.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