- dovecot - dovecot.org

[Dovecot] Next message unexpectedly corrupted in mbox file
by Justin Piszcz 08 Feb '10

08 Feb '10

Hi, I am seeing this on one of my servers: Jan 8 10:08:58 l1 dovecot: IMuser(user): Next message unexpectedly corrupted in mbox file /home/user/Mailbox at 10558 I have never seen this before, and google yields no results except when this warning was added to the source code here: http://www.dovecot.org/list/dovecot-cvs/2009-December/015177.html The user has deleted all of the mail in the Mailbox but the problem persists. Any ideas? Justin.

4 9

[Dovecot] managesieve does call a wrong chown
by Wolfgang.Friebel＠desy.de 07 Feb '10

07 Feb '10

After upgrading from dovecot 1.2.3, managesieve 0.11.8, sieve 0.1.11 to dovecot 1.2.9, managesieve 0.11.10 and sieve 0.1.14 users who do not have sieve rules yet and use managesieve for the first time do trigger error messages in the log file (for the authenticated user ggg in group syspr): Jan 4 17:35:26 apollo dovecot: MANAGESIEVE(ggg): chown(/var/spool/sieve/ggg, -1, 0(root)) failed: Operation not permitted (egid=203(syspr)) Jan 4 17:35:26 apollo dovecot: MANAGESIEVE(ggg): sieve-storage: sieve_storage_verify_dir(/var/spool/sieve/ggg/tmp) failed: Operation not permitted Jan 4 17:35:26 apollo dovecot: MANAGESIEVE(ggg): Fatal: Failed to create sieve storage with data: /var/spool/sieve/ggg Anyway the filter rules get created (used avelsieve) and the filter does get compiled when the first mail hits the rule. Subsequent invocations of managesieve do not try to change the group ownership of the directory. Looks like an annoyance only, but I would feel more comfortable w.o. the error messages. the dovecot -n output: # 1.2.9: /etc/dovecot.conf # OS: Linux 2.6.18-164.6.1.el5 x86_64 Scientific Linux SL release 5.4 (Boron) protocols: imap imaps managesieve listen(default): * listen(imap): * listen(managesieve): *:2009 shutdown_clients: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(managesieve): /usr/libexec/dovecot/managesieve-login login_processes_count: 5 login_max_processes_count: 512 verbose_proctitle: yes mail_location: maildir:~/Maildir mmap_disable: yes fsync_disable: yes lock_method: dotlock maildir_copy_with_hardlinks: no mbox_read_locks: dotlock flock mbox_write_locks: dotlock flock mail_drop_priv_before_exec: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(managesieve): /usr/libexec/dovecot/managesieve mail_plugins(default): quota imap_quota zlib acl imap_acl listescape mail_plugins(imap): quota imap_quota zlib acl imap_acl listescape mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(managesieve): /usr/lib64/dovecot/managesieve imap_client_workarounds(default): delay-newmail netscape-eoh tb-extra-mailbox-sep outlook-idle imap_client_workarounds(imap): delay-newmail netscape-eoh tb-extra-mailbox-sep outlook-idle imap_client_workarounds(managesieve): namespace: type: private separator: / location: maildir:~/Maildir inbox: yes list: yes subscriptions: yes namespace: type: private separator: / prefix: #mbox/ location: mbox:~/mail:CONTROL=~/mboxctrl hidden: yes list: no subscriptions: yes lda: postmaster_address: postmaster(a)ifh.de mail_plugins: sieve quota acl sieve_global_path: /var/spool/sieve/default.sieve quota_full_tempfail: yes auth_socket_path: /var/run/dovecot/auth-master fsync_disable: no auth default: mechanisms: gssapi gss-spnego login plain realms: IFH.DE DESY.DE cache_size: 32 passdb: driver: pam args: max_requests=1 cache_key=%u userdb: driver: passwd-file args: /etc/userdb socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 438 plugin: quota: maildir:User Quota quota_rule: *:storage=1000MB quota_rule2: INBOX:storage=1000MB quota_rule3: Trash:ignore acl: vfile:/etc/dovecot-acls:cache_secs=300 acl_shared_dict: file:/var/spool/shared/shared-mailboxes.db sieve_storage: /var/spool/sieve/%u sieve: /var/spool/sieve/%u.sieve quota_warning: storage=95%% /usr/local/bin/mailquota-warning.sh 95 quota_warning2: storage=80%% /usr/local/bin/mailquota-warning.sh 80 quota_warning3: storage=60%% /usr/local/bin/mailquota-warning.sh 60 -- Wolfgang Friebel Deutsches Elektronen-Synchrotron DESY Phone/Fax: +49 33762 77372/216 Platanenallee 6 Mail: Wolfgang.Friebel AT desy.de D-15738 Zeuthen Germany

3 5

[Dovecot] LMTP in 2.0: concurrency, inet sockets
by Stefan Foerster 07 Feb '10

07 Feb '10

I didn't really have much time to look at the beta versions of dovecot 2.0 (apart from installing it once and migrating most of my current configuration, purely for testing purposes). An exciting new feature is the LMTP support. In the default configuration I have seen, that one only listened on a Unix socket - will it support network (inet) sockets, too? What about concurrent deliviers? As of now, when using the deliver LDA together with Postfix, you have to make sure that only one recipient is passed to deliver at a time, so for multi-recipient mail, the system might spawn a large number of processes (two per recipient, therefore two forks/execve calls). Is that limit still imposed with the new LMTP server? Stefan

3 4

Re: [Dovecot] LMTP in 2.0: concurrency, inet sockets
by Timo Sirainen 07 Feb '10

07 Feb '10

On Sun, 2010-02-07 at 13:40 +0100, Stefan Foerster wrote: > For 100k messages, delivery to a Maildir store using Postifx's pipe(8) > and Dovecot's deliver took 4319s, which equals 23.15 delivieries per > second - and that's with the pipe(8) delivery agent haning around for > up to 100 seconds, being reused for multiple transactions. > > Dovecot 2.0, with LMTP, was finished after 4007s, which equals 24.96 > deliveries per second. You could also try if maildir_very_dirty_syncs=yes affects it.

1 0

[Dovecot] blocked for xx secs
by Andrew Hearn 06 Feb '10

06 Feb '10

Hello, Occasionally (a few times a day) we get batches of Warnings in the log such as: dovecot: Warning: chdir(/maildir/x.co.uk/users/y) blocked for 18 secs This tends to last a minute or so for different users. /maildir is a NFS mount, and I'm suspecting it's the NFS server being busy and dovecot having to wait. Other than replacing the NFS server with faster hardware is there anything else we can do? Indexes are local, and Maildir is on the NFS. Dovecot 1.2.5 using: mail_nfs_storage = yes mmap_disable = no NFS mounted as; /maildir on /.automount/a.diskless/root/mail type nfs (nosuid,nodev,noatime,vers=3,proto=tcp) TIA -- Andrew

2 1

[Dovecot] Compressing Maildir mails on delivery
by Timo Sirainen 06 Feb '10

06 Feb '10

Now supported by v2.0. Also as a patch to v1.2: http://dovecot.org/patches/1.2/zlib-compress.diff I'm not really sure if I should commit it to v1.2 code tree. The code contains ugly copy&pasted io_stream_copy() and v1.2 is supposed to be feature complete..

3 5

[Dovecot] Also - is there a reliable way for TB to know it is connecting to a dovecot server?
by Charles Marcus 06 Feb '10

06 Feb '10

This would be so it could auto-disable GLODA - its new 'Global Search and Indexing' scheme - for that account - assuming they accept (and implement) my bug request to be able to do that: https://bugzilla.mozilla.org/show_bug.cgi?id=544100

2 6

[Dovecot] upgrade 1.0.x -> 1.2.x
by maximatt 06 Feb '10

06 Feb '10

its posible upgrade from dovecot 1.0.x to 1.2.x? i only see upgrades over micro versions.. thanks! -- Salu2 ;)

2 1

[Dovecot] v2.0: tcp-wrappers support
by Timo Sirainen 06 Feb '10

06 Feb '10

Some people have been requesting this forever. So finally this works: service tcpwrap { unix_listener login/tcpwrap { mode = 0666 } } login_access_sockets = tcpwrap There can also be more sockets listed, in case someone wants to build their own access checking service.

1 0

[Dovecot] pop3 quick question
by Nikita Koshikov 06 Feb '10

06 Feb '10

Hello list, I have found imap_allowed option in dovecot which do exactly what I need, for imap. Is there something similar for pop3 protocol? The main goal for it - is to enable pop3 access to specific users. Or maybe dovecot have some 'pop3=yes' or 'imap=no' args to userdb/passdb sections ? I know future dovecot 2.* versions will support rewriting for protocols, but this is required for 1.2 branch.

2 2